I'm assuming Windows...
1) The new master server absolutely *must* have the same name and IP address - so both can't exist at the same time.
2) If your catalog for the old master is on SAN storage, do not disturb it, this is your fall back point.
2a) Make detailed notes about your existing cabling - all copper, fibre and SCSI if you have any. Maybe take photos too, if you're allowed.
3) Do don't make any changes whatsoever to the old master server, this is your recovery point.
4) Wait for all backups/duplications to complete.
5) Make a note of your scheduling (bpconfig -L).
5b) Disable scheduling (bpconfig -tries 0)
6) Perform two catalog backups - to two different media - remember to configure two different media in the catalog menu option first.
7) Make a note of the media numbers.
7a) Make a note of values used in any SIZE_DATA_BUFFERS, NUMBER_DATA_BUFFERS, NET_BUFFER_SZ and any of the _REST and _RESTORE settings too. (Research where these files live).
7b) Save a copy of your bp.conf (actually in registry for Windows), but you can dump it with (bpgetconfig -M $master > old.lis) - save this file for comparing later.
7c) Save a copy of vm.conf (Research where this file lives).
7d) Do you have a no.restrictions file? altnames entries?
7e) Do you use drive_error_threshold and/or media_error_threshold files?
8) Shutdown the old master. Physically disconnect from network, in case someone mistakenly boots it or it receives a WOL - as you definitely do not want two masters with same name and same IP on your network - then you really will be in a mess.
9) Boot your new server and install O/S, and join domain. Reboot.
9b) If your master uses SAN storage, do not use the old volumes, create some new storage.
10) Install O/S patches. Reboot.
11) Shutdown server. Attach to SAN (or SCSI). Boot.
12) Install library and tape drivers as required. Reboot.
13) Install NetBackup v5.1 GA. Reboot.
14) Instal NetBackup v5.1 MP7. Reboot.
15) Run device configuration wizard.
16) Perform a catalog recovery.
17) Reboot.
18) Run device configuration wizard.
18b) Recreate any special configuration files noted above.
18c) Take a "bpgetconfig -M $master > new.lis" and compareto "old.lis" - any differences? Changes required?
18d) Compare old and new vm.conf - changes required?
19) Inventory your robots.
20) Use the "catalog" GUI function to browse for old and lastest backups - are they listed/known in the catalog?
21) Peform a restore of one file from a client, restore to a temp area on your new master. Did it work?
22) Create a test policy.
23) Run some test backups from the test policy. Did they work?
24) Enable scheduling (bpconfig -tries N) (whatever you noted from step 5).
Beware that this list is by no means exhaustive/complete/accurate or useful. Flesh it up as you see fit.
Anyone else have any pointers/gotchas/workarounds or a simpler process?
