Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
  3. Performing catalog backup and recovery
  4. Backing up a catalog
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Backing up a catalog

You can backup a catalog.

To backup a catalog

  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.
    • Open NetBackup Administrator Console (Java UI).

    • Navigate to Security Management > Global Security Setting > Disaster Recovery.

    • In Encryption for Disaster Recovery section, add the passphrase, confirm 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:

    kuebctl 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/nbu-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/nbu-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.

Feedback

Was this page helpful?
Previous

Performing catalog backup and recovery

Next

Restoring a catalog

Feedback

Was this page helpful?