This section describes the case where your original Backup server is beyond repair, so you want to move Backup to a new server. This procedure assumes that you are not updating the operating system or the Backup software.
Do not make major changes to the operating system or Backup software at the same time you move to a new server.
If you want to make changes to the operating system or the Backup software, configure the new server exactly like the original, using the same version of the operating system and Backup software. After configuring the new server, make sure the system is operational, perform a couple of successful backups, and then update or upgrade the operating system or the Backup software, one at a time.
To move Backup to a new server, use the same steps for recovering the operating system and Backup software, including the indexes and configuration files. Follow the instructions in these sections:
However, you should be aware of the following requirements for configuring and registering the software:
Use the same hostname for the new Backup server. You must use the same hostname because the server indexes were created under the original Backup server name.
Make sure the original server name is listed as an alias for the server in the Client window of the nwadmin program.
If the new server has a different host ID, you need to reregister the Backup software.
After you move the Backup server to another system, you must recover the resource database (nsr.res file) to ensure that you carry over the same resource and attribute settings to the new Backup server.
If the new server has a different host ID, you have 15 days to reregister the software with Sun. Refer to the Solstice Backup 5.1 Installation and Release Notes.
Sun will send you a Sun Backup Host Transfer Affidavit, which you must complete and return. Once Sun receives the signed affidavit, Sun sends you a new authorization code to enter into the Auth Code field of the Registration window.
After you successfully move your server, check the following:
Verify that the server and all the clients are included in a scheduled backup.
Schedule a full backup or use the savegrp -O command to back up the server and all the clients as soon as possible. (Manual backups do not back up the server or client indexes.)
Use the nwrecover program's window Recover window to make sure all the client indexes are browsable and, therefore, recoverable.