As somebody that went through this because of Katrina, you also need to
think about Licenses. If you don't have an extra Networker enabler,
the minute you go online with a duplicate license, both will shut down.
For testing, you can use a 45 day enabler, but then you need to think
about any SLQ, ORACLE, or Exchange modules that you might have.
The renaming of a Networker server works fine. In our case, our
original server was completely intact in New Orleans, but because Bell
South could not provide any data circuits to our building, we had to
come up on a new server in Baton Rouge. To keep things as simple as
possible, we came up under the same server name and IP address.
Eventually, we had to bring up the original server in New Orleans, and
to do this, I had to bring it up off the network, and use the Legato
renaming procedures. I also had to create a hosts file so that it could
have some way to resolve the client names that were previously backed up
by this server.
Once the server is renamed, you can put it on the network, and have it
join the Domain (if it's in a windows environment).
Lastly, (sorry for the long wind) I can't reiterate enough about having
extra Legato licenses for this. In our case, I used a set of licenses
from an old decommissioned server. We have about 30 SQL and 15
Exchange servers, so moving the licenses to the appropriate server can
be time consuming. Legato has a web link to move enablers from one
server to another, and I used it frequently.
Good luck, and as others stated, testing before you are under the gun
would be preferable.
David M. Browning Jr.
LSUHSC Enterprise Network Operations/Help Desk
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Dave Mussulman
Sent: Thursday, September 28, 2006 12: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
|
