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
  3. NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
  5. Performing catalog backup and recovery
  7. Restoring a catalog
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Restoring a catalog

You can restore a catalog.

To restore a catalog

  1. Copy DRPackages files (packages) located at /mnt/nblogs/DRPackages/ from the pod to the host machine from where Amazon Elastic Kubernetes Service cluster is accessed.

    Run the kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine> command.

  2. Preserve the data of /mnt/nbdata and /mnt/nblogs on host machine by creating tar and copying it using the kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data> command.
  3. Change CR spec from paused: false to paused: true in primary, mediaServers, and msdpScaleouts sections in environment.yaml and re-apply yaml using the kubectl apply -f environment.yaml -n <namespace> command.
  4. Change replica count to 0 in primary server's statefulset using the kubectl edit statefulset <primary-server-statefulset-name> -n <namespace> command.
  5. Get names of PV attached to primary server PVC (catalog, log and data) using the kubectl get pvc -n <namespace> -o wide command.
  6. Delete primary server PVC (catalog, log and data) using the kubectl delete pvc <pvc-name> -n <namespace> command.
  7. Delete the PV linked to primary server PVC using the kubectl delete pv <pv-name> command.
  8. Navigate to mounted EFS directory and delete the content from primary_catalog folder by running the rm -rf /efs/* command.
  9. Change CR spec paused: true to paused: false in primary server section in environment.yaml and reapply yaml with the kubectl apply -f environment.yaml -n <namespace> command.
  10. After the primary server pod is in ready state, change CR spec from paused: false to paused: true in primary server section in environment.yaml and reapply yaml with the kubectl apply -f environment.yaml -n <namespace> command.
  11. Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.

    • Increase the debug logs level on primary server.

    • Create a directory DRPackages at persisted location using mkdir /mnt/nblogs/DRPackages.

    • Change ownership of the DRPackages folder to service user using the chown nbsvcusr:nbsvcusr /mnt/nblogs/DRPackages command.

  12. Copy earlier copied DR files to primary pod at /mnt/nblogs/DRPackages using the kubectl cp <Path_of_DRPackages_on_host_machine> <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages command.
  13. Execute the following steps in the primary server pod.

    • Change ownership of files in /mnt/nblogs/DRPackages using the chown nbsvcusr:nbsvcusr <file-name> command.

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

    • Stop the NetBackup services using /usr/openv/netbackup/bin/bp.kill_all.

    • Execute the nbhostidentity -import -infile /mnt/nblogs/DRPackages/<filename>.drpkg command.

    • Restart all the NetBackup services using /usr/openv/netbackup/bin/bp.start_all.

  14. Verify security settings are back.
  15. Add respective media server entry in host properties using NetBackup Administration Console.

    • Navigate to NetBackup Management > Host properties > Master Server > Add Additional server and add media server.

  16. Restart the NetBackup services in primary server pod and external media server.

    • Execute the following command in the primary server pod:

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

    • Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the same using the /usr/openv/netbackup/bin/bp.start_all 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.

  17. Configure a storage unit on external media server that is used during catalog backup.
  18. Perform catalog recovery from NetBackup Administration Console.

    For more information, refer to the NetBackup Troubleshooting Guide.

  19. Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.

    • Stop the NetBackup services using the /usr/openv/netbackup/bin/bp.kill_all command.

    • Start NetBackup 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.

  20. Change CR spec from paused: true to paused: false in primary, mediaServers, and msdpScaleouts sections in environment.yaml and re-apply yaml using the kubectl apply -f environment.yaml -n <namespace> command.
  21. To configure NetBackup IT Analytics refer to the following topic.

    See Configuring NetBackup IT Analytics for NetBackup deployment.

Feedback

Was this page helpful?
Previous

Backing up a catalog

Next

Managing MSDP Scaleout

Feedback

Was this page helpful?