NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
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 and a configmap.
Initially pod will be in not ready state (0/1) when installation is going on in the background. Check the pod logs for installation progress using the following command:
kubectl logs <primary-pod-name> -n <namespace>
Primary server can be considered as successfully installed and running when the primary server pod's state is ready (1/1) and the Statefulset is ready (1/1).
You can access the NetBackup webUI 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.