DFS-R: Volumes hosting replicated folders should have sufficient free disk space

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


File Services






DFS Replication may soon run out of disk space because one (or more) of the volumes hosting DFS replicated folders have a small amount of available disk space.


After DFS Replication runs out of disk space, it won't be able to replicate properly, causing files to become stale or missing. If disk space is not available, users will not be able to create or modify files in replicated folders on the affected volumes.


Free up some space on the affected volumes or consider relocating the replicated folder to another volume. Optionally, consider relocating the staging areas located on this volume to another volume to free up disk space.

To resolve this issue, increase the available disk space on the affected volume, increase the size of the volume, or change the path of the staging folder (and possibly the replicated folder) to a volume with more available disk space. After freeing up space, restart the DFS Replication service.

To change the location of the staging folder, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder (http://go.microsoft.com/fwlink/?LinkId=186944).


To manage a replicated folder, you must be a member of the Domain Admins group in the domain in which the replication group is configured, the creator of the replication group, or have been delegated permissions.