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
- Preparing the environment for NetBackup installation on AKS
- Recommendations of NetBackup deployment on AKS
- Limitations of NetBackup deployment on AKS
- About primary server CR and media server CR
- Monitoring the status of the CRs
- Updating the CRs
- Deleting the CRs
- Configuring NetBackup IT Analytics for NetBackup deployment
- Managing NetBackup deployment using VxUpdate
- Migrating the node pool for primary or media servers
- Upgrading NetBackup
- Deploying Snapshot Manager
- Migration and upgrade of Snapshot Manager
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager deployment
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Uninstalling Snapshot Manager
- Troubleshooting
- View the list of operator resources
- View the list of product resources
- View operator logs
- View primary logs
- Pod restart failure due to liveness probe time-out
- 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
- Data migration unsuccessful even after changing the storage class through the storage yaml file
- Host validation failed on the target host
- Primary pod is in pending state for a long duration
- Taint, Toleration, and Node affinity related issues in cpServer
- Operations performed on cpServer in environment.yaml file are not reflected
- Host mapping conflict in NetBackup
- NetBackup messaging queue broker take more time to start
- Local connection is getting treated as insecure connection
- Issue with capacity licensing reporting which takes longer time
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Primary pod goes in non-ready state
- Appendix A. CR template
Initializing the MSDP operator
Run the following command to initialize MSDP operator.
kubectl msdp init -i <acr-url>/msdp-operator:<version> -s <storage-class-name> [-l agentpool=<nodepool-name>]
You can use the following init command options.
Table: init command options
Option | Description |
|---|---|
-i | MSDP operator images on your ACR. |
-s | The storage class name. |
-l | Node selector of the MSDP operator. By default, each node pool has a unique label with key-value pair agentpool=<nodepool-name>. If you have assigned a different and cluster-wise unique label for the node pool, you can use that instead of agentpool. |
-c | Core pattern of the operator pod. Default value: "/core/core.%e.%p.%t" |
-d | Enable debug-level logging in MSDP operator. |
-a | The maximum number of days to retain the old log files. Range: 1-365 Default value: 28 |
-u | The maximum number of old log files to retain. Range: 1-20 Default value: 20 |
-n | Namespace scope for this request. Default value: msdp-operator-system |
-o | Generate MSDP operator CRD YAML. |
-h | Help for the init command. |
This command installs Custom Resource Definitions (CRD) msdpscaleouts.msdp.veritas.com and deploys MSDP operator in the Kubernetes environment. MSDP operator runs with Deployment Kubernetes workload type with single replica size in the default namespace msdp-operator-system.
MSDP operator also exposes the following services:
Webhook service
The webhook service is consumed by Kubernetes api-server to mutate and validate the user inputs and changes of the MSDP CR for the MSDP Scaleout configuration.
Metrics service
The metric service is consumed by Kubernetes/AKS for Azure Container Insight integration.
You can deploy only one MSDP operator instance in an AKS cluster.
Run the following command to check the MSDP operator status.
kubectl -n msdp-operator-system get pods -o wide