We just went through a DR exercise.  We were able to recover the client
indexes to a separate server.  Basically we TARed up the client indexes
moved them to the DR server, defined the client and then performed an
NSRCK -L 7 on the DR Networker Server.

That being said we only did a recovery using SSID but, the indexes were
browsable etc.

This was done from a Solaris 8 SPARC machine to a Solaris 10 X86 machine
running under VMWare.  We were actually able to restore a partition
saved using RAWASM on the Solaris 8 box to the Solaris 10 box.  

Brian

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Dave Mussulman
Sent: Thursday, September 28, 2006 1:33 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Disaster Recovery on a different server

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

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