Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
Last Published:
2022-09-08
Product(s):
NetBackup (10.1)
- Introduction to NetBackup on EKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- Preparing the environment for NetBackup installation on EKS
- Recommendations of NetBackup deployment on EKS
- Limitations of NetBackup deployment on EKS
- 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 group 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 EKS
- 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 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
- Resolving the primary server connection issue
- Primary pod is in pending state for a long duration
- Host mapping conflict in NetBackup
- NetBackup messaging queue broker take more time to start
- Local connection is getting treated as insecure connection
- Issue with capacity licensing reporting which takes longer time
- Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
- Appendix A. CR template
Resolving an issue related to invalid nodepool
Invalid nodepool is mentioned in primary server or media server CR nodeSelector spec. Due to this, primary server or media server pod fails to schedule.
The following error is displayed:
Error: Did not match Pod's node affinity/selector.
To resolve an issue related to invalid nodepool
- If you are deploying NetBackup on Amazon Elastic Kubernetes Service Cluster for the first time, delete the respective CR.
If it is primary server CR:
Delete it using the kubectl delete -f <environment.yaml> command.
Update the node selector in primary server section in
environment.yamland apply it again using the kubectl apply -f <environment.yaml> command.
- For media server CR: Delete the media server CR by removing the mediaServer section in the
environment.yamland save the changes.Note:
Ensure that you copy spec information of the media server CR. The spec information is used to reapply the media server CR.
- Apply the new changes using the kubectl apply -f <environment.yaml> command.
- Add the mediaServer section, update the nodeSelector, and reapply the
environment.yamlusing the kubectl apply -f <environment.yaml> command.