All I did when I migrated from 7.2 on Windows 2003 to 7.6.1 on Windows 2008 R2 
x64 was copy the files over.  No mmrecov involved.

Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Joe N. Wallace
Sent: Wednesday, June 15, 2011 5:06 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Migrating Networker 7.4.5 from win 2000 to win2003

I'm going to be involved in migrating Networker 7.6.1 on Windows server 2003
x86 to Server 2008 R2 x64 with a new hostname and IP address

Will it be possible to use mmrecov in such a scenario? When both hostname
and IP address will change?

Does perhaps only matter for the license? I expect that I could get that
resolved with licensing AT emc DOT com. But I rather not have problems with the
media db and the resource files.

Regards,
Wallace

2011/6/14 Dag Nygren <dag AT newtech DOT fi>

> > On Monday 13 June 2011 08:08:14 Dag Nygren wrote:
> > > söndag 12 juni 2011 18:01:56 skrev  jee:
> > > > Kurianv
> > > >
> > > > for the migration you need to perform a DR procedure and not a copy
> of
> > > > media db and config files. Then you need to rename the target server.
> > >
> > > Not necessarily. IF the byte ordering is the same on the servers a
> plain
> > > copy will work fine. (Providing the same sarver name) It is not the
> > > supported way, but you are out of support with your version anyway :-).
> > > And I have yet to see it fail.> .
> >
> > A plain copy may fail.   Actually a cross platform migration can be safer
> > than a mere copy of files if the media db is exported/imported using the
> > right tools.  However that procedure is not officially supported
> (although
> > that wouldn't matter here).
>
> A plain copy will fail if the source and the target have different
> byteordering. Otherwise it will work.
>
> > > Just follow the procedure outlined in a previous answer. Except from
> the
> > > fact that you can copy mm and index too and save the trouble of
> > > recovering the indexes from tape. And don't forget to bring down
> > > networker on the source before you copy :-)
> >
> > The best method is the DR. It is clean and well organized. It is there
> for
> > a good reason. running mmrecover+ nsrck  following the right procedure is
> > not trouble. It avoids getting into it.
>
> Yes. This is the ONLY method that takes care of byte ordering. But very
> often
> we are talking x86 to x86 migration.
>
> > Copying the media db, res etc is ok for test servers but it should never
> be
> > recommended on production systems. I don't mean it won't work. I mean it
> > may fail.
> >
> > > > However if you move the server to other HW, the HostID will change
> and
> > > > you will need to register the existing base enabler (ot a new one)
> with
> > > > a new authorization code.
> > >
> > > As this is a Windows machine the host-ID is derived from the primary IP
> > > of the server and so even your authorizations will stay OK if your
> > > network setup is the same.
> >
> > That's not strictly correct. The hostID on a windows machine is based on
> > the SID and not on the IP. The HostId may change after a reinsallation of
> > the OS or hardware on the host even if the primary IP is the same.
>
> This depends on the version of Networker you are using. Earlier Networker
> versions used the IP address and the newest versions (7.4 -> ?) seems to
> use
> it. There was an intermediate period when the SID was used (but not in
> upgrades, only new installs)
>
> > However there is a workaround and it is possible to define and force a
> > HostID based on the server IP (using the HEX representation of the IP --
> > without the dots.). I  haven't used this for a long time but there was an
> > old  tech note that explained how to do this ( I don't remember the
> > details).
>
> Yes. That was for that intermediate versions.
>
> Best
> Dag
>
> 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