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

Performing partial catalog restore

With partial catalog approach, it is assumed that restore operations do not need tapes to be assigned or located in specific media pools. It is also assumed that a tape exists in EMM and NetBackup can mount and read the tape for restoring. The following steps must be carried out before restores can be started:

To prepare for partial catalog restore

  1. On UNIX and Linux master servers create copies of the bp.conf and vm.conf files.
  2. Recover only the NetBackup catalog image and configuration files.
    • When using the NetBackup Administration Console, select the Partial catalog recovery option when prompted.

    • Or run the bprecover -wizard command.

    Note:

    The DR master server must have the same name as the production master server.

    Note:

    If a catalog backup that was created on a separate media server is used, a media server with the same name is required for the catalog recovery.

  3. Run the cat_export - all - staging to export the metadata from the replicated relational database backup.
  4. Run the command cat_import - all to import the exported metadata into the active relational database. Alternatively, set the parameter LIST_FS_IMAGE_HEADERS to YES in the bp.conf file or the registry depending on the master server platform. This will cause the next catalog cleanup job to automatically import the exported metadata.
  5. Deactivate all the backup policies to prevent backups from starting automatically.
    • You can do this manually using the NetBackup Adminstration Console.

    • Or run the bpplinfo <policy> -modify -inactive CLI.

  6. Shut down NetBackup.
  7. On UNIX and Linux master servers, replace the bp.conf and the vm.conf files that were restored from the catalog backup with the copies created in step 1
  8. Start NetBackup.
  9. Inventory all the tape libraries to ensure that the tapes are added to the non-scratch media pool. This pool prevents tapes from being accidentally overwritten by active backup policies at a later time.

You can now start restore and recovery operations of client data that is backed up at the production datacenter.

Feedback

Was this page helpful?
Previous

About partial catalog recovery

Next

Making the DR environment consistent after a partial catalog restore

Feedback

Was this page helpful?