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
Managing AWS S3 immutable storage using msdpcldutil tool
MSDP cloud admin tool /usr/openv/pdde/pdcr/bin/msdpcldutil
is used to manage immutable.
Before using this tool, set the following environment variables:
export MSDPC_ACCESS_KEY=xxxx export MSDPC_SECRET_KEY=yyyyyyyyyyyyy export MSDPC_REGION=us-east-1 export MSDPC_PROVIDER=amazon
For Amazon S3, MSDPC_ACCESS_KEY is the AWS access key associated with an IAM user. MSDPC_SECRET_KEY is the secret key associated with the access key. MSDPC_REGION is the AWS region where the bucket will be created or accessed.
Perform the following tasks to create the immutable storage and configure it:
Create a cloud immutable volume.
#/usr/openv/pdde/pdcr/bin/msdpcldutil create -b bucketname -v volumename --mode GOVERNANCE --min 1D --max 30D --live 2021-12-31
List the cloud volumes.
#/usr/openv/pdde/pdcr/bin/msdpcldutil list
Update the cloud immutable volume mode.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update mode -b bucketname -v volumename --mode COMPLIANCE --live 2021-12-31 --inherit enable
--inherit disable If your Governance mode data is testing and does not need to be protected, you must use this option.
--inherit enable If you want to protect the Governance mode data, you must use this option.
The volume retention mode can switch from governance to compliance. It cannot switch from compliance to governance. After governance mode is switched to the compliance mode, the new backup image retention mode is compliance. When the mode is switched from governance to compliance mode, due to the nature of deduplication, the images in compliance mode may share some data in the previous images in governance data. Users then have a choice to lock this shared data in either existing governance mode or in compliance mode.
Update the cloud immutable volume min and max retention period.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update range -b bucketname -v volumename --min 1D --max 90D
# /usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedv -stype PureDisk -dp disk_pool_name -dv volumename
The minimum and maximum values are defined by the min and max options. Both values must be between 1 day and 30 years. The maximum value must be less than the volume live duration.
Update the cloud immutable volume live duration.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update live -b bucketname -v volumename -l 2022-01-31
The volume has live period property, which is a timestamp. The backup image retention time must be less than this timestamp. If the live period expires, the volume stops and the backup job fails with the following error message in job details:
Critical bptm (pid=xxxxx) Failed to set WORM immutable and indelible lock for image: clientname_1620671199_C1_IM with status: 2060404 Attempt to WORM lock data past the configured MSDP Cloud lifetime
Cloud administrator can bring the volume back to the running state by extending the live period. You can try the job again.