Disaster recovery for a universal share

Universal share disaster recovery is available for BYO, AKS, and EKS environments when data in a share has been 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. Also, you must have a copy of the auth.key file that is used to encrypt the export lists during the last universal share creation or deletion.

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.

Note:

Universal share disaster recovery is supported only when there is one cloud volume configured.

Performing a disaster recovery for cloud-configured universal shares

Navigate to the following location on the media server:
```
/usr/openv/pdde/vpfs/bin
```
If you have not performed a regular MSDP disaster recovery before, reupload your NFS export list if you have NFS shares using the following command:
```
./vpfscld --upload_export_list --dsid <dsid> --share_type nfs
```
Upload your SMB export list again if you have SMB shares using the following command:
```
./vpfscld --upload_export_list --dsid <dsid> --share_type smb
```
To get the dsid for the cloud volume, run the following command:
```
./vpfscld --get_dsid <dsid> --lsu <volumeName>
```
This action ensures that there are no discrepancies between the cloud export lists and the local export lists.
Run the following:
```
./vpfs_actions -a disasterRecovery --cloudVolume CLOUDVOLUMENAME 
--authKeyFile LASTAUTHKEYFILE
```
Where cloudVolume is the name of the MSDP cloud volume and authKeyFile is the location of the auth.key file that was present during the last universal share creation or deletion.
If you have not performed a regular MSDP disaster recovery before, you can use <MSDP directory>/var/keys/auth.key. If you have performed a regular MSDP disaster recovery and have a new auth.key file, specify the location of the copy of your original auth.key file.
NetBackup automatically performs the following:
- Downloads all of the share scripts from the MSDP cloud volume bucket except for vpfs0.sh which should be recovered during MSDP disaster recovery. NetBackup also adds executable permissions to the scripts.
- Downloads the NFS export list (if it exists) from the cloud.
- Downloads the SMB export list (if it exists) from the cloud.
- Recovers the shares locally.
- Mounts the shares for recovery.
  - Restart the NetBackup server if it's BYO.
    Stop all NetBackup services using /usr/openv/netbackup/bin/goodies/netbackup stop.
    Start all NetBackup services using /usr/openv/netbackup/bin/goodies/netbackup start.
  - Restart the MSDP node if it's in the MSDP cluster.
If you have performed a regular MSDP disaster recovery before, run the following commands:
For NFS shares:
```
./vpfscld --upload_export_list --dsid --share_type nfs
```
For SMB shares:
```
./vpfscld --upload_export_list --dsid <dsid> --share_type smb
```
To get the dsid for the cloud volume, run the following command:
```
./vpfscld --get_dsid --lsu <volumeName>
```
These commands encrypt and re-upload the export lists for each share type using the new auth.key file.

Disaster recovery for a universal share

Feedback

Feedback