On Mar 17, 2008, at 1:59 PM, Werth, Dave wrote:

We're using Networker 7.2.2 on mostly Windows 2K or 2003.



We are in the process of replacing our main file server with new
hardware.  On the old server there are 3 file systems (that we want to
recover) and they are backed up concurrently so the savesets are
multiplexed on the backup tape.  So now I'm testing methods to recover
the backups from the old server to the new one.  Over the weekend I
tried doing it from the Networker User GUI.  Unfortunately it recovers

the savesets serially which would require well over 24 hours to recover all 3 systems. So I'm looking at using the 'recover' command to recover by SSID. When I look at the command it's not clear to me that I can use

the SSID version to recover to a different server than the original

source of the savesets. It looks like the -R (recover-target) parameter

can't be used with the -S (ssid) parameter.

I don't want to test it and possibly mess up the original server so I'm

seeking advice about how best to proceed.

More details: the old server has E:\, F:\ & G:\ volumes that I want to restore to the same locations on the new server (which are all empty at the moment). My thought is to run the recover command on the new server

specifying the save set ID's of the backups from the old server.  What
I'm afraid of is even though I'm running it on the new server it will
try to restore to the old server disrupting the production going on

there at the moment. Of course when we do it for real we will keep the

users off the old system until the transfer is complete.

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