NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Prerequisites for Kubernetes cluster configuration
- Prerequisites for Cloud Scale configuration
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Prerequisites
- 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 logging
- 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
After installing primary server CR
Note the following points:
(AKS-specific) The primary server CR will create a pod, a statefulset, a load balancer service, a configmap, a persistent volume claim for log volume, and a persistent volume claim for catalog volume.
(EKS-specific) The primary server CR will create a pod, a statefulset, a load balancer service, a configmap and PVCs.
Primary server can be considered as successfully installed and running when log-viewer, nbatd, nbmqbroker, nbwsapp, policyjob, policyjobmgr, primary, requestrouter pods successfully got into running state.
You can access the NetBackup Web UI using the
that was specified in the primary server CR status in section.For example, if the primary server hostname is
, then you can access the webUI at https://nbu-primary/webui/login.Check the installation progress in the pod logs by using the following command:
kubectl logs <request-router-pod-name> -n <namespace>
Request router can be considered as successfully installed and running when the request router pod's state is ready (1/1).