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
Preparing the environment for NetBackup installation on AKS
Refer to this section to prepare your host system and Azure Kubernetes cluster for NetBackup installation.
Use the following checklist to prepare the AKS for installation.
Your Azure Kubernetes cluster must be created with appropriate network and configuration settings.
Supported Kubernetes cluster version is 1.21.x and later.
While creating the cluster, assign appropriate roles and permissions.
Use an existing Azure container registry or create a new one. Your Kubernetes cluster must be able to access this registry to pull the images from the container registry. For more information on the Azure container registry, see Azure Container Registry documentation.
A dedicated node pool for NetBackup must be created with manual scaling or Autoscaling enabled in Azure Kubernetes cluster. The autoscaling feature allows your node pool to scale dynamically by provisioning and de-provisioning the nodes as required automatically.
The following table lists the node configuration for the primary and media servers.
Node type
D16ds v4
Disk type
P30
vCPU
16
RAM
64 GiB
Total disk size per node (TiB)
1 TB
Number of disks/node
1
Cluster storage size
Small (4 nodes)
4 TB
Medium (8 nodes)
8 TB
Large (16 nodes)
16 TB
All the nodes in the node pool must be running the Linux operating system.
If you want to use static public IPs, private IPs and fully qualified domain names for the load balancer service, the public IP addresses, private IP addresses and FQDNs must be created in AKS before deployment.
If you want to bind the load balancer service IPs to a specific subnet, the subnet must be created in AKS and its name must be updated in the
key in the section of the custom resource (CR).For more information on the network configuration for a load balancer service, refer to the How-to-Guide section of the Azure documentation.
For more information on managing the load balancer service, See About the Load Balancer service.
Use the following checklist to address the prerequisites on the system that you want to use as a NetBackup host that connects to the AKS cluster.
Linux operating system: For a complete list of compatible Linux operating systems, refer to the Software Compatibility List (SCL) at:
Install Docker on the host to install NetBackup container images through tar, and start the container service.
Prepare the host to manage the AKS cluster.
Install Azure CLI.
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux/
Install Kubernetes CLI
https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/
Log in to the Azure environment to access the Kubernetes cluster by running this command on Azure CLI:
# az login - identity
# az account set --subscription <subscriptionID>
# az aks get-credentials --resource-group
<resource_group_name> --name <cluster_name>
Log in to the container registry:
# az acr login -n <container-registry-name>