|
[Networker] Cloning/migrating from AFTD with multiple clones - first clone gets removed from DB
2008-01-31 14:05:29
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
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] Cloning/migrating from AFTD with multiple clones - first clone gets removed from DB,
Brian O'Neill <=
|
|
|
