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
- Deploying MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- 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 inconsistency in file ownership
- 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
- Appendix A. CR template
Resolve an issue related to pulling an image from the container registry
Primary or media server failed to deploy with error. If the pod Status field displays , it means that the pod could not start because Kubernetes cannot pull a container image. A misspelled registry or image name or image registry being not reachable can cause a status.
Run the $ k get all -n netbackup-operator-system command.
The output should look like:
NAME READY STATUS RESTARTS AGE pod/msdp-operator -controller-manager- 65d8fd7c4d-bsgms 2/2 Running 0 7m9s pod/netbackup-operator -controller-manager- 5df6f58b9b-6ftt9 1/2 ImagePullBackOff 0 13s
For additional details, use the following command:
$ kubectl describe pod/<pod_name> -n netbackup-operator-system
Resolve this issue using any of the following methods:
Check if image name and tag are correct. If not, edit and update the environment CR using the kubectl edit environment <environment CR-name> -n <namespace> command with correct image name and tag, and then save the changes.
Check if the user is authorized and has permissions to access the Azure container registry.