Veritas 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 NetBackup 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 environment with partial catalog replication
In the event of a loss of the source master server (or during a disaster recover test) follow these steps:
- Ensure that replication between the primary and the secondary sites is stopped.
Replication stops 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.
- Use the command nbdb_admin - vxdbms_nb_staging <directory> on the target (disaster recovery) master server to point the staging area for the relational database to the location on the replicated storage.
- Run the command cat_export - all - staging to export the metadata from the replicated relational database backup.
- Run the command cat_import - all to import the exported metadata into the active relational database.
- Start NetBackup on the secondary master server.
- If the backup policies are replicated, 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 command bppllist <policy> -set -inactive .
- Ensure that the appropriate FAILOVER_RESTORE_MEDIA_SERVER settings are defined to direct restore operations through the media servers at the secondary site.
- In order to restore backups from tapes the tapes must be added to the disaster recovery master server's catalog by placing them in a tape library and running an inventory of the library. To prevent the tapes from being accidently overwritten the disaster recovery master server should have a bar code rule that adds the tapes to a volume pool that is not the global scratch pool and is not used by any backup polices. Ideally the tapes should also be physically write locked.
- For disk based backups, the storage servers and disk pools must be added to the disaster recovery master server by running the disk storage server wizard.
Once the disk storage is present, run the following command to reconcile the disk media IDs:
nbcatsync - backupid <catalog backup ID> -prune_catalog
The value <catalog backup ID> is the backup ID of the most recent catalog backup and can be found in the catalog backup's disaster recovery file. Once the tapes have been added and the disk media IDs have been reconciled it is possible to start restore operations