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
NetBackup messaging queue broker take more time to start
This issue is due to service taking more time to start.
To resolve this issue, perform the following steps
- Exec into the respective Primary Server pod using the following command:
kubectl exec -it <pod-name> -n <namespace> -- /bin/bash
- Check the nbmqbroker service logs which are in
/usr/openv/mqbroker/logs/folder.If the value of checking service start status count: is more than the 75 then nbmqbroker would take more time to start.
- Stop the nbmqbroker service using the following command:
/usr/openv/mqbroker/bin/nbmqbroker stop
- Open the
/usr/openv/mqbroker/bin/nbmqbrokerfile. - Increase the value of total_time and sleep_duration and save the file.
- Start the mqbroker service using the following command:
/usr/openv/mqbroker/bin/nbmqbroker start
If the Primary Server pod gets restarted then the user must perform the same above steps to increase the values of total_time and sleep_duration, as these values will not get persisted after pod restart.