Data Deduplication Space Not Reclaimed After Large-Scale Backup Deletions

Question

Data Deduplication Space Not Reclaimed After Large-Scale Backup Deletions

Manon David 40

Hi all,

A backup server is reporting critically low disk space on volumes with Data Deduplication enabled. We recently removed several TB of old backup files, but the available capacity has not increased as expected.

The Deduplication chunk store still appears to contain data associated with the deleted files, suggesting that garbage collection has not yet reclaimed the unused chunks.

What is the proper PowerShell procedure for forcing a full Data Deduplication garbage collection using Start-DedupJob -Type GarbageCollection -Full, and how can we verify that the reclaimed space has been successfully returned to the volume?

Thanks

David

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hello David,

When you delete large amounts of data on a deduplicated volume, the chunk store will not immediately shrink because Data Deduplication relies on scheduled background jobs to perform garbage collection. To force a full cleanup, you should run the following PowerShell command with elevated privileges:

powershell

Start-DedupJob -Volume X: -Type GarbageCollection -Full

Replace X: with the actual drive letter of the deduplicated volume. The -Full parameter ensures that all orphaned chunks are scanned and removed, not just those marked for partial cleanup. Depending on the size of the volume and the number of deleted files, this job can take several hours.

To monitor progress, use:

powershell

Get-DedupJob

This will show the current status of the garbage collection job. Once the job completes, you can verify reclaimed space by checking the free space on the volume with:

powershell

Get-Volume -DriveLetter X

or by running:

powershell

Get-DedupStatus -Volume X:

The Get-DedupStatus output will show the current savings rate and the size of the chunk store. If garbage collection has successfully removed unused chunks, you should see a reduction in the chunk store size and an increase in available free space on the volume.

If you find that space is still not reclaimed after a full garbage collection, it may indicate that some chunks are still referenced by other files or that the deduplication metadata has not yet updated. In such cases, running a scrubbing job can help:

powershell

Start-DedupJob -Volume X: -Type Scrubbing -Full

This validates chunk integrity and can also free up space tied to corrupted or stale references.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!HP.

Answer 2

Use this sequence on the affected deduplicated volume:

Run a full garbage collection job:

Start-DedupJob -Volume <DriveLetter> -Type GarbageCollection -Full

This is the documented job type for reclaiming unreferenced deduplication chunks after large deletions.

Run a full scrubbing job if space still does not recover as expected:

Start-DedupJob -Volume <DriveLetter> -Type Scrubbing -Full

Check whether a deduplication job is running or completed:

Get-DedupJob

Expected result: the garbage collection job should no longer show as active after completion.

Check the volume’s deduplication state:

Get-DedupVolume

This is the supported way to confirm deduplication status on the volume.

Estimate reclaimable space for deleted folder sets before or after cleanup, if needed:

Measure-DedupFileMetadata -Path <PathToDeletedDataParent>

Review the DedupDistinctSize value. That value indicates how much disk space can be reclaimed if the folders are deleted and a garbage collection job is run.

If space is still not reclaimed after the full garbage collection job:

Check for file system corruption and repair it:

chkdsk <DriveLetter>: /f /scan

If maintenance jobs continue to fail or deletions still do not reclaim space, back up the data, create a new volume, restore the backup, and enable deduplication again.

Important:

Full garbage collection can be resource-intensive and is normally scheduled periodically. Running it manually is appropriate when large deletions have occurred and space has not returned.
If the volume remains critically low on free space, expanding the volume may be necessary.
If the goal is to stop monthly Full GC runs because of performance impact, the documented workaround is to configure regular garbage collection only. That registry change affects future scheduling and is separate from manually forcing a one-time Full GC. Registry changes carry configuration risk and should be planned carefully.