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. Veritas NetBackup™ in Highly Available Environments Administrator's Guide
  3. About site disaster recovery with catalog backup and recovery
  4. About catalog recovery
  5. About full catalog recovery
Veritas NetBackup™ in Highly Available Environments Administrator's Guide

About full catalog recovery

Full catalog recovery is primarily used to recover the catalog if the data is corrupted or storage is lost at the production site. Full catalog recovery is recommended for single domain configurations. Full catalog recovery is used if the DR site has the same number of media servers with the same names as those used at the production site.

Full catalog recovery has the following advantages over partial catalog recovery:

  • It restores the relational database components, which include the storage unit definitions, media assignment, and history.

  • It retains the tape information from the primary site including the media pool and other assignment information.

  • It restores the BMR data.

  • It enables backups to be run at the DR site using the same policies and tapes that are used at the production site.

With full catalog recovery, there are the following limitations:

  • When you recover the relational database components, the device configuration and the server configuration set up at the DR site before recovery is lost. You must set it again after recovery. The information that exists in the relational database about production servers and devices may not exist at the DR site. To ensure smooth operation in the DR environment, these server entries must be disabled and the devices associated with them should be removed.

  • Full catalog recovery overwrites the device configuration and the server configuration in the relational database. You must rediscover the DR domain server and device configuration after the catalog is restored.

Feedback

Was this page helpful?
Previous

About catalog recovery

Next

Performing full catalog restore

Feedback

Was this page helpful?