This object monitors volumes that host replicated folders and creates a Warning alert if any errors are detected on the volume that would cause DFS Replication to stop replication. It does so by looking for the presence of DFS Replication Event 2004.
An unhealthy state of this monitor indicates that replication is stopped because of an error on a volume hosting a replicated folder. The error could be caused by the following issues:
Lack of free disk space.
The replicated folder or staging folder exceeds a disk or folder quota.
The disk is failing.
Examine the additional information section of the alert for information about the error, and then use the following resolutions.
Increase available disk space
If the volume hosting the staging folder or debug log files is low on disk space, increase the available disk space on the volume, increase the size of the volume, or change the path of the staging folder to a volume with more available disk space.
To manually check the amount of available disk space, open a command prompt window and type the following command, where <servername> is the name of the server hosting the affected folder and <domain\user> is your user name:
WMIC /node: "<servername>" /user: <domain\user> volume list status.
After freeing up space, restart the DFS Replication service.
If a quota (NTFS disk quota or File Server Resource Manager quota) is limiting the affected folder or volume, consider increasing the quota size.
To adjust folders created with File Server Resource Manager, see Quota Management (http://go.microsoft.com/fwlink/?LinkId=187098).
To adjust NTFS disk quotas, use the Fsutil quota command, as discussed in FSutil quota (http://go.microsoft.com/fwlink/?LinkId=187104).
Change the staging folder path
Use DFS Management to change the location of the staging folder. To do so, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder (http://go.microsoft.com/fwlink/?LinkId=186944).
Note: 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.
Check for volume errors
If this problem occurs frequently, use the chkdsk command to check the volume hosting the DFS Replication database. Also check the System log in Event Viewer for events with the NTFS source. These events might indicate whether the disk is failing.
This monitor automatically resets to a healthy state when the issue is resolved.