Using a primary server instance for disaster recovery
If a NetBackup primary server application instance is lost in a disaster scenario, you can create a new instance to recover the identity of the instance that was lost. To recover the instance identity, you need the following information:
The configuration details of the lost instance
The NetBackup disaster recovery package
For more information about the disaster recovery package, see the chapter "Disaster recovery" in the NetBackup Troubleshooting Guide.
To recover a primary server instance identity
- Create a primary server instance with the same configuration as the instance that was lost. During instance creation, select the option Use instance for disaster recovery.
- Open an SSH session to the instance. If you have not already, change the default password.
- Copy the following NetBackup disaster recovery files to a local folder on the instance:
PolicyName_XXXXXXXX_FULLPolicyName_XXXXXXXX_FULL.drpkg
- Run the following command to import the disaster recovery package:
sudo /usr/openv/netbackup/bin/admincmd/nbhostidentity -import -infile PolicyName_XXXXXXXX_FULL.drpkg
- Run the following command to start all NetBackup services:
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- From the NetBackup web UI, reissue a token for each associated media server and WORM storage server. Use the following steps:
On the left, click Security > Hosts.
Click NetBackup certificates.
Select the host and click Generate reissue token.
Enter a token name and indicate how long the token should be valid for.
Click Create.
- Add the media servers to the primary server's host properties. Use the following steps:
On the left, click Hosts > Host properties.
Select the primary server, then click Edit primary server > Servers.
For a media server with MSDP storage, navigate to the Additional servers tab and click Add.
For a media server with AdvancedDisk storage, navigate to the Media servers tab and click Add.
- Run the Catalog Recovery Wizard. For instructions, see the section "Recovering the entire NetBackup catalog using the Catalog Recovery Wizard" in the NetBackup Troubleshooting Guide.
- Once the catalog recovery completes successfully, run the following commands on the primary server instance to stop and start all primary server daemons:
sudo /usr/openv/netbackup/bin/goodies/netbackup stop
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- Log in to the media server instances and run the following command to stop and restart all media server daemons:
sudo /usr/openv/netbackup/bin/goodies/netbackup stop
sudo /usr/openv/netbackup/bin/goodies/netbackup start
- From the NetBackup web UI, navigate to Hosts > Host Properties. Select each media server and click Connect.
- On the left, click Storage > Media servers. Then click the Media servers tab. Select each media server and click Activate.
- Perform a backup and restore test to each media server to verify that everything is working correctly.