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 loss protection with auto image and catalog replication
  4. About NetBackup catalog replication
  5. About partial catalog replication
  6. Considerations for managing tapes with partial catalog replication
Veritas NetBackup™ in Highly Available Environments Administrator's Guide

Considerations for managing tapes with partial catalog replication

The tapes from the production domain are not assigned in the disaster recovery domain. The tapes must be manually added to the database and placed in a pool where they cannot get accidentally overwritten. This can also be done using a combination of barcode rules and the robot inventory command.

As the tapes are not assigned on the disaster recovery master server they will not be released to the global scratch pool when backups expire and therefore these tapes must be manually recycled.

Caution:

Care must be taken to ensure that the tapes are manually moved to the global scratch pool only when they do not have valid backups on them.

The simplest way of checking this is to create two lists by running the commands bpimagelist - d "01/01/1970 00:00:00" - media - l and vmquery - pn <private pool name> -b and then comparing the lists. Tapes found in the second list but not found in the first list have no valid images on them and can be moved to the scratch pool by running the command vmchange - p <scratch pool number> -m <media id>.

Feedback

Was this page helpful?
Previous

Making the disaster recovery environment consistent with partial catalog replication

Next

Deploying NetBackup master servers with full catalog replication

Feedback

Was this page helpful?