Share via

Dedupe: Verify Garbage Collection is performed regularly on Data Deduplication volumes

  • Article

This article is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this article to computers on which Best Practices Analyzer scans have been run, and that are experiencing the issue addressed by this article. This article can also be useful as general troubleshooting and best practices information to help you configure your server. For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.*

If you think that something in this article is missing or could use improvement, we encourage you to add or edit content that addresses this specific issue. Instructions for editing a TechNet Wiki article are available at Wiki: How to Use the Editor.

Operating System

Windows Server 2012

Product/Feature

Data Deduplication

Severity

Informational

Category

Configuration

 

Issue

Garbage Collection has not been performed for a month, failed, or was cancelled the last time it ran on one or more volumes.

 

Impact

Data deduplication Garbage Collection did not complete successfully for over a month. As a result, data deduplication cannot reclaim space referenced by deleted or modified files.

 

Resolution

Create a Garbage Collection job to run weekly or bi-weekly during server idle times. If the last Garbage Collection job did not complete successfully, review the event logs to determine cause of failure and re-run Garbage Collection manually using Windows PowerShell.

 

Additional references

[[Data Deduplication Overview]]