We've done it this way 3 times over the years (using Networker since
1994). Just keep the old server around for a while if you need to do
restores from it. We keep a database separate from Networker of the
archives and other long term data storage so we only care about
Networker keeping the last 3 months worth of data.
Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Randy Doering
Sent: Tuesday, March 04, 2008 11:00 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Upgrading Networker & moving to a new server
Some good suggestions in there. Another way to do it, if you are moving
to a new tape library as well, is how we did this a couple of years ago.
Forget about upgrading anything. Just retire/shutdown your old server
and start from scratch on the new platform. You'll need to get your
enablers transferred, but that shouldn't be much.
Once you get the new environment setup, just don't bring both the old
and the new online at the same time, or they will disable themselves.
Worked well for us as the old equipment was going back at the end of the
lease, and we had plenty of time to get the new environment in place
well before the old retentions were reached.
Randy
----- Original Message ----
From: Steve Harris <steve AT COMP.LEEDS.AC DOT UK>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Tuesday, March 4, 2008 6:11:58 AM
Subject: [Networker] Upgrading Networker & moving to a new server
Morning all,
We are running Networker Server version 6.x on an old, but maintained,
server and now wish to move to new hardware and upgrade to Networker
7.4.
I am thinking we need to upgrade to 7.4 on the old server before
transferring to the new hardware, but have a few questions:
. should we be able to get an enabler to go straight from 6.x to 7.4
or is it advisable to go through stages. (We have been on
maintenance
throughout but currently only have the enablers to 7.1)
. I have read somewhere that do not need an enabler to move to new
server hardware if you are maintaining the same hostname and IP
address, is this the case?
. Is it possible to restore the client indexes if the server
architecture is changing, or do the tapes need to be re-scanned
using scanner?
(We have successfully tested recovery of the media data from a
backup created using 'savegrp -O')
Please no flaming about running a old versions of Networker. One has
to fix the broken before getting to fix the working but old!
Many thanks for any advice
Steve
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
-------------------------
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
|