This object monitors the ability of DFS Replication to recover from a wrap (overwrite of old journal entries) of the NTFS change journal. It does so by looking for the presence of DFS Replication Event 2208.
An unhealthy state of this monitor indicates that DFS Replication failed to recover from a journal wrap or loss. This can occur due to DFS Replication service internal error conditions or if the volume on which the journal recovery failed does not have at least 512 MB of free 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.
If the change journal has an internal error and 512 MB of space cannot be recovered by moving or deleting files, run chkdsk on the volume to recover the space used by the corrupt journal.