On 1/20/09 4:14 PM, halomerchant wrote:
Frank,
If this is the case were you could deadlock savesets - then would it be wiser
to just clone by volume and bypass SSIDs? I believe using something like a
split command in solaris will give you the opportunity of writing x amount of
VT* barcodes to file1, file2, file3 - and then just run multiple nsrclone
processes against these files?
You could clone the tape -- but read the nsrclone command -- it doesn't
just clone that tape... it will clone all SSIDs that are even partially
contained on that tape (so, you will get more than the contents of the
tape). And because of that -- you can wind up with the same problem
(one process waiting for the other process to finish with the tape it
needs) even cloning at the volume level. Will it deadlock? It
shouldn't -- but I have seen NetWorker deadlock where that APPEARED to
be the reason (hard to tell why jobs are hung up in NetWorker because
there's no command to tell you what they are waiting for when it doesn't
show up as an alert).
Or is cloning by SSID the better way to go?
I think it is -- you won't accidentally clone an SSID multiple times
that way, and it's the way I do it.
BTW - have you shared your script anywhere that I could reference or test out?
I have sent it privately to a couple of people, I'll do the same for you.
Thank you.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
| 