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™ Deduplication Guide
  5. Configuring and managing universal shares
  7. Restoring data using universal shares
  9. Disaster recovery for a universal share
NetBackup™ Deduplication Guide

Disaster recovery for a universal share

Universal share disaster recovery is available for BYO, AKS, and EKS environments when data in a share or share-specific metadata is corrupted or deleted.

Before beginning this procedure, verify that data was backed up with a cloud-configured universal share and at least one PIT image exists for each share that is to be recovered. If there is no PIT image, this procedure cannot be used. The host name of the computer the disaster recovery is performed on must match the host name the shares were originally created on.

If the following procedure is performed after a regular MSDP disaster recovery, ensure that NGINX, SPWS, NFS, and SMB are configured as described previously in this chapter.

Performing disaster recovery for all universal shares

  1. Ensure that the vpfs_cloud.cfg file exists at the following location:

    [MSDP storage directory]/etc/puredisk/vpfs_cloud.cfg

    If the file does not exist, run the following command:

    /usr/openv/pdde/vpfs/bin/vpfscld --download_vpfs_cloud_cfg

  2. Ensure that the nfs export list exists at the following location:

    [MSDP storage directory]/etc/vpfs-shares.exports on BYO or [MSDP storage directory]/cat/config/vpfs-shares.exports on AKS or EKS if there are any loud-configured NFS shares.

    If the list does not exist, run the following command:

    /usr/openv/pdde/vpfs/bin/vpfscld --download_export_list --share_type nfs

  3. Ensure that the smb export list exists at the following location:

    [MSDP storage directory]\/etc/vpfs-shares.conf on BYO or [MSDP storage directory]/cat/config/samba/vpfs-shares.conf on AKS or EKS if there are any cloud-configured SMB shares.

    If the list does not exist, run the following command:

    /usr/openv/pdde/vpfs/bin/vpfscld --download_export_list --share_type smb

  4. Restore data to the shares and recover the metadata with the following command:

    /usr/openv/pdde/vpfs/bin/vpfs_actions -a disasterReovery --cloudVolume CLOUDVOLUMENAME

    Where CLOUDVOLUMENAME is the name of the MSDP cloud volume containing the shares you want to restore. If you want to restore shares across multiple cloud volumes, run this command for each cloud volume.

  5. Restart the NetBackup services using the following commands:

    /usr/openv/netbackup/bin/bp.kill_all

    /usr/openv/netbackup/bin/bp.start_all

Feedback

Was this page helpful?
Previous

Restore methods of universal shares

Next

Disaster recovery for universal shares on migrated cloud LSU

Feedback

Was this page helpful?