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
Prerequisites
Ensure that the following prerequisites are met before proceeding with the deployment.
A Kubernetes cluster in Azure Kubernetes Service in Azure with multiple nodes. Using separate node pool is recommended for the NetBackup and MSDP Scaleout deployments.
Define one or more storage classes in the Kubernetes cluster.
Access to a container registry that the Kubernetes cluster can access, like an Azure Kubernetes Service Container Registry.
Enable AKS Uptime SLA. AKS Uptime SLA is recommended for a better resiliency. For information about AKS Uptime SLA and to enable it, see Azure Kubernetes Service (AKS) Uptime SLA.
Install Cert-Manager. You can use the following command to install the Cert-Manager:
$ kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.6.0/cert-manager.yaml
For details, see https://cert-manager.io/docs/installation/
A workstation or VM running Linux with the following:
Configure kubectl to access the cluster.
Install Azure CLI to access Azure resources.
Configure docker to be able to push images to the container registry.
Free space of approximately 8.5GB on the location where you copy and extract the product installation TAR package file. If using docker locally, there should be approximately 8GB available on the
/var/lib/docker
location so that the images can be loaded to the docker cache, before being pushed to the container registry.