So here's what EMC told me:
> Migration Steps
> 1> take a copy of mm, res and index from BACK001 and copy on some
locations on OTHER.
> 2> Shutdown BACK001
> 3> ensure That host file of OTHER does not have entries for both BACK001
and OTHER
> 4> Change the system name of OTHER to "BACK001" .
> 5> Install networker software
> 6> stop networker services
> 7> Now replace mm, res and index folder from backup of BACK001
> 8> start networker ("nsrexecd; nsrd")
> 9> deleted old library and device configuration and create new library
> 10> did a test recovery of BACK001
> 11>Stop networker services
> 12> rename the hostname back to OTHER
> 13> Now run a test recovery of OTHER.
> 14> Call licensing team and get you new hostid register for all your
licenses.
Now, in my case, since these machines are all Windows, I will have to stop
NW and rename BACK001 to something else, at step 2.
And a similar reboot, at step 12.
But this should avoid an hours-long mmrecov, and it means that OTHER
should only be unavailable for a short amount of time, while it is
temporarily named BACK001 (OTHER is a file server, and for our Executive
department, who seem to like to work on Sat ...).
I've been looking over this, and it seems that it should work. The only
problems that I foresee is waiting for the name change to propogate from
DNS and Active Directory, to the rest of the domain. And then the same for
the rename back.
Anyone see anything I (or EMC) has missed?
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
03/16/2010 09:09:31 AM:
> I have a NW 7.4.5 server, running on BACK001; it has a client named
OTHER.
> What I need to do is to move the Networker server from BACK001 to OTHER.
> I've recovered a NW server before (i.e., mmrecov, rename the res
> directory, nsrck -L7, etc), but the new one had the same name as the old
> one, in that case. Here, I need to do a D/R recovery to a machine with a
> different name (an existing name), and I am unsure of the steps
involved.
> I need to make sure I have all the old history of backups of OTHER
> available for recovery, as OTHER is a file server for that site.
>
> I am reading through the D/R guide, but am still unclear. The clientIDs
> should not change (since they are existing installations), but I can't
> figure out what will happen when an existing client now becomes the
> server, and the server goes down to just being a client.
>
> Pointers appreciated.
>
> --
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 2500 Jackson St
> Philadelphia, PA 19145
> Tel: 215-684-4180
> Cell: 215-252-0143
> <mailto:michael.leone AT pha.phila DOT gov>
>
> 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
|
