Updating NetBackup after changing the host name
Do not change the host name of a NetBackup server. A name change might require that all previously used media be imported to the server before the host can be used under the new name.
Use the following steps to update the NetBackup configuration if a client's host name is changed.
To update NetBackup after a primary server name change | See “To update NetBackup after a primary server name change”. |
To update NetBackup after a client name change |
To update NetBackup after a primary server name change
- On the primary server, delete the client's old name from all policies where it exists and add the client's new name to those policies. You do not need to reinstall NetBackup software on the client. The client continues to have access to all previous backups.
- (On UNIX) Create a symbolic link from the client's old image directory to its new image directory. For example,
cd /usr/openv/netbackup/db/images ln -s old_client_name new_client_name
- (On Windows) Create a file named ALTPATH in the image catalog directory.
For example, if the client name is client1, the ALTPATH file is created in the following location:
Install_path\VERITAS\NetBackup\db\images\client1\ ALTPATH
- (On Windows) Create a directory for the new client2 in the \images directory:
Install_path\VERITAS\NetBackup\db\images\client2
- (On Windows) On the first line of the client1\ALTPATH file, specify the path to the directory for the new client. The path is the only entry in the ALTPATH file.
Install_path\VERITAS\NetBackup\db\images\client2
To update NetBackup after a client name change
- On PC clients, change the client name setting either through the user interface or in a configuration file.
See the online Help in the Backup, Archive, and Restore client interface.
- On UNIX clients, change the CLIENT_NAME value in the bp.conf file to the new name.
If users on UNIX clients have a bp.conf file in the $HOME directory, users must change CLIENT_NAME in that file to the new name.