Once again - mmrecov is a DR tool. In such case, you are not supposed to change 
anything but bring the machine up to the pre-disaster state a.s.a.p. mmrecov 
will not work with a new hostname as the old name will be missing.

As mentioned already, the hostid on Windows is bound to the SID and has nothing 
to to with the hostname and the IP. It will only become affected when you 
install a new OS. On the other hand, you can also set a SID (via sysinternal 
tools). Licenses will not become affected due to another SID, but the hostid - 
consequently you need now auth-codes (which you can get online).

Moving a NW server to a new system/OS/hostname/IP is possible in principle, but 
it is not easy and not straight forward. This is why no general procedure 
exists. If you are in doubt, look for a consultant or even better: make your 
own tests and see how NW works.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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