Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ in Highly Available Environments Administrator's Guide
  3. About site disaster recovery with catalog backup and recovery
  4. About catalog recovery
NetBackup™ in Highly Available Environments Administrator's Guide

About catalog recovery

A major problem that users encounter during site disaster recovery is that the disaster recovery (DR) site is not a mirror image of the production site. To perform DR operations you need a copy of the NetBackup catalog from the production primary server. NetBackup catalog backups are primarily intended for recovering from catalog storage or primary server failure rather than site loss. The default scenario is that NetBackup restores the complete catalog including the NetBackup database. Primary servers use the catalog information to direct backups and restores, query the media servers, and establish the status of the backup devices. In a DR environment which does not contain these media servers, the performance of the primary server can be affected. Also, the ability to carry out restore operations can be affected, as polling operations fail to connect and time out.

Note:

In a cluster setup, if you use external CA-signed certificates for host communication, ensure that the virtual name and the cluster nodes have the same certificate authority (CA) usage. For example, if a node uses only external CA-signed certificates, ensure that the virtual name also uses external CA-signed certificates. If there is a mismatch in the CA usage of the virtual name and cluster nodes, catalog backup and catalog recovery may fail.

Use the following approaches to recover the NetBackup environment at a DR site where the arrangement of media servers and clients is different from the main production site. Both approaches have advantages and disadvantages.

  • In the full catalog recovery approach the whole catalog is recovered and then unwanted configuration elements can be removed or disabled.

  • In the partial catalog recovery the NetBackup database is not restored.

    See About partial catalog recovery.

The most appropriate method for recovery can be determined by the nature of the DR facility and how similar it is to the production facility.

When creating your disaster recovery plan, ensure that it is in line with the approaches discussed in the following sections:

  • See Planning a cross domain replication disaster recovery domain.

  • See Performing full catalog restore.

  • See Performing a partial catalog restore.

More Information

About full catalog recovery

Feedback

Was this page helpful?
Previous

Disaster recovery packages

Next

About full catalog recovery

Feedback

Was this page helpful?