NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
- Introduction to NetBackup on AKS
- Deployment with environment operators
- Assessing cluster configuration before deployment
- Deploying NetBackup
- About primary server CR and media server CR
- Upgrading NetBackup
- Deploying MSDP Scaleout
- Upgrading MSDP Scaleout
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Managing the Load Balancer service
- Performing catalog backup and recovery
- Managing MSDP Scaleout
- About MSDP Scaleout maintenance
- Uninstalling MSDP Scaleout from AKS
- Troubleshooting
- Appendix A. CR template
About MSDP Scaleout components
Following are the MSDP Scaleout components:
MDS (MetaData service)
MDS is an independent and stackable service that provides a single system view of MSDP Scaleout. It's an etcd cluster running inside the MDS pods. These pods run on different AKS nodes. The pod name has a format of <cr-name>-uss-mds-<1,2...>.
The number of pods that get created depends on the number of MSDP Scaleout engines in AKS cluster. These pods are controlled by the MSDP operator.
1 or 2 MSDP Scaleout engines: 1 pod
3 or 4 MSDP Scaleout engines: 3 pods
5 or more MSDP Scaleout engines: 5 pods
MSDP Scaleout Controller
Controller is a singleton service and the entry point of MSDP Scaleout that monitors and repairs MSDP Engines. It controls and manages the application-level business of the MSDP Scaleout. The Deployment object name has a format of <cr-name>-uss-controller. It is controlled by the MSDP operator.
MSDP Scaleout Engine
MSDP Engines provide the ability to write deduplicated data to the storage. The name of a MSDP engine pod is the corresponding FQDN of the static IP that is specified in the CR. Each MSDP engine pod has MSDP services such as spad, spoold, and ocsd running. They are controlled by the MSDP operator.