Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2025-02-26
Product(s):
NetBackup & Alta Data Protection (10.5.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 fluentbit
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Managing fluentbit
- Performing catalog backup and recovery
- Section IV. Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for primary, media servers, fluentbit pods, and postgres pods
- 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
- Appendix B. MSDP Scaleout
- MSDP Scaleout configuration
- Managing MSDP Scaleout
- MSDP Scaleout maintenance
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/nbmqbroker
file. - 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.