Re: [Networker] Failed Automatic Clones Result in Volumes Marked Full
2009-03-20 06:43:35
On 3/19/09 8:16 PM, JGillTech wrote:
How can I repair this? Basically I need to clone multiple volumes onto a single volume and avoid the creation of another ssid/cloneid or "expire" the original ssid/cloneid of the clone instance and create another on the new volume. Further, I would like the merged volume to expire at the same time the orignal (if the operation was successful) would have expired... so in this case 42 days from today.
Any advice?
You should be able to use the nsrstage command specifying the ssid and
cloneid (the -S parameter) of the clone copy to move it off those three
volumes onto another.
However, there is no guarantee that networker won't have issues with
other volumes and still not put the whole thing on a single volume like
it should -- whatever is causing the errors that forced the original
clone to span volumes will still be in play.
--
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
|
|
|