Performing full catalog restore
With full catalog recovery the complete catalog backup is recovered to the DR master server. The media servers that do not exist in the DR environment are deactivated to avoid unnecessary pooling. All device records are removed because the device configuration at the DR site can be different to the production site. Device discovery is run to update the EMM database. You must perform the following procedure before restores can be started. Also, document the procedure in your DR plan.
To prepare for full catalog restore
- On UNIX and Linux master servers, create copies of the
bp.confandvm.conffiles. - Run the bprecover command to recover the entire catalog.
Note:
The DR master server must have the same name and topology as the production master server. If the production master server is a cluster then the DR master server must also be a cluster. The number of member nodes and the names of the nodes can be different.
Note:
If a catalog backup that was created on a separate media server is used, then a media server with the same name is required for the catalog recovery.
- After you run the bprecover command, set a passphrase for disaster recovery package for the subsequent catalog backups to be successful.
- During catalog recovery, security certificates for cluster nodes are not recovered. Only the virtual name certificate is recovered.
- Clear white list cache and restart the service on all hosts in the domain.
- Deactivate all the backup policies to prevent backups from starting automatically.
You can do this manually using the NetBackup Adminstration Console.
Or run the bpplinfo <policy> -modify -inactive CLI.
- Shut down NetBackup.
- On UNIX and Linux master servers, replace the
bp.confand thevm.conffiles that were restored from the catalog backup with the copies created in step 1. - Start the NetBackup Relational Database Manager, NetBackup PBX, and EMM services on the new master server.
On UNIX and Linux master servers, run the following commands:
/usr/openv/netbackup/bin/nbdbms_start_stop start
start /opt/VRTSpbx/bin/pbx_exchange
/usr/openv/netbackup/bin/nbemm
On Windows master servers, start the following Windows services:
NetBackup Relational Database Manager
Veritas Private Branch Exchange
NetBackup Enterprise Media Manager
Note:
The PBX process may already be running because the NetBackup commands do not stop and start PBX.
For more information about NetBackup Relational Database Manager service, see the NetBackup Troubleshooting Guide.
- Deactivate the media servers that are not part of the DR environment. Run the following command:
nbemmcmd -updatehost -machinename <Media Server> -machinestateop set_admin_pause -machinetype media -masterserver <Master Server>
- Delete all the tape devices from the EMM database. Run the following command:
nbemmcmd -deletealldevices -allrecords
- Restart NetBackup.
- Using the Device Configuration wizard create the new tape drive and library configuration.
- If bar code masking rules were used at step 9, ensure that the same rules are set here. If necessary, add them.
- Using the NetBackup Adminstration Console, verify if all the recovery media are set to non-robotic.
If some recovery media still need to be set to non-robotic, do the following:
Select the robotic media, right-click and select Move.
Change the robot field to Standalone.
Click OK to save the changes.
- Once all the recovery media are set to non-robotic, in the Inventory all the tape libraries field ensure that the media are identified in the correct library.
You can now start restore and recovery operations of the client data that is backed up at the production datacenter.