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
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 <user_id> -all_hosts /usr/openv/volmgr/bin/tpconfig -add -storage_server <sts_hostname> -stype PureDisk -sts_user_id <user_id> -password <your_passwd> |
3 | Redirect the command output to a file to prepare the config template. | /usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -storage_server <sts_hostname> -stype PureDisk >/root/local-lsu.txt The content of the file local-lsu.txt V7.5 "storagepath" " " string V7.5 "spalogin" " " string V7.5 "spapasswd" " " string .... V7.5 "kmsservername" " " string V7.5 "keygroupname" " " string V7.5 "extendedcapabilities" " " string V7.5 "imagesharingincloud" "false" string |
4 | Generate the config template. | Make changes to the template file Parameters: /root/local-lsu.txt V7.5 "storagepath" "/Storage" string V7.5 "spalogin" "my-user-name" string V7.5 "spapasswd" "my-password" string V7.5 "spalogretention" "90" int V7.5 "verboselevel" "3" int For more information about the parameters, See Editing an MSDP storage server configuration file. |
5 | 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 | Get LSU name before you reuse cloud LSU configuration. | Run any of the following commands to get the LSUs (disk volumes) on this MSDP server. /usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -stype PureDisk -U /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -U Sample output: Disk Pool Name : my-aws-pool Disk Type : PureDisk Disk Volume Name : my-aws-lsu Disk volume name is LSU name. In this sample, LSU name is my-aws-lsu. |
2 | Prepare a template file and save it. | Config template example 1 : V7.5 "operation" "reuse-lsu-cloud" string V7.5 "lsuCloudUser" "your-acct-id" string V7.5 "lsuCloudPassword" "your-secret" string V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string V7.5 "lsuCloudBucketName" "bucket-name" string V7.5 "lsuCloudBucketSubName" "lsuname" string V7.5 "requestCloudCacheCapacity" "1017" string Configuration template example 2 with encryption enabled: V7.5 "operation" "reuse-lsu-cloud" string V7.5 "lsuCloudUser" "your-acct-id" string V7.5 "lsuCloudPassword" "your-secret" string V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string V7.5 "lsuCloudBucketName" "bucket-name" string V7.5 "lsuCloudBucketSubName" "lsuname" string V7.5 "lsuKmsServerName" "FQDN-KMS-server-host" string V7.5 "requestCloudCacheCapacity" "1017" string |
3 | Check if lsuCloudAlias exist. | Run the following command to list the instances to check if lsuCloudAlias exist. /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -i | grep <lsuname> If an alias does not exist, run the following command to add them. /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in <cloud_privder_name> -sts <storageserver> -lsu_name <lsuname> Run the following command to find the cloud_privder_name: /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -l |
4 | Reuse cloud LSU configuration. | Run the following command for each LSU to configure the cloud LSU. /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <storageserver> -stype PureDisk -configlist /root/dr-lsu.txt |
5 | Recover spad/spoold metadata from cloud. | For each cloud LSU perform the previous four steps, and then run the following command. /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr <lsuname> Note: The time to run this command depends on the size of the containers. Run the following command to get the catalog recovery status: /usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddrstatus <lsuname> |
6 | Restart storage server. | /usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all |
7 | 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. |