In regard to: Re: [Networker] nsrstage/nsrclone, Frank Swasey said (at...:

Alan,

nsrstage is used to move a saveset from one volume to a different volume. If you go into NMC's configuration panel and look at the staging rules, you can see the policies that are possible to be defined (number of days on the volume, %full of the volume). However, this is not a clone, the original saveset is deleted when the staging process is completed.

It may be semantics, but I don't completely agree with that last sentence.
nsrstage *is* a clone, but it's a clone that is (generally) followed by
a removal of the "original" (which might also be a clone).  If you do a
complete migration, you will have the same number of copies of a saveset
when nsrstage completes, whereas with a traditional clone, you would have
N+1 copies.

What Frank is saying is important to keep in mind, though.  If you want
multiple copies of a saveset, you generally shouldn't use nsrstage,
because it's really meant to move savesets (by cloning and then deleting
the source), not produce duplicates.  If you want N+1 copies of a saveset
when your operation finishes, traditional cloning is likely the way to go.

Tim

Today at 10:18am, Alan Maxwell wrote:

Currently in our environment we do "manual" cloning of savesets using perl
scripts and the nsrclone command.  While there is some automation to this
more is desired.  I have read that nsrstage can do more policy driven
cloning, but I have some concerns.
What sort of control would you have to stop and start cloning , say due to
a hadware issue?  Would you have to stop the entire server services?

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

--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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