Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
Last Published:
2022-06-27
Product(s):
NetBackup & Alta Data Protection (10.0.0.1)
- 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 MSDP Scaleout
- Upgrading 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
- Resolving the certificate error issue in NetBackup operator pod logs
- Appendix A. CR template
Pod status field shows as pending
If the pod Status field shows Pending state, it indicates that Kubernetes is not able to schedule the pod. To check use the following command:
$ kubectl get all -n netbackup-operator-system
The output is something like:
NAME READY STATUS RESTARTS AGE pod/msdp-operator- controller-manager- 65d8fd7c4d-bsgms 2/2 Running 0 12m pod/netbackup- operator-controller- manager-6c9dc8d87f -pq8mr 0/2 Pending 0 15s
For more details use the following pod describe command:
$ kubectl describe pod/netbackup-operator-controller-manager-6c9dc8d87f-pq8mr -n netbackup-operator-system
The output is something like:
Type Reason Age Message
---- ------ ---- -------
Warning FailedScheduling 56s (x3 over 2m24s) 0/4 nodes are
available:1 node(s)
had taint {node-
role.kubernetes.
io/master: }, that
the pod didn't
tolerate, 3 node(s)
didn't match
Pod's node
affinity/selector.
To resolve this issue verify the nodeSelector settings in the operator/patch/operator_patch.yaml file.