This object monitors the volume database and creates a Warning alert if the database needs to be recreated. It does so by looking for the presence of DFS Replication Event 2102.
An unhealthy state of this monitor indicates that replication is stopped because of an error on the DFS Replication database on a specific volume. This can occur due to a disk error or the manual deletion of the DFS Replication database.
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.
This monitor automatically resets to a healthy state after the replication database is recreated and DFS Replication detects Event 2106 or 4108.
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