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
Telemetry reporting
Telemetry reporting entries for the NetBackup deployment on AKS/EKS are indicated with the
text.By default, the telemetry data is saved at the
/var/veritas/nbtelemetry/
location. The default location will not persisted during the pod restarts.If you want to save telemetry data to persisted location, then execute the kubectl exec -it -n <namespace> <primary/media_server_pod_name> - /bin/bash command in the pod using the and execute telemetry command using /usr/openv/netbackup/bin/nbtelemetry with
--dataset-path=DESIRED_PATH
option.Exec into the primary server pod using the following command:
kubectl exec -it -n <namespace> <primary/media_server_pod_name> -- /bin/bash
Execute telemetry command using /usr/openv/netbackup/bin/nbtelemetry with
--dataset-path=DESIRED_PATH
Note:
Here
DESIRED_PATH
must be/mnt/nbdata or /mnt/nblogs
.