Expanding existing data or catalog volumes
You can expand the existing data or catalog volumes by updating the Cloud Scale helm release.
To expand the data or catalog volumes by updating the Cloud Scale helm release
- Navigate to the helm directory within the extracted tar location.
- Run the following command to obtain the Cloud Scale release name:
Helm ls -n <namespace>
- Run the following command to expand the data volume:
helm upgrade <cloudscale helm release> cloudscale-<version>.tgz -n netbackup --reuse-values
--set environment.msdpScaleouts.storage.dataVolumes[0].capacity=<new-value>
--set environment.msdpScaleouts.storage.dataVolumes[0].storageClassName=<new-value>
- Run the following command to expand the catalog volume:
helm upgrade <cloudscale helm release> cloudscale-<version>.tgz -n netbackup --reuse-values
--set environment.msdpScaleouts.storage.catalog[0].capacity=<new-value>
--set environment.msdpScaleouts.storage.catalog[0].storageClassName=<new-value>
Sometimes Azure disk or 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 Azure disk or Amazon CSI storage 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.