NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Your Azure Kubernetes cluster must be created with appropriate network and configuration settings.

Supported Kubernetes cluster version is between 1.21.x and 1.24.x.

While creating the cluster, assign appropriate roles and permissions.

Concepts - Access and identity in Azure Kubernetes Services (AKS) - Azure Kubernetes Service | Microsoft Docs

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.

Another dedicated node pool must be created for Snapshot Manager (if it has to be deployed) with auto scaling enabled.

Following is the minimum configuration required for Snapshot Manager data plane node pool:

Following are the different scenario's on how the NetBackup Snapshot Manager calculates the number of job which can run at a given point in time, based on the above mentioned formula:

All the nodes in the node pool must be running the Linux operating system.

Taints and tolerations allows you to mark (taint) a node so that no pods can schedule onto it unless a pod explicitly tolerates the taint. Marking nodes instead of pods (as in node affinity/anti-affinity) is particularly useful for situations where most pods in the cluster must avoid scheduling onto the node.

Taints are set on the node pool while creating the node pool in the cluster. Tolerations are set on the pods.

To use this functionality, user must create the node pool with the following detail:

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 annotations key in the networkLoadBalancer 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.

Create a storage class with Managed disc storage type with file.csi.azure.com and allows volume expansion. It must be in LRS category with Premium SSD. It is recommended that the storage class has , Retain reclaim. Such storage class can be used for primary server as it supports Azure premium files storage only for catalog volume.

For more information on Azure premium files, see Azure Files CSI driver.

For example,

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: {{ custome-storage-class-name }}
provisioner: file.csi.azure.com
reclaimPolicy: Retain
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer
parameters:
  storageaccounttype: Premium_LRS
  protocol: nfs

Create a storage class with Managed disc storage type with allowVolumeExpansion = true and ReclaimPolicy=Retain. This storage class will be used for Primary server data and log volume. Media server storage details support azure disks only.

Customer's Azure subscription should have Network Contributor role.

For more information, see Azure built-in roles.

Linux operating system: For a complete list of compatible Linux operating systems, refer to the Software Compatibility List (SCL) at:

NetBackup Compatibility List for all Versions

https://sort.veritas.com/netbackup

Install Docker on the host to install NetBackup container images through tar, and start the container service.

https://docs.docker.com/engine/install/

Prepare the host to manage the AKS cluster.