How to replace the server hardware for a NetBackup media server without completely decommissioning the media server

Problem

How to replace the server hardware for a NetBackup media server without completely decommissioning the media server

Solution

It is sometimes necessary for a customer to replace the hardware they use for their media server. For example it may be necessary to replace a 32 bit media server with a newer model 64 bit media server. In most cases this just involves replacing the existing media server with a newer machine of a similar type but a higher specification and can be accomplished without assistance from Veritas Consulting Services. The following steps are required when replacing the hardware for a media server:

1. Set the media server to inactive through the administration GUI, by going to Media and Device Management > Devices > Media Servers, right clicking on the required media server and selecting the deactivate option, or by running the nbemmcmd command with the following options from the master server:
   • nbemmcmd -updatehost -machinename <Media Server> -machinestateop set_admin_pause -machinetype media -masterserver <Master Server>
   • If the media server forms part of a cluster, the cluster should be frozen.
2. Make a note of the media type of any tape drives presented to the media server and the number of any robot that is controlled by this media server, then delete any tape device and robotic control records (including VTLs) related to the media server.
   • a. Drives can be deleted using the administration GUI by going to Media and Device Management > Devices > Drives, right clicking on the appropriate drive and selecting the delete option.
     • Drives can also be deleted using the tpconfig command with the following options from the media server:
       tpconfig -delete -drive <drive index>
   • b. Robots can be deleted using the administration GUI by going to Media and Device Management > Devices > Robots, right clicking on the appropriate drive and selecting the delete option.
     • Robots can also be deleted using the tpconfig command with the following options from the media server:
       tpconfig -delete -robot <robot number>
   • c. For MSDP, save the configuration parameters to a file by running the following nbdevconfig command:
     nbdevconfig -getconfig -storage_server <MSDP_NAME> -stype PureDisk -configlist /path/filename
     • Ensure to validate '/etc/pdregistry.cfg'
     • Ensure directories remain intact.
3. Shut down the old server and disconnect any storage devices.
4. Provision a new server with the same host name and IP address (a different IP address provided DNS is updated but the host name must not be changed) and connect any storage devices to it.
5. For BasicDisk and AdvancedDisk, ensure that any disk backup storage is presented to the new media server using the same mount points as the old media server.
6. OpenStorage users should ensure that they have the appropriate plug-in for the platform and version of NetBackup they are running.
7. Install the same version of NetBackup on the new media server making sure to specify all the servers known to the old media server.
   • If the media server encryption option (MSEO) is used, the MSEO media server agent must also be installed.
   • If the media server forms part of a cluster ensure the clustering software is installed and the cluster is configured correctly.
8. Set the new media server to active through the administration GUI, by going to Media and Device Management > Devices > Media Servers, right clicking on the required media server and selecting the activate option, or by running the nbemmcmd command with the following options from the master server:
   • nbemmcmd -updatehost -machinename <Media Server> -machinestateop clr_admin_pause -machinetype media -masterserver <Master Server>
9. Run the device discovery wizard (Configure Storage Devices) from the Administration GUI on the master server to discover the tape and robotic control devices on the new media server. Confirm that the media type of any tape devices matches the media type of the tape devices as configured on the old media server and that the robot number of any robot controlled by this media server is the same by viewing the properties of each device and modifying it if necessary.
   • For MSDP, recover the configuration parameters saved in step 2c. above by running the nbdevconfig command:
   • nbdevconfig -setconfig -storage_server <MSDP_NAME> -stype PureDisk -configlist /path/filename
10. Run some test backups and restores (including restores from backups made using the old media server hardware) through the new media server to confirm it is functioning correctly.

Note: Please refer to the NetBackup Documentation (Administration Guides and Command Guides) for more details on changing device media types and robot numbers from the command line, or command syntax.

The nbemmcmd and nbdevconfig commands are located in the following path:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd
Windows: <install path>\Veritas\NetBackup\bin\admincmd

The tpconfig command is located in the following path:
UNIX/Linux: /usr/openv/volmgr/bin
Windows: <install path>\Veritas\Volmgr\bin