This object monitors the NTFS change journal on volumes hosting replicated folders, and creates a Warning alert if the change journal is not accessible. It does so by looking for the presence of DFS Replication Event 2204.
An unhealthy state indicates that DFS Replication detected lost entries in the NTFS change journal and is attempting to recover them. This can occur for the following reasons:
An administrator deleted the change journal.
The volume is low on disk space.
Wait for NTFS change journal recovery to complete
No action is required.
DFS Replication automatically initiates a journal recovery process.
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.
This monitor automatically resets itself to a healthy state after the recovery process is complete.