Prerequisites for Snapshot Manager (AKS/EKS)
Azure Kubernetes cluster
Your Azure Kubernetes cluster must be created with appropriate network and configuration settings.
Availability zone for AKS cluster must be disabled.
Cert-manager and trust-manager must be installed.
Two storage classes with the following configurations are required:
Storage class field
Data
Log
provisioner
disk.csi.azure.com
file.csi.azure.com
storageaccounttype
Premium_LRS
Premium_LRS
reclaimPolicy
Retain
Retain
allowVolumeExpansion
True
True
Azure container registry (ACR)
Use existing ACR or create a new one. Your Kubernetes cluster must be able to access this registry to pull the images from ACR. For more information on Azure container registry, see 'Azure Container Registry documentation' section in Microsoft Azure Documentation.
Node pool
A dedicated data node pool must be created specifically for Snapshot Manager's data plane services (workflow and data movement services). Autoscaling for the Snapshot Manager's data node pool must be enabled to allow dynamic scaling based on workload demands. It is recommended to configure the Snapshot Manager's data node pool minimum node count to 0, and max node count more than 0, depending on the operational requirements.
It is recommended to use NetBackup primary server's node group for Snapshot Manager's control plane services. The control node pool must have managed identity enabled. Users must assign the appropriate roles to allow Snapshot Manager to operate as expected.
Client machine to access AKS cluster
A separate computer that can access and manage your AKS cluster and ACR.
It must have Linux operating system.
It must have Docker daemon, the Kubernetes command-line tool (kubectl), and Azure CLI installed.
The Docker storage size must be more than 6 GB. The version of kubectl must be v1.19.x or later. The version of Azure CLI must meet the AKS cluster requirements.
If AKS is a private cluster, see Create a private Azure Kubernetes Service cluster.
Static Internal IPs
If the internal IPs are used, reserve the internal IPs (avoid the IPs that are reserved by other systems) for Snapshot Manager and add DNS records for all of them in your DNS configuration.
The Azure static public IPs can be used but is not recommended.
If Azure static public IPs are used, create them in the node resource group for the AKS cluster. A DNS name must be assigned to each static public IP. The IPs must be in the same location of the AKS cluster.
Ensure that the managed identity has the scope to connect to the resource group of the cluster created for cloud scale deployment.
AWS Kubernetes cluster
Your AWS Kubernetes cluster must be created with appropriate network and configuration settings.
Two storage classes with the following configuration is required:
Storage class field
Data
Log
provisioner
kubernetes.io/aws-ebs
efs.csi.aws.com
reclaimPolicy
Retain
Retain
allowVolumeExpansion
True
True
Note:
It is recommended to use a separate EFS for Snapshot Manager deployment and primary server catalog.
Amazon Elastic Container Registry (ECR)
Use existing ECR or create a new one. Your Kubernetes cluster must be able to access this registry to pull the images from ECR.
Node Group
A dedicated data node group must be created specifically for Snapshot Manager's data plane services (workflow and data movement services). Autoscaling for the Snapshot Manager's data node group must be enabled to allow dynamic scaling based on workload demands. It is recommended to configure the Snapshot Manager's data node group minimum node count to 0, and max node count more than 0, depending on the operational requirements.
It is recommended to use NetBackup primary server's node group for Snapshot Manager's control plane services. Users must assign the appropriate IAM role with required permission to control node group.
Client machine to access EKS cluster
A separate computer that can access and manage your EKS cluster and ECR.
It must have Linux operating system.
It must have Docker daemon, the Kubernetes command-line tool (kubectl), and AWS CLI installed.
The Docker storage size must be more than 6 GB. The version of kubectl must be v1.19.x or later. The version of AWS CLI must meet the EKS cluster requirements.
If EKS is a private cluster, see Creating an private Amazon EKS cluster.
Static Internal IPs
If the internal IPs are used, reserve the internal IPs (avoid the IPs that are reserved by other systems) for Snapshot Manager and add forward and reverse DNS records for all of them in your DNS configuration.
The AWS static public IPs can be used but is not recommended.