NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Preparing the environment for NetBackup installation on Kubernetes cluster
- Recommendations of NetBackup deployment on Kubernetes cluster
- Limitations of NetBackup deployment on Kubernetes cluster
- Primary and media server CR
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the cloud node for primary or media servers
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying MSDP Scaleout
- Prerequisites for AKS
- Prerequisites for EKS
- Installing the docker images and binaries
- Initializing the MSDP operator
- Configuring MSDP Scaleout
- Using MSDP Scaleout as a single storage pool in NetBackup
- Configuring the MSDP cloud in MSDP Scaleout
- Using S3 service in MSDP Scaleout for AKS
- Enabling MSDP S3 service after MSDP Scaleout is deployed for AKS
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Socket connection failure
- Resolving an invalid license key issue
- Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
- Resolving the issue where the NetBackup server pod is not scheduled for long time
- Resolving an issue where the Storage class does not exist
- Resolving an issue where the primary server or media server deployment does not proceed
- Resolving an issue of failed probes
- Resolving token issues
- Resolving an issue related to insufficient storage
- Resolving an issue related to invalid nodepool
- Resolving a token expiry issue
- Resolve an issue related to KMS database
- Resolve an issue related to pulling an image from the container registry
- Resolving an issue related to recovery of data
- Check primary server status
- Pod status field shows as pending
- Ensure that the container is running the patched image
- Getting EEB information from an image, a running container, or persistent data
- Resolving the certificate error issue in NetBackup operator pod logs
- Pod restart failure due to liveness probe time-out
- NetBackup messaging queue broker take more time to start
- Host mapping conflict in NetBackup
- Issue with capacity licensing reporting which takes longer time
- Local connection is getting treated as insecure connection
- Primary pod is in pending state for a long duration
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Storage server not supporting Instant Access capability on Web UI after upgrading NetBackup
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Elastic media server related issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Prerequisites
Azure Kubernetes cluster
Your Azure Kubernetes cluster must be created with appropriate network and configuration settings.
Supported Azure Kubernetes cluster version is 1.21.x and later.
Availability zone for AKS cluster must be disabled.
Two storage classes with the following configurations is 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
A Kubernetes Secret that contains the required Snapshot Manager credentials.
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.
Node Pool
You must have a dedicated node pool for Snapshot Manager created. The Azure autoscaling allows your node pool to scale dynamically as required.
It is recommended that you set the minimum node number to 1 or more to bypass some limitations in AKS.
User must enable system managed identity on the control node pool and add appropriate role for Snapshot Manager to operate.
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.
Amazon Elastic Kubernetes Services cluster
Your Amazon Elastic Kubernetes Services cluster must be created with appropriate network and configuration settings.
Supported Amazon Elastic Kubernetes Services cluster version is 1.21.x and later.
Two storage classes with the following configurations 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.
A Kubernetes Secret that contains the required Snapshot Manager credentials.
Amazon Elastic Kubernetes Service containerSnapshot Manager 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
You must have a dedicated node group created for Snapshot Manager's scalable workflow and data movement services. It is recommended to use the NetBackup primary server's node group for Snapshot Manager's control services.
User must assign same IAM role with required permissions to both the node groups, that is control node group and data 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.21.x or later. The version of AWS CLI must meet the EKS cluster requirements.
If EKS is a private cluster, see Create a private Amazon EKS 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 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.