On Wed, Sep 27, 2006 at 02:19:52PM -0700, Darren Dunham wrote:
> > I was thinking that the new server would need to be the same name 
> > (Server_A) or does it?  
> 
> No, not necessarily.  Certainly not the way that Netbackup binds
> everything to the server name.
> 
> There is a technote procedure for changing the name of the networker
> server.  You could do that (basically you're changing the name of the
> server from A to B).  However if all you're doing are simple restores, I
> think it should "just work".

I would test that first.  Because indexes are associated with the
servername, you may need to do some sort of rename operation in
Networker to have it read and reconigze the indexes properly.  If you
only care about saveset recovers, that Darren's statement might be true.

>From my experience moving/renaming servers, I would probably create the
system with the same hostname/IP/hosts file etc. as the production one
(taking it off the network, if necessary, to do so,) and complete the
entire DR restore with the new server as much like the old one as
possible.  Test index restores, etc.  Then, when you've got the data
base (meaning the indexes and media database, not necessarily the client
data,) look at renaming the network and getting the secondary DR server
online to restore to clients.

But test, confirm and document it all as best you can first.  The
DR/renaming procedure isn't something I'd want to do under fire.  (And
sometimes you don't know you should have done something at step 4 until
you get to step 12, so there is an appreciation for dry run full tests
first.)

Dave

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
wit 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