As far as upgrading, right now 7.2.2 works great for us and I like only
making one change at a time. I expect we'll do an upgrade to 7.3 or 7.4
some time next spring when we implement AFD.
Just to clarify some things. The new server has a different name and IP
address from the old server. Those are things I can't change since the
old server has other software on it that I can't change at this time.
Our set-up is pretty small. One Networker server and 11 Windows clients,
1 Solaris client and 1 MS Exchange client. A full backup is around
500GB right now and grows by 20GB or 40GB a month.
Thanks, Dave
David Werth
Garmin AT, Inc
Salem, Oregon
dave.werth<at>garmin.com
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Fazil Saiyed
Sent: Wednesday, November 21, 2007 6:18 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Moving my Networker Server
Hello,
Seems like an ideal opportunity to upgrade to 7.3.3 platform, besides
following the steps in DR guide, one approach that is quite simple and
works fine is as follows. ( Not something that would be recommended by
some folks or emc but nevertheless works just as well). I still
recommend
full backups of old server with Full index backup also for any event of
failover, issues.
1. copy old nsr directory to new server, after you shut down all
networker services on original server.
2. Shut down old server, remove from domain, keep it off the network
etc.
3. Rename the new server name to old and move it to domain, match IP
properties, nslookup, etc.
4. Install new networker version on top of old nsr directory, which you
copied in step 1 ( any location you like on the server)
5. You will have to be careful about how you specified original index in
the client attributes, if it calls for D:\nsr\index then that's where
you
should do initial install, if you did not specify index directory in
client attribute, moving it to C should not be a problem.
6. Start networker services, resync the hardware, you may have to redo
jbconfig, since the drivers etc would have changed
7. Move your host file, double check your config etc ( along with step
one)
You should be up and running at this point, i believe this approach
could
work well even for DR if the nsr directory is replicated with proper
care,
this approach is similar to upgrading networker on the same server, no
need for mmrecov, nsrck etc, however as always , once the server is
successfully moved to new hardware you should run the index check & run
the full backup, test recover etc asap.
I am sure some folks would not like bypassing normal networker dr
routine, so get a second opinions and test it out.
HTH
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
-------------------------
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient. If you are not the intended recipient, please
be aware that any disclosure, copying, distribution or use of this e-mail or
any attachment is prohibited. If you have received this e-mail in error,
please contact the sender and delete all copies.
Thank you for your cooperation
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
|
