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
Common disaster recovery steps
Following are the common disaster recovery steps:
Step | Task | Procedure |
---|---|---|
1 | Delete the deduplication configuration. | /usr/openv/pdde/pdconfigure/scripts/installers/PDDE_deleteConfig.sh |
2 | Delete the NetBackup deduplication Engine credentials on load balancing servers. | /usr/openv/volmgr/bin/tpconfig -delete -storage_server sts_hostname -stype PureDisk -sts_user_id root -all_hosts /usr/openv/volmgr/bin/tpconfig -add -storage_server sts_hostname -stype PureDisk -sts_user_id root -password xxx |
3 | Get the config template. | /usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -storage_server sts_hostname -stype PureDisk |
4 | Reuse or create storage path | /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server sts_hostname -stype PureDisk -configlist /root/local-lsu.txt |
Step | Task | Procedure |
---|---|---|
1 | Reuse cloud LSU configuration. | For each cloud LSU: nbdevconfig -setconfig -storage_server sts_hostname -stype PureDisk -configlist /path/to/dr-lsu.txt Config template example 1: 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 Configuration template example 2 with encryption enabled: 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 alias does not exist, you can use the csconfig command to add them. /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in amazon.com -sts <storageserver> -lsu_name <lsuname> |
2 | Recover spad/spoold metadata from cloud. | For each cloud LSU: /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr lsu1 |
3 | Restart storage server. | /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all Warning: The time taken can be high if the siz eof the containers is large. Use the following command to get the status: /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddrstatus lsu |
4 | Start MSDP online check to recreate refdb. | /usr/openv/pdde/pdcr/bin/pddecfg -a enabledataintegritycheck -d <dsid> /usr/openv/pdde/pdcr/bin/pddecfg -a startdatafullcheck -d <dsid> /usr/openv/pdde/pdcr/bin/crcontrol --processqueue --dsid <dsid> Note: -d and --dsid options are optional parameters and applicable for cloud LSU only. Use /usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu to get cloud LSU dsid value. If given disd value is "0", local LSU is processed.. |