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
- About primary server CR and media server CR
- 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
- Appendix A. CR template
Recommendations of NetBackup deployment on AKS
Note the following recommendations:
Use Azure Premium storage for catalog volume in primary server CR and data volume in media server CR.
Use Azure Standard storage for log volume in primary server CR and media server CR.
For primary server volumes, use
Azure files
as storage type and for media server volumes, usemanaged-disk
as storage type.Do not delete the disk linked to PV used in primary server and media server CR deployment. This may lead to data loss.
Ensure that in one cluster, only one NetBackup operator instance is running.
Do not edit any Kubernetes resource created as part of primary server and media server custom resource. Update is supported through custom resource update only.
Detailed primary server custom resource deployment and media server custom resource deployment logs are retrieved from NetBackup operator pod logs using the kubectl logs <netbackup-operator-pod-name> -c netbackup-operator -n <netbackup operator-namespace> command .
Deploy primary server custom resource and media server custom resource in same namespace.
Ensure that you follow the symbolic link and edit the actual persisted version of the file, if you want to edit a file having a symbolic link in the primary server or media server.
In case of upgrade and during migration, do not delete the Azure disk linked to the old PV which is used in primary server CR deployment until the migration is completed successfully. Else this leads to data loss.