How to Move Your Backup Server License to a Different Machine

To move the Backup server license from one machine to another, follow these steps:

1. Use Backup to perform a full backup of all the filesystems on the old Backup server.

2. Shut down the Backup daemons on the old server, using the nsr_shutdown -a command.

3. Make a tar tape of the entire /nsr directory from the old server, and reload it on the new server.

   If /nsr is a symbolic link on the old server, make sure the new server has the /nsr symbolic link setup also.

4. Shut down your old server and disconnect all the devices.

5. Shut down the new machine, add the hardware devices to the new server, and restart both machines. Start up the old machine first, and then the new one.

6. Install Backup on the new server.

   If you have an autochanger, do not select the option to start the Backup daemons. Refer to the instructions in the Solstice Backup 5.1 Installation and Release Notes to learn how to install and test the Backup device drivers.

   Because you create a new host, you must correctly define the index entry for the new host before you start the Backup daemons. Correct the index entry using one of the two methods:

   • Name the new server with the same hostname as the old server at the operating system level before you modify client resources.

   • Create a new hostname for the new server with the same configuration choices as the old server.

   To create a new hostname for the new server, follow these steps:

1. Create a new hostname for the new server with the same configuration choices as the old server.

2. Delete the hostname entry for the old server.

3. Shut down the Backup daemons on the old server and the new server:

   # nsr_shutdown -a

4. Change to the directory containing the old server index entry:

   # cd /nsr/index

   The entry for the new server hostname is empty.

5. Delete the entry for the new server hostname:

   # rmdir new-hostname

   You must remove this entry or the next step creates a subentry for the new server instead of the correct entry.

6. Rename the old index directory to the new server hostname:

   # mv old-hostname new-hostname

   The Backup daemons start up on the new server.

   new-server syslog: Backup Server: (notice) started new-server syslog: Backup Registration: (notice) invalid auth codes detected. new-server syslog: new-server syslog: The auth codes for the following licenses enablers are now invalid. new-server syslog: The cause may be that you moved the Backup server to a new computer. new-server syslog: You must re-register these enablers within 15 days to obtain new codes. new-server syslog: new-server syslog: License enabler #xxxxxx-xxxxxx-xxxxxx (Backup Advanced/10)

   Reregister your new Backup server. After you move Backup from one system to another, you have 15 days to register the new server with SunSoft.

   To reregister your new server, refer to "How to Register and Authorize Your Software ".

   After you have successfully moved your server, follow these steps:

   1. Verify that all the clients are included in the scheduled backups.

   2. Use the Backup recover program to make sure all the client indexes are visible and, therefore, recoverable.

   3. Back up the indexes on the new server or perform a full backup of the new server as soon as possible.

   If you want to set up the old server as a client, first remove all the Backup software and the /nsr directory from the old server, then reinstall the Backup client software.