Reducing catalog storage management
(For EKS-specific deployments) The primary catalog storage is based on the Elastic File System, which provides unlimited storage (automatic expansion), thereby effacing the need to monitor it.
(For AKS-specific deployments) With this release, the fresh installation of Cloud Scale deployment would have the capability to self-regulate the primary server's catalog volume. The functionality can be controlled by changing the value of field in the primary server catalog storage section of cloudscale-values.yaml file.
If the field is set to,
true, the operator automatically expands the catalog's capacity by 20%, every time the catalog reaches 80% of its usage. This check for catalog usage is only triggered every 10 hours.
false, the automatic check and expansion of primary catalog usage will not happen, and if needed, the volume can be expanded. Expanding storage volumes
If required, the user can expand the catalog capacity by a value different than 20%. This can be achieved by performing the following:
Set the value of field to false under primary's catalog storage.
helm upgrade cloudscale cloudscale-11.2.tgz -n netbackup --reuse-values --set environment.primary.storage.catalog.autoVolumeExpansion=false
Manually expand the catalog capacity to desired value using the following command:
helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.storage.catalog.capacity=80Gi (or whatever the desired capacity is)
To enable automatic catalog volume usage monitoring, update the value of field in the environment to true after manually updating the capacity.