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
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Expanding existing data or catalog volumes

You can expand the existing data or catalog volumes by updating the CR.

To expand the data or catalog volumes by updating the CR YAML file

  1. Open the CR YAML file to edit.
  2. Increase the requested storage size in the spec.dataVolumes field or in the spec.catalogVolume field.
  3. Apply new CR YAML to update the CR in the Kubernetes environment.

    kubectl apply -f <your-cr-yaml>

To expand the data or catalog volumes using the kubectl command directly

  • Run the following command to increase the requested storage size in the spec.dataVolumes field or in the spec.catalogVolume field..

    kubectl -n <sample-namespace> edit msdpscaleout <your-cr-name> [-o json | yaml]

Sometimes Amazon EBS CSI driver may not respond the volume expansion request promptly. In this case, the operator retries the request by adding 1 byte to the requested volume size to trigger the volume expansion again. If it is successful, the actual volume capacity could be slightly larger than the requested size.

Due to the limitation of Amazon EBS CSI driver, the engine pods need to be restarted for resizing the existing volumes. This can cause the short downtime of the services.

MSDP Scaleout does not support the following:

  • Cannot shrink the volume size.

  • Cannot change the existing data volumes other than for storage expansion.

  • Cannot expand the log volume size. You can do it manually. See Manual storage expansion.

  • Cannot expand the data volume size for MDS pods. You can do it manually. See Manual storage expansion.

Feedback

Was this page helpful?
Previous

Adding data volumes

Next

Manual storage expansion

Feedback

Was this page helpful?