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™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
  3. Managing MSDP Scaleout
  4. Expanding existing data or catalog volumes
  5. Manual storage expansion
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Manual storage expansion

You also can manually expand storage size by expanding PVC size.

To expand the data or catalog volumes

  1. Open the CR YAML file to edit.
  2. Configure spec.paused: true.
  3. Apply new CR YAML to stop MSDP operator from reconciling and repairing the pods automatically.

    kubectl apply -f <your-cr-yaml>

  4. Patch the corresponding PVCs.

    kubectl patch pvc <pvc-name> --type merge --patch '{"spec": {"resources": {"requests": {"storage": "<requested-size>"}}}}' -n <sample-namespace>

  5. Specify spec.paused: false in the CR.
  6. Apply new CR YAML to recover MSDP operator to continue to reconcile and repair the pods automatically.

    kubectl apply -f <your-cr-yaml>

Note:

If you add new MSDP Engines later, the new Engines will respect the CR specification only. Your manual changes would not be respected by the new Engines.

Feedback

Was this page helpful?
Previous

Expanding existing data or catalog volumes

Next

MSDP Scaleout scaling recommendations

Feedback

Was this page helpful?