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
Deleting a cloud LSU
Use the following steps carefully to remove an MSDP cloud LSU:
- Expire all images of the cloud LSU in NetBackup.
- Remove the storage unit and disk pool of this MSDP cloud LSU.
- Delete all S3 buckets of the cloud LSU if MSDP S3 is configured.
- To delete a cloud LSU, storageId and CachePath are needed.
Run following command to get the information of one cloud LSU:
/usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu dsid, lsuname, storageId, CachePath 3, S3Volume, server1_ S3Volume/cloud-bucket1/sub1, /msdp/data/ds_3 4, S3Volume2, server1_ S3Volume2/cloud-bucket1/sub2, /msdp/data/ds_4
Here the storageId of the cloud LSU is "server1_ S3Volume/cloud-bucket1/sub1" and CachePath of the cloud LSU is "/msdp/data/ds_3"
- Run CRQP to make sure no tlog entries are present in
<msdp_storage_path>/spool
folder and<msdp_storage_path>/queue
folder. - Delete LSU configurations in spad by using nbdevconfig command.
Configuration file contents for deleting an MSDP cloud LSU configuration are as follows:
Configuration setting
Description
V7.5 "operation" "delete-lsu-cloud" string
The value "delete-lsu-cloud" for deleting the MSDP cloud LSU configurations in spad.
V7.5 "lsuName" " " string
Specifies the LSU name.
For example:
V7.5 "operation" "delete-lsu-cloud" string V7.5 "lsuName" "s3amazon1" string
After creating the configuration file, run the following command:
# /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <storage server> -stype PureDisk -configlist <configuration file path>
- Stop the MSDP service and its monitor service.
# /usr/openv/netbackup/bin/nbsvcmon -terminate
# /usr/openv/pdde/pdconfigure/pdde stop
- Delete LSU configurations in spoold using the following command:
# /usr/openv/pdde/pdcr/bin/spoold --removepartition <storageId>
- Remove the cache and other back-end folders by using the following commands (Optional):
# rm -r <CachePath>
# rm -r <msdp_storage_path>/spool/ds_<dsid>
# rm -r <msdp_storage_path>/queue/ds_<dsid>
# rm -r <msdp_storage_path>/processed/ds_<dsid>
# rm -r <msdp_storage_path>/databases/refdb/ds_<dsid>
# rm -r <msdp_storage_path>/databases/datacheck/ds_<dsid>
- Remove the entire sub-bucket folder in cloud. (Optional)
- Start the MSDP service and its monitor service.
# /usr/openv/pdde/pdconfigure/pdde start
# /usr/openv/netbackup/bin/nbsvcmon
- Delete the cloud instance alias.
# /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -rs -in <instance_name> -sts <storage_server_name>_<lsu_name>