Resolving the issue where the NetBackup server pod is not scheduled for long time
The NetBackup server (primary server and media server) pods are stuck in Pending state. The issue can be because of one of the following reasons:
Insufficient resource allocation.
Persistent volume claims are not bound to persistent volume.
NetBackup server pods have the anti-affinity rule added.
As a result, primary server and media server pods are scheduled on different nodes. If nodes are not available, pod remains in pending state with event logs indicating nodes are scaling up, if auto scaling is configured in cluster.
To resolve the issue where the NetBackup server pod is not scheduled for long time
- Check the pod event details for more information about the error using kubectl describe <PrimaryServer/MediaServer_Pod_Name> -n <namespace> command.
- Depending on the output of the command and the reason for the issue, perform the required steps and update the environment CR to resolve the issue.