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 partial catalog recovery
Veritas NetBackup™ in Highly Available Environments Administrator's Guide

About partial catalog recovery

Partial catalog recovery is recommended for multi-domain configurations. Partial catalog recovery is used for DR sites where the server layout is different from the production site with fewer media servers, different library types, etc. Partial catalog recovery is a variation of the Recovery without import method. It is subjected to many of the same constraints. For more information, go to the following link:

Partial catalog recovery recovers only the flat file components and not the relational database. Thus, the details of the existing infrastructure (servers, devices etc.) at the DR site is not lost during the recovery process. It also means that the media server information that is associated with the backups is not recovered. The media server must be manually added to the database and is unassigned. Ensure that the media server are placed in a pool where they cannot get accidentally overwritten.

Partial catalog recovery has the following advantages over full catalog recovery:

  • No elements of the configuration need to be removed or rediscovered. The recovery process does not affect the general configuration of the DR environment.

  • It does not affect the server topology. The master server topology at the DR site does not need to reflect the topology at the production site. Thus, a catalog backup from a clustered master server can be restored to a standalone master server at the DR site.

  • The DR site can be a production site, provided the client names, backup policy names, and tape label ranges used in the two environments are unique. Also, it must be possible to do a partial recovery to another production backup domain.

With partial catalog recovery, you cannot recover the tape information from the primary site at the DR site. Ensure that the tapes are not accidentally overwritten. These tapes must not be easily used for backups at the DR site.

Feedback

Was this page helpful?
Previous

Making the DR environment consistent after a full catalog restore

Next

Performing partial catalog restore

Feedback

Was this page helpful?