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 container aging
Container aging tries to identify the containers that contain a small number of segments but live for a long time, and exclude them from being referenced by new backup images.
The contentrouter.cfg
file has the following aging check related parameters:
Parameter | Description | Default value |
---|---|---|
EnableAgingCheck | Enable or disable Cloud LSU container aging check. | true |
AgingCheckAllContainers | This parameter determines whether to check all containers or not. If set to 'false', it only checks containers in some latest images. | false |
AgingCheckSleepSeconds | Aging check thread wakes up periodically with this time interval (in seconds). | 20 |
AgingCheckBatchNum | The number of containers for aging check each time. | 400 |
AgingCheckContainerInterval | Default interval value of checking a container when adding Cloud LSU (in days). | 180 |
AgingCheckSizeLowBound | This threshold is used to filter the containers whose size is less than this value for aging check. | 8Mib |
AgingCheckLowThreshold | This threshold is used to filter the containers whose garbage percentage is less than this value (in percentage). | 10% |
After you update the aging check related parameters, you must restart the MSDP service. You can use the crcontrol command line to update those parameters without restarting MSDP service.
To update the aging parameters using crcontrol command line
- Enable cloud aging check for all cloud LSUs.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckon
- Enable cloud aging check for a specified cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckon <dsid>
- Disable cloud aging check for all cloud LSUs.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckoff
- Disable cloud aging check for a specified cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckoff <dsid>
- Show cloud aging check state for all cloud LSUs.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckstate
- Show cloud aging check state for a specified cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingcheckstate <dsid>
- Change cloud aging check to fast mode for all cloud LSUs.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingfastcheck
- Change cloud aging check to fast mode for a specified cloud LSU.
/usr/openv/pdde/pdcr/bin/crcontrol --cloudagingfastcheck <dsid>