NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
- Introduction to NetBackup on AKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on AKS
- Recommendations of NetBackup deployment on AKS
- Limitations of NetBackup deployment on AKS
- About primary server CR and media server CR
- Monitoring the status of the CRs
- Updating the CRs
- Deleting the CRs
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the node pool for primary or media servers
- Upgrading NetBackup
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Troubleshooting
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Pod restart failure due to liveness probe time-out
- Socket connection failure
- Resolving an invalid license key issue
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to inconsistency in file ownership
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Resolving the certificate error issue in NetBackup operator pod logs
- Appendix A. CR template
Configuring MSDP Scaleout
After you push the docker images to ACR and initialize MSDP operator, configure MSDP Scaleout.
To configure MSDP Scaleout
- Create a dedicated namespace for MSDP Scaleout to run.
kubectl create ns <sample-namespace>
- Create an MSDP Scaleout Secret. The Secret is used in CR.
kubectl apply -f <secret-yaml-file>
See Secret.
- Display the custom resource (CR) template.
kubectl msdp show -c
- Save the CR template.
kubectl msdp show -c -f <file path>
- Edit the CR file in the text editor.
- Apply the CR file to the AKS cluster.
Caution:
Add MSDP_SERVER = <first Engine FQDN> in
/usr/openv/netbackup/bp.conffile on the NetBackup primary server before applying the CR YAML.kubectl apply -f <sample-cr-yaml>
- Monitor the configuration progress.
kubectl get all -n <namespace> -o wide
In the STATUS column, if the readiness state for the controller, MDS and engine pods are all Running, it means that the configuration has completed successfully.
In the READINESS GATES column for engines, 1/1 indicates that the engine configuration has completed successfully.
- If you specified spec.autoRegisterOST.enabled: true in the CR, when the MSDP engines are configured, the MSDP operator automatically registers the storage server, a default disk pool, and a default storage unit in the NetBackup primary server.
A field ostAutoRegisterStatus in the Status section indicates the registration status. If ostAutoRegisterStatus.registered is True, it means that the registration has completed successfully.
You can run the following command to check the status:
kubectl get msdpscaleouts.msdp.veritas.com -n <sample-namespace>
You can find the storage server, the default disk pool, and storage unit on the Web UI of the NetBackup primary server.