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).

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

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.

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).

> And to answer your actual questions:
> Yes. The config will stay exactly the same.
>
> 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