This object monitors recovery operations on the DFS Replication database, and creates a Warning alert if any errors occur. It does so by looking for the presence of DFS Replication Event 2104.
An unhealthy state of this monitor indicates that replication is stopped due to an internal error with the replication database. This can occur for the following reasons:
The disk on which the replicated folder is stored is full.
The database has become corrupt, possibly due to hardware problems.
Physical problems with the disk interfered with database access.
Wait for database recreation to complete
No action is required.
DFS Replication automatically rebuilds the database and then begins initial synchronization for all replicated folders hosted on that volume. Therefore, it may take a long time for recovery to complete, depending on the amount of data and number of files in replicated folders on the specified volume.
If you see this error occurring frequently, run the chkdsk command on the affected volume to check whether disk errors may be causing this issue, and examine the System event log for disk-related errors.
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.
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.
If you continue to experience problems, contact Microsoft Customer Service and Support (http://support.microsoft.com).
After replication completes and DFS Replication logs Event 2106 or Event 4108, this monitor automatically resets to a healthy state.
To manually confirm that replication is healthy, run a propagation test on the affected folder by using DFS Management or the following commands, where <ReplicationGroup>is the name of the replication group and <ReplicatedFolder>is the name of the replicated folder:
dfsrdiag propagationtest /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml
dfsrdiag propagationreport /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml /reportfilename:c:\DFS-R_Report.xml