Optimizing the Deduplicated Database (DDB) Pruning (Garbage Collection)
You can use the Garbage Collection feature to optimize the Deduplication Database (DDB) pruning by reducing the disk IO. With the Garbage Collection feature, the DDB disk is parsed once in 24 hours outside of the Backup Operation Window to mark the CommServe job records for pruning and the data aging process prunes these marked CommServe job records.
- Upgrade your entire setup including: data mover MediaAgent, Deduplication database MediaAgents and Commserve to service pack 14.
For complete procedures on upgrading to the latest service packs, see: Upgrades.
- Run the DDB compaction with the
compactfile secondaryoption on the upgraded DDB MediaAgents. The compaction process takes some time. For example, if the DDB is using a SSD or NVMe, then upgrading a 500GB DDB MediaAgent might take 4 HRS approximately.
For more information on running compaction, see Compacting the Deduplication Database.
Note: The DDB pruning optimizing feature is not supported for Transactional DDB.
- From the Commcell Console , on the ribbon, click the Storage tab, and then click Media Management.
The Media Management Configuration dialog box appears.
- On the Deduplication tab enable the Enable garbage collection and pruning log journaling options configuration parameter.
- From the CommCell Browser, expand Storage Resources > Deduplication Engines > storage_policy_copy.
- Right-click the deduplication database and click Properties.
The Deduplication Database Properties dialog box appears.
- On the Settings tab click the Enable garbage collection check box.
- Click OK.
Last modified: 3/8/2019 4:53:23 PM