|
Re: [Networker] Changing networker server
2011-07-18 08:38:03
On 07/18/11 15:14, Preston de Guise wrote:
Solaris 9, Networker 7.5.2
Due to various circumstances we are looking at upgrading our current server sun
v440 with a sun v890. The intention is to keep the same host name and I.P.,
although I know the host ID would change. We are also looking to upgrade to
Solaris 10.
Any hints or ideas would be greatly appreciated.
If the host ID is going to change, you'll need to do a license transfer with
EMC. Organise the new licenses prior to doing the transfer.
I'd recommend installing Solaris 10 on the new host first, then transferring
NetWorker afterwards. Probably no main reasons other than how I've always done
it in the past when there's been a combined server move + OS upgrade.
The actual transfer of the /nsr region should be pretty simple. Optimally you
might be able to literally transfer the hard drives from one server to the
next. If not, you may have to look at an approved copy method. The EMC
recommended process is to do a bootstrap backup/recovery (i.e., mmrecov). I'm
not 100% sure whether that's literally required now when moving servers on the
same platform; check with EMC support to confirm whether it's definitely
required, as I've seen instances in the past where people have moved their
server details the 'wrong' way, and caused themselves major issues.
I have been upgrading Networker from different hardware and OS
versions (always Solaris on Sparc) and Networker versions and always
kept my /nsr the same (I never recovered the configuration). When there
was a need to copy things to a different server or disk, I just did
rsync (with a last rsync when Networker is down). When you bring
Networker up on the new server you just need to get new auth codes for
the new hostid (I think there is a 15 days grace period). So the step I
would do (and done in the past) are:
. rsync /nsr from the old server to the new one.
. Bring down Networker on old server.
. rsync /nsr from the old server to the new one to catch deltas.
. Install Networker on new server (if you already installed on the
new server, just bring Networker down and mv /nsr elsewhere before you
start the rsync).
. Reconfigure hardware (which was probably changed). You need to
delete jukeboxes and devices and reconfigure them.
The above will bring you all configuration to the new server. That
includes indexes, client configuration and media databases (and logs as
well. I still have logs from 2003).
For rsync you should use the following:
rsync -v -rptgo --delete /nsr v880:/nsr
(don't use -a, the --delete is important, or you will end up with
expired indexes)
Cheers,
Preston.
--
Preston de Guise
http://nsrd.info/blog NetWorker Blog
http://www.enterprisesystemsbackup.com "Enterprise Systems Backup and
Recovery: A corporate insurance policy"
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
--
-- Yaron.
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
|
|
|
