Updating the Primary/Media server CRs
After the successful deployment of the primary server and media server CRs, you can update the values of only selected specs by editing the respective environment custom resource.
Note:
Updating the Kubernetes resources (pod, configmap, services, statefulset etc) created for the CRs is not recommended.
Following tables describe the specs that can be edited for each CR.
Table: Primary server CR
Spec | Description |
|---|---|
paused | Specify True or False as a value, to temporarily stop the respective CR controller. True: Stop the controller. False: Resume the controller. |
configCheckMode | Specify default, dryrun or skip as a value. |
(AKS-specific) capacity | Catalog, log and data volume storage capacity can be updated. |
Table: Media server CR
Spec | Description |
|---|---|
paused | Specify True or False as a value, to temporarily stop the respective CR controller. True: Stop the controller. False: Resume the controller. |
replicas | Specifies the maximum number of replicas that the media server can scale up to. Note: It is recommended not to reduce the number of maximum replicas. To reduce the maximum number of replicas, perform the media server decommissioning steps mentioned in References to nonexistent or decommissioned media servers remain in NetBackup. |
minimumReplicas | Describes the minimum number of replicas of the media server running. This is an optional field. If not specified, the value for this field will be set to the default value of 1. |
configCheckMode | Specify default, dryrun or skip as a value. |
(AKS-specific) capacity | Catalog, log and data volume storage capacity can be updated. |
If you edit any other fields, the deployment can go into an inconsistent state.
Delete the Load Balancer service created for the media server by running the following commands:
$ kubectl get service --namespace <namespce_name>
$ kubectl delete service <service-name> --namespace <namespce_name>
Identify and delete any outstanding persistent volume claims for the media server by running the following commands:
$ kubectl get pvc --namespace <namespce_name>
$ kubectl delete pvc <pvc-name>
Locate and delete any persistent volumes created for the media server by running the following commands:
$ kubectl get pv
$ kubectl delete pv <pv-name> --grace-period=0 --force