You have migration guide available with steps on Powerlink KB - you can use that one. That guide also discusses if new server will have the same or different name than original server.

Be sure to check the Release notes and the Installation manual for 7.5x details of upgrade path, requirements, gotchas etc.

Also on Powerlink there is a new tool called the "Networker Procedure Generator"
Currently the only procedure it has is how to do Upgrades.
You enter in details of your environment and it generates a detailed procedure

Find it on Powerlink
Home > Support > Product and Diagnostic Tools > NetWorker Procedure Generator

I used the following method:

Treat the old server as "broken"
So you have to do an Disaster/Recovey of Networker on the new Server with MMRECOV

0) write down your latest bootstrap ID
1) Disconnect old server form network
2) Give new server same name and ip-addres
3) Install same Networker version and patches on new server
4) Make backupmedium available to new server
5) Use MMRECOV on new server
6) check everything
7) If OK than Upgrade to latest version

Its also in DISASTER/RECOVEY GUIDE
kind regards

Thanks for your help but i still not have a complete solution.
Must I go step by step: Install a new server with windows 2000 and Networker 7.2 and then upgrade to windows 2003 and to Networker 7.5.
Or can I install directly Windows 2003 and Networker 7.2 on the new server and perform the restore procedure?
If this can be done it would be great. I can then upgrade to 7.5.
Thanks

Message was edited by:
condor

You can go directly to win2k3. Actually, if the name would be the same you could just copy over databases. Your sid will change so you will need to do host transfer. And you wish to use 7.5SP1 and not 7.5. Make sure you have update enablers ready as well.

Go directly to Windows 2003, And yes like Hrvoje said, you have to do an host transfer (via powerlink).

kind regards