In my mind, that is not necessarily an error, more of a condition. As in "my sysvol is in journal wrap state"
Google journal wrap. Basic description- The USN journal is a log of fixed size that records all changes that take place on NTFS 5.0-formatted partitions. NTFRS monitors the NTFS USN journal file for closed files in FRS replicated directories as long as FRS is running. Journal wrap errors occur if a sufficient number of changes take place while FRS is turned off such that the last USN change that FRS recorded during shutdown no longer exists in the USN journal during startup. The risk is that changes to files and folders for FRS replicated trees may have taken place while the service was turned off, and no record of the change exists in the USN journal. To guard against data inconsistency, FRS asserts into a journal wrap state. -----Original Message----- From: John Aldrich [mailto:[email protected]] Sent: Thursday, April 07, 2011 7:26 AM To: NT System Admin Issues Subject: RE: Need help with DFS Well, it's saying that there's an error in the "jrnl_wrap" for NTFRS. I've got a call in to a consultant to help with this, but he's not going to be available until about 2:30. :-( That being said, one of the servers was down for awhile Tuesday night, which might also have contributed to the problem (power outage...the server was shut down automatically by the PowerChute software.) Realistically, I think it was likely the "unsafe" shutdown that occurred when I tried to force the second server to come back up before the UPS was ready. From: Jonathan Link [mailto:[email protected]] Sent: Thursday, April 07, 2011 10:14 AM To: NT System Admin Issues Subject: Re: Need help with DFS And nothing is in the eventlogs of either server detailing the reasons for replication failing? On Thu, Apr 7, 2011 at 10:05 AM, John Aldrich <[email protected]> wrote: Ok, I apparently accidentally broke DFS replication yesterday testing my UPS -- it shut down one of the two servers unexpectedly and now DFS won't replicate. I have followed the instructions here: http://technet.microsoft.com/en-us/library/cc753479(WS.10).aspx and tried to restart the replication, but it isn't replicating. Any ideas? Windows 2003 R2, fully updated. HELP!!! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
