Hello
If you are doing this switch over at your site , you may have better 
alternative, can you not setup a copy job which can keep the file system 
in sync.
 ( provided your system names are different).Then all you will need to do 
is shut down netwoker services on the primary, run a last sync job and 
rename servers and move the devices, all of this within minutes. ( you 
will then need to get the licences transferred over to the new server with 
the help from EMC)
You can practice with the software listed here.
Secure copy
Secure sync
Robocopy.
HTH




"Werth, Dave" <dave.werth AT GARMIN DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
03/17/2008 12:59 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
"Werth, Dave" <dave.werth AT GARMIN DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
[Networker] Best way to recover to a new server






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.

 

Thanks, Dave.

 

Dave Werth

Garmin AT, Inc.

Salem, Oregon

 


-------------------------
This e-mail and any attachments may contain confidential material for the 
sole use of the intended recipient. If you are not the intended recipient, 
please be aware that any disclosure, copying, distribution or use of this 
e-mail or any attachment is prohibited. If you have received this e-mail 
in error, please contact the sender and delete all copies.
Thank you for your cooperation

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



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