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 between 1.21.x and 1.24.x.
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
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:
Node type
B4ms
RAM
8 GB
Number of nodes
Minimum 1 with auto scaling enabled.
Maximum pods per node
6 (system) + 4 (static pods) + RAM*2 (dynamic) = 26 pods or more
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:
For 2 CPU's and 8 GB RAM node configuration:
CPU
More than 2 CPU's
RAM
8 GB
Maximum pods per node
6 (system) + 4 (static pods) + 8*2 = 16 (dynamic pods) = 26 or more
Autoscaling enabled
Minimum number =1 and Maximum = 3
Note:
Above configuration will run 8 jobs per node at once.
For 2/4/6 CPU's and 16 GB RAM node configuration:
CPU
More than 2/4/6 CPU's
RAM
16 GB
Maximum pods per node
6 (system) + 4 (Static pods) + 16*2=32 (Dynamic pods) = 42 or more
Autoscaling enabled
Minimum number =1 and Maximum = 3
Note:
Above configuration will run 16 jobs per node at once.
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:
Add a label with certain key value. For example key = nbpool, value = nbnodes
Add a taint with the same key and value which is used for label in above step with effect as NoSchedule.
For example, key = nbpool, value = nbnodes, effect = NoSchedule
Provide these details in the operator yaml as follows. To update the toleration and node selector for operator pod,
Edit the
operator/patch/operator_patch.yamlfile. Provide the same label key:value in node selector section and in toleration sections. For example,nodeSelector: nbpool: nbnodes # Support node taints by adding pod tolerations equal to the specified nodeSelectors # For Toleartion NODE_SELECTOR_KEY used as a key and NODE_SELECTOR_VALUE as a value. tolerations: - key: nbpool operator: "Equal" value: nbnodes
Update the same label
key:valueaslabelKeyandlabelValuein nodeselector section inenvironment.yamlfile.
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.
Create a storage class with Managed disc storage type with
file.csi.azure.comand allows volume expansion. It must be in LRS category with Premium SSD. It is recommended that the storage class has ,Retainreclaim. Such storage class can be used for primary server as it supportsAzure premium filesstorage 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: nfsCreate a storage class with
Managed discstorage type withallowVolumeExpansion = trueandReclaimPolicy=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 role.
For more information, see Azure built-in roles.
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>