Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  3. Troubleshooting
  4. Primary pod is in pending state for a long duration
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Primary pod is in pending state for a long duration

Primary pod and Operator pod have pod anti-affinity set.

To resolve the issue of long duration pending state of primary pod

  1. Verify if Operator pod and Primary pod are scheduled to same node using the following commands:

    kubectl get all -n <primary pod namespace> -o wide

    kubectl get all -n <operator pod namespace> -o wide

  2. If it is allocated to same node then create new node with same node selector given in CR for primary server.
  3. Delete the Primary pod which is in pending state.

    The newly created Primary pod must not be in pending state now.

Feedback

Was this page helpful?
Previous

Host validation failed on the target host

Next

Taint, Toleration, and Node affinity related issues in cpServer

Feedback

Was this page helpful?