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
About full catalog replication
In full catalog replication, all parts of the catalog are replicated to the alternate primary server. In full catalog replication, the tape information from the production domain, the media pool, and other assignments is retained. Backups can be run in the DR domain using the same policies and tapes that are used at the production domain. The replication can be reversed, which simplifies a transition back to the production domain. However, replicating the database components implies that the device configuration and the server configuration of the production domain is replicated to the DR domain. This configuration information cannot be used and the configuration in the DR domain must be discovered after recovery.
Full catalog replication is not recommended for cross domain replication.