Faidherbe, Thierry wrote:
>Hi,
>
>NetWorker reporting Utility contains, in client configuration pages,
>the information about which backup command must be used for
>a specific client ressource. This is not a problem, this is
>just like looking at backup command field from Nwadmin GUI.
>But this is not your expectation.
>
>Determining now, from mminfo, the cmd name that issued a save session
>is just impossible. Networker does not allow you to track backup cmd name.
>For eg, you cannot retrieve that the cmd "NSRXCHSV.exe" has been used to start
>a
>MSEXCH: saveset for client my_exch_server. It's just impossible.
>
>The only thing you "can" track is if a saveset has been started
>from a savegroup or not (using "group" field in mminfo query)
>but this is not 100% reliable as you can issue a manual save
>session and forcing a group membership.
>
>In addition (and if I followed you), you dump the data from the
>clearcase client to a netapp filer and then, dump the netapp filer
>via ndmp to tape. This is a multi steps backup.
>
>Up to now, what you can do if you know the source client(s) and NetApp Filer
>saveset name(s) is to build your backup quality control ruleset(s)
>(see FAQ page provided with my reporter kit) : In the rulesets, you
>will have to define "source client" as your clearcase server and
>"backuping client" as your effective backuping client name (NetApp Filer name)
>and restrict saveset names to used NetApp volumes (but NetApp volume saveset
>naming, of course -/vol/XXXX for eg-). This may be a solution if your
>volume is dedicated to 1 Q-TREE (because ndmp backups are volume-based
>and not QTREE-based).
>
>See section "Using NetWorker Reporting Utility's Backup Quality Control Rules
>Editor" but this is again a status such as reported by mminfo (final backup
>step) and
>you cannot overwrite it : You may have an incomplete/incorrect clearcase dump
>that has correctly been written to tape and reported as OK by mminfo.
>
>HTH,
>
>Th
>
>Kind regards - Bien cordialement - Vriendelijke groeten,
>Thierry FAIDHERBE
>HP Services - Storage Division
>Tru64 Unix and Legato Enterprise Backup Solutions Consultant
>********* ********* HEWLETT - PACKARD
>******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
>****** h ****** 1140 Bruxelles/Brussel/Brussels
>***** hhhh pppp *****
>***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
>***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
>****** p ****** BELGIUM
>******* p *******
>********* ********* Phone : +32 (0)2 / 729.85.42
> Mobile : +32 (0)498/ 94.60.85
> Fax : +32 (0)2 / 729.88.30
> I N V E N T Email/MSN : thierry.faidherbe(at)hp.com
> Internet : http://www.hp.com/ <http://www.hp.com/>
>
>
>________________________________
>
>De: Legato NetWorker discussion de la part de bob flynn
>Date: mer. 4/01/2006 12:26
>À: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Objet : Re: [Networker] networker reporting utility and backup command
>
>
>
>Itzik Meirson wrote:
>
>
>
>>Normally, clearcase backups are just regular file(system) backup that
>>have been done by either a special backup script or the Networker
>>savepnpc pre/post processor.
>>As such, there is no special designation for clearcase backups.
>>As regarding to the second part of your question, there is no recording
>>of the "backup command".
>>The "script" or in other words the "backup command" can (usually) be
>>found in the Networker's executables directory according to the OS
>>platform.
>>Itzik
>>
>>-----Original Message-----
>>From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
>>EDU]
>>On Behalf Of bob flynn
>>Sent: Wednesday, January 04, 2006 12:50
>>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>>Subject: [Networker] networker reporting utility and backup command
>>
>>What I want to do is the following.
>>
>>Identify savesets which have been backed up via a specific backup
>>command. This is a script which is clearcase aware.
>>
>>The purpose of this is, I want to flag those savesets having failed via
>>this backup scripy to the clearcase administrator and provide a status
>>of success/failure to the people using the data being backed up. I know
>>I can pull this data out via mminfo, but as I am already using netwoker
>>reporting utility, I was wondering if the backup command used is stored
>>during the processing anywhere.
>>
>>I have grepped for the script name in the data directory, but have been
>>unable to find it.
>>
>>Thanks for any info.
>>
>>-Bob
>>
>>The information contained in this e-mail and in any attachments is
>>confidential and is designated solely for the attention of the intended
>>recipient(s). If you are not an intended recipient, you must not use,
>>disclose, copy, distribute or retain this e-mail or any part thereof. If
>>you have received this e-mail in error, please notify the sender by
>>return e-mail and delete all copies of this e-mail from your computer
>>system(s).
>>Please direct any additional queries to: communications AT s3group DOT com.
>>Thank You.
>>
>>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>>type "signoff networker" in the body of the email. Please write to
>>networker-request AT listserv.temple DOT edu if you have any problems wit this
>>list. You can access the archives at
>>http://listserv.temple.edu/archives/networker.html or via RSS at
>>http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>
>>
>>
>>
>I had a look at the savepnpc, and the problem is that the clearcase vobs
>are stored on a netapp file server. The backups are done via ndmp.
>Therefore as my understanding of the savepnpc command, the legato server
>contacts the client to run the pre and post commands. However as the
>client in this case is not an active legato client, it cannot complete
>the commands. So rather than doing this, I script the closing and
>opening of the clearcase vob from the legato server before asking the
>ndmp client to backup the saveset.
>
>What I am getting at, is there a way of confirming the script or command
>used to carry out the actual backup of a saveset, as I can use this as a
>flag to indicate it the saveset was of a clearcase VOB or not ?
>
>-Bob
>
>
>
>The information contained in this e-mail and in any attachments is
>confidential and is designated solely for the attention of the intended
>recipient(s). If you are not an intended recipient, you must not use,
>disclose, copy, distribute or retain this e-mail or any part thereof. If you
>have received this e-mail in error, please notify the sender by return e-mail
>and delete all copies of this e-mail from your computer system(s).
>Please direct any additional queries to: communications AT s3group DOT com.
>Thank You.
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type "signoff networker" in the
>body of the email. Please write to networker-request AT listserv.temple DOT
>edu if you have any problems
>wit this list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>
>
>
many thanks for the detailed reply.
To clarify the backup process.
savesets which contain clearcase data, call a clearcase aware script.
This does the following;
1. Locks the vobs residing in the saveset. ( It can do this as the
backup server is also a clearcase client ).
2. tell the filer to run a ndmp dump of the saveset.
3. Once completed, unlock the vobs.
4 To some housekeeping, ie rotate log files to track the above.
I propose to change this by making snapshots on the filer clearcase
aware, then simply doing a snapshot and backing this up.
>From what you are saying, the simplest way of marking out clearcase
backups would to do something like put all clearcase data on a specific
volume and search for the status of backups of that volume ?
The information contained in this e-mail and in any attachments is confidential
and is designated solely for the attention of the intended recipient(s). If you
are not an intended recipient, you must not use, disclose, copy, distribute or
retain this e-mail or any part thereof. If you have received this e-mail in
error, please notify the sender by return e-mail and delete all copies of this
e-mail from your computer system(s).
Please direct any additional queries to: communications AT s3group DOT com.
Thank You.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
