Configuring MSDP Scaleout
After you push the docker images to ACR and initialize MSDP operator, configure MSDP Scaleout.
To configure MSDP Scaleout
- Create a dedicated namespace for MSDP Scaleout to run.
kubectl create ns <sample-namespace>
- Create an MSDP Scaleout Secret. The Secret is used in CR.
kubectl apply -f <secret-yaml-file>
See Secret.
- (Optional) Create an MSDP S3 root credential secret. The secret is used in CR.
$ kubectl msdp generate-s3-secret --namespace <sample-namespace> --s3secret <s3-secret-name>
- Display the custom resource (CR) template.
kubectl msdp show -c
- Save the CR template.
kubectl msdp show -c -f <file path>
- Edit the CR file in the text editor.
- Apply the CR file to the cluster.
Caution:
Add MSDP_SERVER = <first Engine FQDN> in
/usr/openv/netbackup/bp.conffile on the NetBackup primary server before applying the CR YAML.kubectl apply -f <sample-cr-yaml>
- Monitor the configuration progress.
kubectl get all -n <namespace> -o wide
In the STATUS column, if the readiness state for the controller, MDS and engine pods are all Running, it means that the configuration has completed successfully.
In the READY column for engines, 2/2 or 3/3 indicates that the engine configuration has completed successfully.
- If you specified spec.autoRegisterOST.enabled: true in the CR, when the MSDP engines are configured, the MSDP operator automatically registers the storage server, a default disk pool, and a default storage unit in the NetBackup primary server.
A field ostAutoRegisterStatus in the Status section indicates the registration status. If ostAutoRegisterStatus.registered is True, it means that the registration has completed successfully.
You can run the following command to check the status:
kubectl get msdpscaleouts.msdp.veritas.com -n <sample-namespace>
You can find the storage server, the default disk pool, and storage unit on the Web UI of the NetBackup primary server.