Burflags and Journal wrap

On November 28, 2009, in Migrationextras, by

One of the key “this will nail you EVERY migration you attempt” is the Journal Wrap.  And I’ve seen a lot of folks in the SBS world with a journal wrap error.

Fortunately it’s an easy fix.  You literally read the KB article that it points to and voila, it fixes the journal wrap error.

This was an old one I had years ago on my old SBS 2k3 server.  I got in this condition because I didn’t have a good UPS on the home server and Dad and PG&E shut down the circuit breaker on the house during Thanksgiving weekend in 2007.  I didn’t fix the error until Christmas because on a single domain box, you won’t notice it having issues.

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date:  12/25/2007
Time:  2:43:19 PM
User:  N/A
Computer: KIKIBITZFINAL
Description:
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.
 
 [1] Volume “\\.\C:” has been formatted.
 [2] The NTFS USN journal on volume “\\.\C:” has been deleted.
 [3] 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 journal.
 [4] File Replication Service was not running on this computer for a long time.
 [5] 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.
 [1] 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.
 [2] 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.
 
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   “System\CurrentControlSet\Services\NtFrs\Parameters”
Double click on the value name
   “Enable Journal Wrap Automatic Restore”
and update the value.   [to 1]
 
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 shown above.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Keep in mind that even if you have fixed it, it may still show up in the BPA report as it sees that old journal wrap event left over in your File replication log files.  The key thing is to review the File replication log and ensure that post registry you get indicators that the system has been fixed up.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13560
Date:  12/26/2007
Time:  12:34:03 AM
User:  N/A
Computer: KIKIBITZFINAL
Description:
The File Replication Service is deleting this computer from the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” as an attempt to recover from the error state,
 Error status = FrsErrorSuccess
 At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13520
Date:  12/26/2007
Time:  12:39:39 AM
User:  N/A
Computer: KIKIBITZFINAL
Description:
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
 
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.
 
In some cases, the File Replication Service may copy a file from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other replicating partner.
 
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13553
Date:  12/26/2007
Time:  12:39:40 AM
User:  N/A
Computer: KIKIBITZFINAL
Description:
The File Replication Service successfully added this computer to the following replica set:
    “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
 
Information related to this event is shown below:
Computer DNS name is “kikibitzfinal.Kikibitzrtm.local”
Replica set member name is “KIKIBITZFINAL”
Replica set root path is “c:\windows\sysvol\domain”
Replica staging directory path is “c:\windows\sysvol\staging\domain”
Replica working directory path is “c:\windows\ntfrs\jet”

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Using the BurFlags registry key to reinitialize File Replication Service replica sets:
http://support.microsoft.com/kb/290762

Complications from an SBS 2008 Migration :: Third Tier:
http://www.thirdtier.net/2009/11/complications-from-an-sbs-2008-migration/

And don’t blow off what it says….

 

Comments are closed.