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
- Edit the environment custom resource using the kubectl edit Environment <environmentCR_name> -n <namespace> command.
- Update storage capacity for respective volume in storage subsection of primary section.
- 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.
- Edit the environment custom resource using the kubectl edit Environment <environmentCR_name> -n <namespace> command.
- To pause the reconciler of the particular custom resource, change the paused: false value to paused: true in the primaryServer or mediaServer section and save the changes. In case of multiple media server objects change Paused value to true for respective media server object only.
- Edit StatefulSet of primary server object using thekubectl edit <statfulset name> -n <namespace> command, change replica count to 0 and wait for all pods to terminate for the particular CR object.
- Update all the persistent volume claim which expects capacity resize with the kubectl edit pvc <pvcName> -n <namespace> command. In case of particular media server object, resize respective PVC with expected storage capacity for all its replicas.
- Update the respective custom resource section using the kubectl edit Environment <environmentCR_name> -n <namespace> command with updated storage capacity for respective volume and change paused: false. Save updated custom resource.
To update the storage details for respective volume, add storage section with specific volume and its capacity in respective primaryServer or mediaServer section in environment CR.
Earlier terminated pod and StatefulSet must get recreated and running successfully. Pod should get linked to respective persistent volume claim and data must have been persisted.
- 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