To backup a catalog automatically

1. A catalog backup policy can be automatically configured during a new installation. This can be done by supplying the DR Secret through the drInfoSecret field of the environment.Spec in helm/values.yaml file.
2. The drInfoSecret field must be created before deployment using the following command:

   kubectl create secret generic dr-info-secret --namespace <nbu-namespace> --from-literal=passphrase="Y@123abCdEf" --from-literal=emailAddress="abc@xyz.com"

   The passphrase field is compulsory.

3. Once catalog policy is created, configure Recovery Vault storage in the catalog backup policy. For more information, see NetBackup Deduplication Guide.
4. In the automatically configured catalog backup policy, the DR package path is set to /mnt/nbdb/usr/openv/drpackage_<storage server name>. If required, this can be changed by editing the policy from the Web UI.
5. If the email field is included in the DR Secret, then on running a catalog backup job, the created DRPackages would be sent through email. this is applicable only when the e-mail server is configured. Configuring email server

To backup a catalog manually

1. Exec into the primary server pod using the following command:

   kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash

2. Create a directory DRPackages at persisted location using mkdir /mnt/nblogs/DRPackages.
3. Change ownership of DRPackages folder to service user using chown nbsvcusr:nbsvcusr /mnt/nblogs/DRPackages.
4. Set the passphrase to be used at time of catalog recovery.

   • Click on the Settings icon (located on the top right hand corner of the Web UI).

   • Navigate to Global Security Setting > Disaster Recovery tab.

   • Add the Disaster Recovery passphrase under Enter passphrase and confirm the passphrase, and save it.

5. Add respective external media server entry in host properties through NetBackup Management > Host properties > Master Server > Add Additional server.

   Note:

   It is recommended to use an external media server for catalog backup and recovery.

6. Exec into the primary server pod using the following command:

   kubectl exec -it -n <namespace> <primaryserver pod name> -- bash

   Set the KMS_CONFIG_IN_CATALOG_BKUP configuration option to 1 in /usr/openv/netbackup/bp.conf file of primary server to include the KMS configuration as part of the disaster recovery package during catalog backup.

7. Restart the NetBackup services in primary and external media server.

   • Exec into the primary server pod using the following command:

     kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash

   • Deactivate NetBackup health probes using the /opt/veritas/vxapp-manage/nb-health deactivate command.

   • Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command.

   • Activate NetBackup health probes using the /opt/veritas/vxapp-manage/nb-health activate command.

   • Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command on the external media server.

8. Configure storage unit on earlier added external media server.

   For more information, refer to the NetBackup™ Administrator's Guide,Volume I

   Note:

   It is recommended to use AdvancedDisk or BasicDisk storage unit.

9. Configure NetBackup catalog backup policy.

   Add package path as /mnt/nblogs/DRPackages while configuring the catalog backup policy.

10. Run the catalog backup job.