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
Adding data volumes
You can add the data volumes by updating the CR.
To add the data volumes by updating the CR YAML file
- Open the CR YAML file to edit.
- Append the new data volume specifications in the spec.dataVolumes field.
- Apply new CR YAML to update the CR in the Kubernetes environment.
kubectl apply -f <your-cr-yaml>
To add the MSDP engine using the kubectl command directly
- Run the following command to append new data volume specifications in the spec.dataVolumes field.
kubectl -n <sample-namespace> edit msdpscaleout <your-cr-name> [-o json | yaml]
In the MSDP engine pod, the first data volume is mounted on /msdp/data/dp1/pdvol
. Nth data volume is mounted on /msdp/data/dp1/${N-1}pdvol
. For example, 2nd data volume is mounted on /msdp/data/dp1/1pdvol
.
Each MSDP engine can support up to 16 data volumes.
It is recommended that you use the same data volume size if you add multiple volumes.
Note:
Due to some Kubernetes restrictions, MSDP operator restarts the engine pods for attaching the existing and new volumes, which can cause the short downtime of the services.