Expanding storage volumes
You can update storage capacity of already created persistent volume claim for primary server and media server. Expanding storage volume for particular replica of respective CR object is not supported. In case of media server user needs to update volumes for all the replicas of particular media server object.
(AKS-specific) To expand storage capacity of catalog volume in primary server
- Run the following command to edit the environment custom resource, update the storage capacity for respective volume:
helm upgrade cloudscale cloudscale.tgz -n <namespace> --reuse-values --set environment.primary.storage.catalog.capacity=<expandedcapacity>Gi
- Save the changes.
PVC will expand as per the new size and it will be available to volume mounts in primaryServer pod.
To expand volume of data and log volumes for primary and media server
Note:
(EKS-specific) Amazon EFS is an elastic file system, it does not enforce any file system capacity limits. The actual storage capacity value in persistent volumes and persistent volume claims is not used when creating the file system. However, because storage capacity is a required field in Kubernetes, you must specify a valid value. This value does not limit the size of your Amazon EFS file system.
- Run the following command:
For data volumes:
helm upgrade cloudscale cloudscale.tgz -n <namespace>--reuse-values --setenvironment.primary.storage.data.capacity=<expandedcapacity>Gi
For log volumes:
helm upgrade cloudscale cloudscale.tgz -n <namespace>--reuse-values --set environment.primary.storage.log.capacity=<expandedcapacity>Gi
- Run the kubectl get pvc -n <namespace> command and check for capacity column in result to check the persistent volume claim storage capacity is expanded.
- (Optional) Update the log retention configuration for NetBackup depending on the updated storage capacity.
For more information, refer to the
NetBackup™ Administrator's Guide, Volume I