About primary server CR and media server CR
Primary server custom resource is used to deploy the NetBackup primary server and media server custom resource is used to deploy the NetBackup media server.
After the operator is installed, update the custom resource YAMLs to deploy the primary server and media server CRs located in the
samplesfolder. CR yamls are located insamplesfolder where package is untarred.The primary server CRD and media server CRD are located in
operator_deployment.yamlin the operator folder where the package is extracted.used in the primary server and media server CRs must not be same. In the primary server CR the should not contain the word and in the media server CR the should not contain the word .
Note:
After deployment, you cannot change the in primary server and media server CR.
Before the CRs can be deployed, the utility called Config-Checker is executed that performs checks on the environment to ensure that it meets the basic deployment requirements. The config-check is done according to the configCheckMode and paused values provided in the custom resource YAML.
For more information, refer to See How does the Config-Checker utility work.
You can deploy the primary server and media server CRs in same namespace.
Use the storage class that has the storage type as 'Azure disk' for the catalog and log volumes in the primary server CR, and data and log volumes in the media server CR.
During fresh installation of the NetBackup servers, the value for keep logs up to under log retention configuration is set based on the log storage capacity provided in the respective primary server or media server CR inputs. You may change this value if required.
The NetBackup deployment sets the value as per the formula.
Size of logs PVC/PV * 0.8 = Keep logs up value By default, the default value is set to 24GB.
For example: If the user configures the storage size in the CR as 40GB (instead of the default 30GB) then the default value for that option become 32GB automatically based on the formula.
Deployment details of primary server and media server can be observed from the operator pod logs using the following command:
kubectl logs <operator-pod-name> -c netbackup-operator -n <operator-namespace>