2009-09-09 23:51:06 UTC
I have a new client (yay!) and upon checking their server I've found
that is in a journal wrap condition, and I'm wondering what I should do
to fix this.
SBS 2003, Premium, R2, fully patched. (ISA and SQL Server are both
In the SBS Best Practices Analyzer, it points to:
... which states on the page...
To recover, the affected replica member will need to be reinitialized
with a non-authoritative restore (BURFLAGS=D2) where it will synchronize
files from an existing inbound partner. This re-initialization can be
time consuming for large replica sets.
However; in the Event Logs, under File Replication Service, the error
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of
one of the following reasons.
 Volume "\\.\C:" has been formatted.
 The NTFS USN journal on volume "\\.\C:" has been deleted.
 The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk
can truncate the journal if it finds corrupt entries at the end of the
 File Replication Service was not running on this computer for a
 File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter
to 1 will cause the following recovery steps to be taken to
automatically recover from this error state.
 At the first poll, which will occur in 5 minutes, this computer
will be deleted from the replica set. If you do not want to wait 5
minutes, then run "net stop ntfrs" followed by "net start ntfrs" to
restart the File Replication Service.
 At the poll following the deletion this computer will be re-added
to the replica set. The re-addition will trigger a full tree sync for
the replica set.
WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to
0 to prevent automatic recovery from making the data unexpectedly
unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Click down the key path:
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD
Value function under the Edit Menu item. Type the value name exactly as
So I'm not sure what path to follow (1. or 2.), and would appreciate any
According to the Event Logs the journal wrap error has existed since Feb