I would go from 6.1 to a pre 7.3 version. Say 7.2. You will need an
update enabler to activate. Once there you can then upgrade to 7.4.1.
Depending on how big your datazone is you could move the entire nsr file
system over to the new server with a different name and IP. Do not start
networker. Stop the old server and rename and re-ip. Now rename and
re-ip the new server to the original name. Start networker. You would
not have to recover any indexes this way. 

If a large datazone and the index and media db are large I would do the
mmrecov using the bootstrap. You can then use the new server name. Just
make sure you stop the old server so as to not get any licenseing
issues.  


EDWARD COTY
LEAD STORAGE ENGINEER, LCNA, NACP
WORK - 973-533-2098
CELL - 973-296-0918
EDWARD.COTY AT AIG DOT COM

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Stan Horwitz
Sent: Tuesday, March 04, 2008 7:22 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Upgrading Networker & moving to a new server

On Mar 4, 2008, at 6:11 AM, Steve Harris wrote:

> 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!

This is very important to know. What kind of server and OS are you
running now with 6.x? Your plan to update to 7.4 on the old hardware is
in general a good idea; however, be aware that 7.4.x requires a lot more
horsepower, so if your old server is not up to the task, you may find
that after upgrading from 6.x to 7.4 SP1, that it grinds to its knees.

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