NetBackup™ Deployment Guide for Kubernetes Clusters

Scenario 1: MSDP Scaleout and its data is lost and the NetBackup primary server remains unchanged and works well

1. Redeploy MSDP Scaleout on a cluster by using the same CR parameters and NetBackup re-issue token.
2. If the LSU cloud alias does not exist, you can use the following command to add it.

   /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in <instance-name> -sts <storage-server-name> -lsu_name <lsu-name>

   When MSDP Scaleout is up and running, re-use the cloud LSU on NetBackup primary server.

   /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <STORAGESERVERNAME> -stype PureDisk -configlist <configuration file>

   Credentials, bucket name, and sub bucket name must be the same as the recovered Cloud LSU configuration in the previous MSDP Scaleout deployment.

   Configuration file template:

   V7.5 "operation" "reuse-lsu-cloud" string
   V7.5 "lsuName" "LSUNAME" string
   V7.5 "cmsCredName" "XXX" string
   V7.5 "lsuCloudAlias" "<STORAGESERVERNAME_LSUNAME>" string
   V7.5 "lsuCloudBucketName" "XXX" string
   V7.5 "lsuCloudBucketSubName" "XXX" string
   V7.5 "lsuKmsServerName" "XXX" string

   Note:

   For Veritas Alta Recovery Vault Azure storage, the cmsCredName is a credential name and cmsCredName can be any string. Add recovery vault credential in the CMS using the NetBackup web UI and provide the credential name for cmsCredName. For more information, see About Veritas Alta Recovery Vault Azure topic in NetBackup Deduplication Guide.

3. On the first MSDP Engine of MSDP Scaleout, run the following command for each cloud LSU:

   sudo -E -u msdpsvc /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr <LSUNAME>

4. Restart the MSDP services in the MSDP Scaleout.

   Option 1: Manually delete all the MSDP engine pods.

   kubectl delete pod <sample-engine-pod> -n <sample-cr-namespace>

   Option 2: Stop MSDP services in each MSDP engine pod. MSDP service starts automatically.

   kubectl exec <sample-engine-pod> -n <sample-cr-namespace> -c uss-engine -- /usr/openv/pdde/pdconfigure/pdde stop

   Note:

   After this step, the MSDP storge server status may appear as down on the NetBackup primary server. The status changes to up automatically after the MSDP services are restarted in a few minutes.

   If the status does not change, run the following command on the primary server to update MSDP storage server status manually:

   /usr/openv/volmgr/bin/tpconfig -update -storage_server <storage-server-name> -stype PureDisk -sts_user_id <storage-server-user-name> -password <storage-server-password>

5. If MSDP S3 service is configured, restart MSDP S3 service after MSDP services are restarted.

   kubectl exec <sample-engine-pod> -n <sample-cr-namespace> -c uss-engine -- systemctl restart pdde-s3srv

Scenario 2: MSDP Scaleout and its data is lost and the NetBackup primary server was destroyed and is re-installed

1. Redeploy MSDP Scaleout on a cluster by using the same CR parameters and new NetBackup token.
2. When MSDP Scaleout is up and running, reuse the cloud LSU on NetBackup primary server.

   /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <STORAGESERVERNAME> -stype PureDisk -configlist <configuration file>

   Credentials, bucket name, and sub bucket name must be the same as the recovered Cloud LSU configuration in previous MSDP Scaleout deployment.

   Configuration file template:

   V7.5 "operation" "reuse-lsu-cloud" string
   V7.5 "lsuName" "LSUNAME" string
   V7.5 "cmsCredName" "XXX" string
   V7.5 "lsuCloudAlias" "<STORAGESERVERNAME_LSUNAME>" string
   V7.5 "lsuCloudBucketName" "XXX" string
   V7.5 "lsuCloudBucketSubName" "XXX" string
   V7.5 "lsuKmsServerName" "XXX" string

   If KMS is enabled, setup KMS server and import the KMS keys.

   If the LSU cloud alias does not exist, you can use the following command to add it.

   /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in <instance-name> -sts <storage-server-name> -lsu_name <lsu-name>

   Note:

   For Veritas Alta Recovery Vault Azure storage, the cmsCredName is a credential name and cmsCredName can be any string. Add recovery vault credential in the CMS using the NetBackup web UI and provide the credential name for cmsCredName. For more information, see About Veritas Alta Recovery Vault Azure topic in NetBackup Deduplication Guide.

3. On the first MSDP Engine of MSDP Scaleout, run the following command for each cloud LSU:

   sudo -E -u msdpsvc /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr <LSUNAME>

4. Restart the MSDP services in the MSDP Scaleout.

   Option 1: Manually delete all the MSDP engine pods.

   kubectl delete <sample-engine-pod> -n <sample-cr-namespace>

   Option 2: Stop MSDP services in each MSDP engine pod.

   kubectl exec <sample-engine-pod> -n <sample-cr-namespace> -c uss-engine -- /usr/openv/pdde/pdconfigure/pdde stop

   Note:

   After this step, the MSDP storge server status may appear as down on the NetBackup primary server. The status changes to up automatically after the MSDP services are restarted in a few minutes.

   If the status does not change, run the following command on the primary server to update MSDP storage server status manually:

   /usr/openv/volmgr/bin/tpconfig -update -storage_server <storage-server-name> -stype PureDisk -sts_user_id <storage-server-user-name> -password <storage-server-password>

5. If MSDP S3 service is configured, restart MSDP S3 service after MSDP services are restarted.

   kubectl exec <sample-engine-pod> -n <sample-cr-namespace> -c uss-engine -- systemctl restart pdde-s3srv

6. Create disk pool for the cloud LSU on NetBackup server.
7. Do two-phase image importing.

   See the NetBackup Administrator's Guide, Volume I