Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2024-06-17
Product(s):
NetBackup & Alta Data Protection (10.4.0.1)
- Introduction
- Section I. Configurations
- Prerequisites
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Section II. Deployment
- Section III. Monitoring and Management
- Monitoring NetBackup
- Monitoring Snapshot Manager
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- Section IV. Maintenance
- MSDP Scaleout Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for Primary and Media servers
- Upgrading
- Cloud Scale Disaster Recovery
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
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
- 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
- If it is allocated to same node then create new node with same node selector given in CR for primary server.
- Delete the Primary pod which is in pending state.
The newly created Primary pod must not be in pending state now.