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
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- 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
- 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 cloud LSU in Flex Scale
When the NetBackup Flex Scale recovers from a site-based disaster, the backup data in cloud LSU can be recovered by disaster recovery of the cloud LSU.
Considerations before disaster recovery of the cloud LSU:
The secondary NetBackup Flex Scale is ready.
For more information, See the Site-based disaster recovery section of the NetBackup Flex Scale Administrator's Guide.
MSDP storage server is ready and configured with the same configuration.
KMS server is ready and key group in KMS server is ready if MSDP KMS encryption is enabled in this cloud LSU.
To perform the disaster recovery for cloud LSU
- If the cloud instance alias does not exist, run the following command to add the alias.
csconfig cldinstance -as -in amazon.com -sts <storageserver> -lsu_name <lsuname>
- On the NetBackup primary server, run the following command to reuse the cloud LSU. Use the same credentials, bucket name, and sub bucket that were used before the disaster recovery.
nbdevconfig -setconfig -storage_server sts_hostname -stype PureDisk -configlist <configuration file>
Sample configuration file:
If MSDP KMS encryption is enabled in this cloud LSU:
V7.5 "operation" "reuse-lsu-cloud" string V7.5 "lsuCloudUser" "XXX" string V7.5 "lsuCloudPassword" "XXX" string V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string V7.5 "lsuCloudBucketName" "XXX" string V7.5 "lsuCloudBucketSubName" "XXX" string V7.5 "lsuKmsServerName" "XXX" string
If MSDP KMS encryption is disabled in this cloud LSU:
V7.5 "operation" "reuse-lsu-cloud" string V7.5 "lsuCloudUser" "XXX" string V7.5 "lsuCloudPassword" "XXX" string V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string V7.5 "lsuCloudBucketName" "XXX" string V7.5 "lsuCloudBucketSubName" "XXX" string
- On the NetBackup primary server, get the storage server name. On the engines container with the storage server name, run the following command to get the catalog from the cloud:
cacontrol --catalog clouddr <lsuname>
Retry this command if it fails for intermittent network issue.
- Restart the cluster.
- Create the disk pool for the cloud LSU.
- Do two-phase import.