Link to home
Start Free TrialLog in
Avatar of tech53
tech53Flag for United Kingdom of Great Britain and Northern Ireland

asked on

journal wrap error 13568

Hi Folks,

To cut out the long story, I have an SBS 2003 server.  There was once another DC added to the network but it died.  So it went into tombstone state.

I'm now migrating to SBS 2011 and have the journal wrap error.  So I have used the ntdsutil to clean up the metadata successfully as per the excellent article at http://www.petri.co.il/delete_failed_dcs_from_ad.htm

The journal wrap condition still exists.  My choices now are:

set the BurFlags to D2
set the BurFlags to D4
or enable journal wrap automatic restore

From my reading up on these options, all three pose a threat of possible data loss which I obviously want to avoid.  I have backed up the system state at several stages already.

Which option is the right one to do?
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

I always use the D4 for SBS as it is the Master server on a network.

Alan
Avatar of tech53

ASKER

Thanks.  I know I'm in a bad place with this, but the D4 option is pretty drastic.  I did this before in an identical situation and active directory disappeared on a reboot.

When the D4 option is set, what exactly happens? I now it rebuilds AD from scratch, but where does it rebuild it from? And is that source reliable?

thanks again
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Just make sure you have a system state and server backup - then you can recover AD if it does go south, not that I have ever needed it.
Avatar of tech53

ASKER

Ok.  how long does it take?  Its a small SBS network with 15 users. No customised GPOs.

Also when rebuilds, is it like replaying the logs or something?
It's usually very quick - worst case about 15 minutes.

No logs to replay - just does the following (from the link I posted):

When the FRS service is restarted, the following actions occur:
The value for the BurFlags registry key is set back to 0.
An event 13566 is logged to signal that an authoritative restore is started.
Files in the reinitialized FRS replicated directories remain unchanged and become authoritative on direct replication. Additionally, the files become indirect replication partners through transitive replication.
The FRS database is rebuilt based on current file inventory.
When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.
Avatar of tech53

ASKER

Ok. cool.  I did read this but wanted the expert translation and support.

I'll apply it now and post back.

cheers
Avatar of tech53

ASKER

Perfect!  Thanks for the help.  Although I had researched this a bit before posting, Its always good to get the re-assurance from an expert.

AD rebuilt in les than 1 minute.
NTFRS logs are clear.
Items recently added to AD are present.

I'll do a server reboot later to be sure, but it all looks good.

Thanks a million Alan.
You are welcome - always pays to check before you hose your system!!