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 and NetBackup Appliances Hardening Guide
  3. Steps to protect Flex Appliance
  4. Protecting the MSDP catalog on a WORM storage server
NetBackup and NetBackup Appliances Hardening Guide

Protecting the MSDP catalog on a WORM storage server

By default, WORM storage servers store a copy of the MSDP catalog in the directory /mnt/msdp/vol0 in addition to the original copy that is available under the dedicated catalog volume (/mnt/msdpcat).

If you want extra protection for the catalog, you can configure additional copies. Use the following procedures to manage the MSDP catalog copies from the deduplication shell.

To view the catalog copies

  1. Open an SSH session to the server.
  2. Run the following command:

    cacontrol --catalog listshadowcopies

To configure an additional copy

  1. Open an SSH session to the server.
  2. Run the following command to determine which volumes exist in the /mnt/msdp directory:

    df -h

    Select one of the volumes other than vol0.

    Note:

    To configure an additional catalog copy, at least one volume other than vol0 must exist in the /mnt/msdp directory.

  3. Run the following command:

    cacontrol --catalog addshadowcopy /mnt/msdp/<volume name>

    Where <volume name> is the volume that you chose in the previous step.

    For example:

    cacontrol --catalog addshadowcopy /mnt/msdp/vol1

Feedback

Was this page helpful?
Previous

Adding a replication operation to SLP at the production primary server

Next

Using a sign-in banner

Feedback

Was this page helpful?