Hello Brian,
I believe you are speaking of "nsrstage" instead of "nsrclone".
Your problem is simple. nsrstage will stage successfully the saveset you
will mention, but if there is multiple instances of this same ssid, all of
them will be deleted from the media database. Networker, after the staging
process, run something similar to nsrmm -d -S 1234566 to erase the
saveset... If you run this manually against an existing saveset, all copies
of it will go away...
How can you deal with this? By using the combination of ssid/cloneid. Run
simply a script like this:
mminfo -av -q"volume=dbo1.001,savetime<=5 days ago" -r"ssid,cloneid" -xc/ >
staging.txt
This will give you and output like this in the file
ssid/cloneid
12345676/12341234
nsrclone, nsrstage and nsrmm understand this as well: -S 123456/12341234
Now you can simply run an nsrstage against this file and it will work just
fine...
nsrstage -v -b"Destination Pool" -m -S -F staging.txt
But it will generate an error on the first entry because nsrstage can't
parse ssid/cloneid words written at the beginning of the file. A simple FOR
loop skipping the first line or the use different tools to mangle the file
will make it right.
Then, run nsrtage -v -C -V dbo1.001 at the end of your script to ensure the
DBO will be cleaned up.
Hope it helps!
Eric Poulin
On Jan 31, 2008 2:01 PM, Brian O'Neill <oneill AT oinc DOT net> wrote:
> I've got a script that has worked great for us for making two tape
> clones of savesets from a VTL. I generate a list of ssid/cloneid pairs
> from the VTL tapes, and feed that to nsrclone (for the first copy) and
> nsrmigrate (for the second copy, which then removes the DB entries for
> the original VTL tapes), and then recycle the tapes.
>
> I'm now trying to adapt this for use with an AFTD staging device instead
> of the VTL. This has thrown a wrench into the works.
>
> When I generate the list of ssid/cloneids from the RO side of the AFTD,
> and then nsrclone them to pool CloneA, everything is fine. But when I
> nsrmigrate them to pool CloneB, the DB entries for both the original
> AFTD savesets go away (good), but also for the CloneA copies (bad). I
> end up with a full CloneA tape with nothing on it. :(
>
> I tried specifying just the ssid, which had the same effect.
>
> Any ideas on what the magic combination might be?
>
> I know I could simply feed the AFTD volume directly to
> nsrclone/nsrmigrate, but I want to avoid the possibility of a backup
> running simultaneously and ending up on CloneB but not CloneA because of
> timing.
>
> -Brian
>
> 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 with
> 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
>
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 with 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
|
