Deduplication Pruning Leaves Orphaned Data on the Disk
Article ID: DD0071 Deduplication Pruning Leaves Orphaned Data on the Disk
There is a known issue in V10 and V11, in which deduplication pruning leaves orphaned data on the disk.
Some signs that this problem has occurred are as follows:
- The deduplication ratio of a deduplication database (DDB) is low. For example, the ratio might be 2:1 instead of the expected 5:1.
- The amount of data in your disk library is much greater than what is reported in the Disk Library Properties dialog box.
If this is the case, you can use the steps described in the documentation for Validating and Pruning Aged Data on the DDB to resynchronize the DDB; with the CommServe database and remove any extraneous data on disk without having to put the DDB in maintenance mode first. This operation can be performed on demand and the resynchronization process will not interrupt other operations on the DDB, such as pruning, backups or Auxiliary Copy jobs.
If you continue to see that the disk library is much larger than what is reported in the Disk Library Properties dialog box, and if the disk hosting your disk library does not support drilling holes, you can run a Data Verification job with the Reclaim idle space on Mount Paths with no drill hole capability option enabled to reclaim the space.
Depending on your environment, you may have to run both these operations to reclaim space.