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
Managing an Azure cloud immutable volume using msdpcldutil tool
MSDP cloud admin tool /usr/openv/pdde/pdcr/bin/msdpcldutil
is used to manage cloud immutable volume.
You can create an Azure cloud immutable volume in the following scenarios:
Azure storage account has enabled version-level immutability support.
The container is created through Azure portal and has enabled version-level immutability support.
You use Azure service principal.
For information about immutability policies configurations in Azure, see Configure immutability policies for blob versions
To create a cloud volume when version-level immutability support is enabled:
- Set the following environment variables:
# export MSDPC_REGION=<your region> # export MSDPC_PROVIDER=azure # export MSDPC_ACCESS_KEY=<your storage account> # export MSDPC_SECRET_KEY=<your access key> # export MSDPC_ENDPOINT=https://<your storage acount>.blob.core.windows.net/
- Create a cloud immutable volume.
# msdpcldutil create -b bucketname -v volumename --mode ENTERPRISE --min 1D --max 30D --live 2022-12-31
ENTERPRISE is unlocked policy and COMPLIANCE is locked policy in Azure.
- List the cloud volumes.
#/usr/openv/pdde/pdcr/bin/msdpcldutil list
- 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
- Update the cloud immutable volume live duration.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update live -b bucketname -v volumename -l 2023-01-31
- List cloud immutable storage cloud providers.
#/usr/openv/pdde/pdcr/bin/msdpcldutil platform list
To create a cloud volume when the container is created through Azure portal and has enabled version-level immutability support:
- Set the following environment variables:
# export MSDPC_REGION=<your region> # export MSDPC_PROVIDER=azure # export MSDPC_ACCESS_KEY=<your storage account> # export MSDPC_SECRET_KEY=<your access key> # export MSDPC_ENDPOINT=https://<your storage acount>.blob.core.windows.net/
- Create a cloud immutable volume.
# msdpcldutil create -b bucketname -v volumename --mode ENTERPRISE --min 1D --max 30D --live 2022-12-31
ENTERPRISE is unlocked policy and COMPLIANCE is locked policy in Azure.
- List the cloud volumes.
#/usr/openv/pdde/pdcr/bin/msdpcldutil list
- 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
- Update the cloud immutable volume live duration.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update live -b bucketname -v volumename -l 2023-01-31
- List cloud immutable storage cloud providers.
#/usr/openv/pdde/pdcr/bin/msdpcldutil platform list
To create a cloud volume using Azure service principal:
- Set the following environment variables:
# export MSDPC_REGION=<your region> # export MSDPC_PROVIDER=azure # export MSDPC_ACCESS_KEY=<your storage account> # export MSDPC_SECRET_KEY=<your access key> # export MSDPC_ENDPOINT=https://<your storage acount>.blob.core.windows.net/ # export MSDPC_SUBSCRIPTION_ID=<your subscription id > # export MSDPC_RESOURCE_GROUP=<resource group storage acct is in> # export AZURE_TENANT_ID=<azure tenant id> # export AZURE_CLIENT_ID=<azure client id> # export AZURE_CLIENT_SECRET=<azure client secret>
- Create a cloud immutable volume.
# msdpcldutil create -b bucketname -v volumename --mode ENTERPRISE --min 1D --max 30D --live 2022-12-31
ENTERPRISE is unlocked policy and COMPLIANCE is locked policy in Azure.
- List the cloud volumes.
#/usr/openv/pdde/pdcr/bin/msdpcldutil list
- 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
- Update the cloud immutable volume live duration.
#/usr/openv/pdde/pdcr/bin/msdpcldutil update live -b bucketname -v volumename -l 2023-01-31
- List cloud immutable storage cloud providers.
#/usr/openv/pdde/pdcr/bin/msdpcldutil platform list