NetBackup™ in Highly Available Environments Administrator's Guide
- About in this guide
- NetBackup protection against single points of failure
- About site disaster recovery with catalog backup and recovery
- About site loss protection with auto image and catalog replication
- About Auto Image Replication (AIR)
- About NetBackup catalog replication
- Deploying NetBackup primary servers with full catalog replication
- About replication considerations
- About non-clustered NetBackup primary server with catalog replication
- About globally clustered NetBackup primary servers with catalog replication
- Installing and configuring a globally clustered NetBackup primary server with catalog replication
- Populating the server tables in the NetBackup database
- Upgrading NetBackup in a clustered replication configuration
- Failing over to an alternate primary server cluster
- Testing the NetBackup primary server cluster in clustered replication environment
- Using NetBackup to perform backups and restores in a cluster
Recovering the catalog with full catalog replication
With full catalog replication, complete catalog backup is recovered to the DR primary server. The media servers that do not exist in the DR environment should be deactivated to avoid unnecessary pooling. Since the device configuration at the DR site is likely to be different to the production site all device records are removed. Further, device discovery is run to update the NetBackup database.
This approach assumes that NetBackup is installed but not running on the secondary primary server and the media servers in the DR domain. Also, the alternate primary server and the media servers are configured to communicate with each other.
Before restores can be started, carry out the following procedure to prepare for full catalog restore. You must document this procedure in your DR plan:
To recover the catalog with full catalog replication
- Ensure that replication between the main and the alternate sites is stopped.
The replication is stopped if the main primary server is unavailable or if the replication link is disabled.
- Mount the replicated volume to the appropriate mount point on the alternate primary server.
- Start the NetBackup Scale-Out Relational Database Manager, NetBackup PBX, and EMM services on the new primary server.
On Linux primary servers run the following commands:
/usr/openv/netbackup/bin/nbdbms_start_stop start
/opt/VRTSpbx/bin/pbx_exchange
"/usr/openv/netbackup/bin/nbemm - maintenance
On Windows primary servers start the following Windows services:
NetBackup Scale-Out Relational Database Manager
Veritas Private Branch Exchange
NetBackup Enterprise Media Manager
Note:
The PBX process may already be running since it is not stopped and started by the NetBackup startup and shutdown commands.
- 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 primary_server
- If any media servers in the DR domain have the same names as media servers in the production domain, delete all tape devices from the EMM database. Run the following command:
nbemmcmd -deletealldevices -allrecords
Note:
This step resolves possible device configuration conflicts on media servers. Skip this step, if the media servers in the DR domain have different names to those of the media servers in the production domain.
- Restart NetBackup.
- Optionally, deactivate all the backup policies to prevent backups from starting automatically. Use one of the following methods:
The NetBackup web UI.
Run the bpplinfo <policy> -modify -inactive CLI.
- Register the media servers that form part of the DR environment in EMM by starting NetBackup on each media server.
- Using the Device Configuration Wizard, create the new tape drive and library configuration.
- Verify that 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 client data that is backed up at the production datacenter.