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 Key Management Server 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
- Running MSDP services with the non-root user
- 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 bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- 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
- Disaster recovery in S3 interface for MSDP
- 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
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- 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 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
Configuring the cloud compaction
Cloud compaction replaces the existing container with the garbage with a new smaller container without the garbage. It is similar to compaction for local storage. In the compaction process, containers that meet the conditions are downloaded from object cloud storage to local copies. Compaction removes garbage in the local copies and uploads them to overwrite the old objects in the cloud. In this process, data is transferred to and from cloud storage and may incur extra cost. It also needs reasonable bandwidth for compaction to work efficiently. Hence, cloud compaction is disabled by default. It can be enabled in the deployment where cost and bandwidth are not a problem. For example, it's recommended to enable it in a private cloud or in case MSDP is deployed in the same cloud as object storage.
Limitations:
WORM cloud LSU is not supported.
Buckets with versioning enabled are not supported.
CloudCatalyst migration system is not supported.
MSDP Cluster deployments (AKS, EKS, NBFS) are not supported.
You can configure cloud compaction with the following options in cloud.json
Parameter | Description | Default value |
---|---|---|
CompactEnable | Enable or disable cloud compaction. | false |
CompactBatchNum | The number of containers for cloud compaction each time. | 400 |
EnableCompactCandidateCheck | Enable or disable cloud compaction check. This value is available when CompactEnable is true. | true |
CompactLboundMB | Filter the containers that have garbage size less than this value for cloud compaction. | 16 |
CompactSizeLboundMB | Filter the containers with the size less than this value for cloud compaction. | 32 |
CompactMaxPo | Filter the containers that are referenced more than this number of path objects for cloud compaction. | 100 |
To update the cloud compaction parameters using crcontrol command line
- Enable cloud compaction for one cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudcompacton <dsid>
This command enables compaction temporarily. To enable compaction permanently, update CompactEnable value manually in
cloud.json
.Container aging is disabled automatically when cloud compaction is enabled.
- Disable cloud compaction for one cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudcompactoff <dsid>
To disable compaction permanently, update CompactEnable manually in
cloud.json
, and restart spoold. - Show cloud compaction state for all cloud LSUs.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudcompactstate