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
MSDP Scaleout CR
The CR name must be fewer than 40 characters.
The MSDP credentials stored in the Secret must match MSDP credential rules.
MSDP CR cannot be deployed in the namespace of MSDP operator. It must be in a separate namespace.
You cannot reorder the IP/FQDN list. You can update the list by appending the information.
You cannot change the storage class name.
The storage class must be backed with:
AKS: Azure disk CSI storage driver "disk.csi.azure.com"
EKS: Amazon EBS CSI driver "ebs.csi.aws.com"
You cannot change the data volume list other than for storage expansion. It is append-only and storage expansion only. Up to 16 data volumes are supported.
Like the data volumes, the catalog volume can be changed for storage expansion only.
You cannot change or expand the size of the log volume by changing the MSDP CR.
You cannot enable NBCA after the configuration.
Once KMS and the OST registration parameters set, you cannot change them.
You cannot change the core pattern.