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. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section III. Monitoring and Management
  4. Performing catalog backup and recovery
  5. Restoring a catalog
  6. MSDP-X corrupted
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

MSDP-X corrupted

  1. Note the storage server, cloud LSU and cloud bucket name.
  2. Edit the environment and remove MSDP server.
  3. From NetBackup Web UI allow reissue of token for MSDP server.
  4. Deploy MSDP server with same fields using the following command:

    helm upgrade --install cloudscale cloudscale-<version>.tgz -f cloudscale-values.yaml --namespace <namespace>

  5. Verify if MSDP installation is successful and default MSDP storage server, STU and disk pool is created with old names.
  6. Perform from step 2 in the following section:

    “Scenario 1: MSDP Scaleout and its data is lost and the NetBackup primary server remains unchanged and works well”

  7. Verify/Backup/Restore the backup images in NetBackup server to check if the MSDP-X cluster has recovered or not.

Feedback

Was this page helpful?
Previous

Primary server corrupted

Next

MSDP-X and Primary server corrupted

Feedback

Was this page helpful?