HI Venkat,
I assume the 2 servers have different hostnames.
1) After a failover to server2, how do you handle that the clients
can be backed up by a NW server of a different hostname (both server1
and server2 in every clients servers file ?)
2) I was of the opinion that the MM folder data and the INDEX data
were somehow linked to the hostname of the NW server, and that if you
copied it across to another NW server, it would not work. Obviously,
this is not what happened in your case. What version(s) of NW did do
use ?
regards
John Hope-Bailie
From: Venkat Tudi [mailto:venkat.tudi AT gmail DOT com]
Sent: 15 January 2010 04:26 PM
To: EMC NetWorker discussion; John Hope-Bailie
Subject: Re: [Networker] Implementing a standby NetWorker Server
You can do the following way also. We used to do it this way and worked
verywell for us.
This requires another NW server LIC.
1). Install Networker Server.
2). MMRECOVE or copy the RES, INDEX, Mdedia Database (MM folder)
3). From the command line NSRADMN -d (Path of the lic)
4). Delete the lic (since this will be the same as your production
server).
5). enther the new auth code.
6). Start the server.
>From here on
Only copy the Index and MM folder on regular basis.
Any time a new client is created on the production server make sure you
create the client with the same client ID on the dev/DR/standby. This
will ensure the media and client indexes are in SYNC.
Now will have 2 identical systems if on goes down you can use the second
one.
coming to your question 3 How will the AD react?
I believe you have to delete the old Server from AD. B/C no 2 Servers
cvan have the same name unless the FQDN is different.
Hope this helps
cheers
Venkat
On Fri, Jan 15, 2010 at 6:02 AM, John Hope-Bailie
<johnhb AT demanddata.co DOT za> wrote:
We will be implementing a standby NetWorker server in a Windows 2008
environment.
The simplest approach seems to be to have only the device zoning
preconfigured on the standby server and when the fail-over is actioned,
to do the following :-
1) Rename the standby server hostname to the production NW server
name
2) Set up the correct IP config on the standby server (match that
of the powered down production NW server)
3) Install NetWorker on the standby server
4) Run mmrecov
5) Go into production.
We would like to simplify and automate this process as much as possible.
Some ideas and concerns have been as follows.
1) Use a "floating" TCP/IP name/address alias as the NW server
name. This might be easier and quicker to work with in the failover
sequence. I have has feedback that this can cause serious problems
during MS-SQL client restores (go figure ??). Unless you insert an
entry for the actual hostname of the NW server into the hosts file of
the SQL client, the restore fails. Any comments ?
2) Have the NW server code pre-installed on the standby server.
This would allow you to simply start the services at failover time and
not have to install NetWorker.
3) I am not sure how the issue of having the NW server installed
into the AD domain is relevant (or not). If you shut down the active NW
server, and then start up and rename the standby server, does this
require that the original server be removed from the domain, and the
renamed server be installed into the domain ?
Any help or comments would be welcome.
Regards,
John Hope-Bailie
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
--
Venkat Tudi
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
|