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
- S3 Interface for MSDP
- Configuring S3 interface for MSDP
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Monitoring deduplication activity
- Viewing MSDP job details
- 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
- 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 and 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 hostname of the computer the disaster recovery is performed on must match the hostname the shares were originally created on. Also, you must make a copy of the auth.key
file because the file is required for the disaster recovery.
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 a disaster recovery for all universal shares
- Navigate to the following location on the media server:
/usr/openv/pdde/vpfs/bin
- Ensure that the
auth.key
file in your storage path is the same as when a share was last created or deleted. The file contents may be different if you perform a universal share disaster recovery after a regular MSDP disaster recovery. - Run the following:
./vpfs_actions -a disasterRecovery --cloudVolume CLOUDVOLUMENAME
(where cloudVolume is the name of the MSDP cloud volume)
- Revert your
auth.key
file if you replaced it in step 2. - 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.
NetBackup calls the vpfsadm --ioctlProxy command to recreate the shares locally.
NetBackup 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.