DFS-R: The DFS Replication service needs sufficient disk space to store replication conflicts for the replicated folder
Updated: April 27, 2010
Applies To: Windows Server 2008 R2, Windows Server 2012
This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the File Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.
Operating System |
Windows Server 2008 R2 |
Product/Feature |
File Services |
Severity |
Warning |
Category |
Operation |
Issue
The size of the Conflict and Deleted folder is near the quota limit for the replicated folder '{0}' that belongs to replication group '{1}'.
Impact
If the Conflict and Deleted folder runs out of space, DFS Replication will remove older conflicting or deleted files to free up disk space, which might temporarily decrease replication performance.
If a staging folder quota is configured to be too small, DFS Replication might consume additional CPU and disk resources to regenerate the staged files. Replication might also slow down because the lack of staging space can effectively limit the number of concurrent transfers with partners. Increasing the size of the staging folder and the Conflict and Deleted folder can increase replication performance and the number of recoverable conflicting and deleted files.
Resolution
Delete files from the Conflict and Deleted folder, or increase the quota of the Conflict and Deleted folder for the appropriate replicated folder(s).
To increase the quota size, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder (https://go.microsoft.com/fwlink/?LinkId=186944).