NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Monitoring deduplication activity
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
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 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 newauth.key
file, specify the location of the copy of your originalauth.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.