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
Upgrading MSDP Scaleout
You can upgrade the MSDP Scaleout solution to the latest version in your AKS environment.
To upgrade MSDP Scaleout
- Install the new kubectl plug-in and push the new docker images to your container registry.
- Run the following command to upgrade the MSDP operator.
kubectl msdp init -i <new-operator-image> -s <storage-class-name> -l agentpool=<nodepool-name> -n <operator-namespace>
All the options except -i option must be same as earlier when the operator was deployed initially.
- Run the following command to change the spec.version in the existing CR resources.
kubectl edit msdpscaleout <cr-name>
Wait for a few minutes. MSDP operator upgrades all the pods and other MSDP Scaleout resources automatically.
Note:
If you use the environment operator for the MSDP Scaleout deployment, change the version string for MSDP Scaleout in the environment operator CR only. Do not change the version string in the MSDP Scaleout CR.
- Upgrade process restarts the pods. The NetBackup jobs are interrupted during the process.
Upgrade NetBackup 10.0 or 10.0.0.1 to NetBackup 10.1
After you upgrade NetBackup 10.0 (or 10.0.0.1) to NetBackup 10.1 or MSDP Scaleout to 17.0, if you find the storage server not supporting Instant Access capability on Web UI, or if you fail to select MSSQL recovery point to create MSSQL Instant Access on Web UI, then perform the following steps manually to refresh the Instant Access capability in NetBackup.
Login to NetBackup primary server.
Execute the following commands to refresh the MSDP capabilities on NetBackup primary server:
nbdevconfig -getconfig
nbdevconfig -setconfig
For example,
/usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -stype PureDisk -storage_server [storage server] > /tmp/tmp_pd_config_file
/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server [storage server] -stype PureDisk -configlist /tmp/tmp_pd_config_file
Restart the NetBackup Web Management Console service (nbwmc) on NetBackup primary server.
For example,
/usr/openv/netbackup/bin/nbwmc terminate
/usr/openv/netbackup/bin/nbwmc start