Veritas NetBackup™ in Highly Available Environments Administrator's Guide
- About in this guide
- NetBackup protection against single points of failure
- Protecting against component failures
- Storage device connection failures
- Media server failures
- Protecting against component failures
- About site disaster recovery with catalog backup and recovery
- About catalog recovery
- About disk recovery in DR domain
- About site loss protection with auto image and catalog replication
- About NetBackup catalog replication
- About multi-site single domain replication
- About multi-site cross domain replication
- About full catalog replication
- About partial catalog replication
- Deploying NetBackup master servers with full catalog replication
- About non-clustered NetBackup master server with catalog replication
- About globally clustered NetBackup master servers with catalog replication
- Installing and configuring a globally clustered NetBackup master server with catalog replication
- 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 master 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 EMM database.
This approach assumes that NetBackup is installed but not running on the secondary master server and the media servers in the DR domain. Also, the secondary master 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:
- Ensure that replication between the primary and the secondary sites is stopped.
The replication is stopped if the primary master server is unavailable or if the replication link is disabled.
- Mount the replicated volume to the appropriate mount point on the secondary master server.
- 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/nbemm - maintenance
On Windows master servers start the following Windows services:
NetBackup Relational Database Manager
Veritas Private Branch Exchange
NetBackup Enterprise Media Manager
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 <Master 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
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, you can deactivate all backup policies to prevent backups from starting automatically.
You can deactivate the backup policies manually using the NetBackup Administration Console.
Or run the bppllist <policy> -set -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.
- 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 client data that is backed up at the production datacenter.