Journal Wrap Error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Anyone out there?

We have 2 DC's in our single site environment. Were doing final
preparations to migrate to 2003 when I noticed that we were getting a journal
wrap error in the event log on one of the DC's. Furthermore, I have also
noticed that group policy objects have not replicated to the other DC
properly. (I have one on the "good" DC and 6 on the "bad" dc, the one with
the journal wrap error). I can chalk it up to a issue that happend back in
november where we had a minor corruption with SYSVOL Share. (of course no
backups going back that far!!) Which we thought was originally with the good
dc. But now I'm wondering.......

I have read about 20 articles about setting the BurFlags to peform both
non-authoritative and authoritative restores. If I perform a
non-authoritative on the DC with the journal wrap issue my understanding it
will blow away any of the good information on the bad DC. Meaning if I do a
non authoritative will it take all the info off the other DC which has only 1
of 6 GPO's. (as an example).

Question: Should I be performing a D4 authoritative on the bad DC (with the
wrap) and then a D2 non-authoritative on the other. I'm looking to keep all
of the information on the bad dc, yet clear the journal wrap error.

Don't want to confuse this but other than the journal wrap error the "bad"
dc is functioning correctly. (ie GP0's are being picked up correctly, hence
my nervousness).

Any direction would be appreciated.
 
there is an article where you set a registry entry to do with journal wrap.
had a similar issue last week( except my journal wrap was the bad one)
 
mikenanc said:
Do have the link or is it MS KB Article 290762?
Click to expand...

Try Google:

[ site:microsoft.com "journal wrap" registry ]

....shoud find the KB article.

(I don't know it either.)
 
Sorry, yes I already had that one printed off with the 10 or so other related
articles. This article describes a lot with the non-authoritative restores
and increasing the journal size which I have already done as a first step.
If I perform a non-authoritative restore it will wipe out everything and have
to start from scratch. (it will sync with the other DC that only has 1 of 6
GPO's etc) What I want to do is somehow keep the info that is on the bad DC
as it seems more intact than the second DC. My question is if I perform a
authoritative restore or D4 on the bad DC will it keep all the info intact
and wipe out the journal error? (I would then perform a D2 or
non-authoritative on the other DC so it syncronizes everything)
 
AFAIK - Yes

as a extra precaution, you could copy all the gpo objects to another
location, perform the restore then copy them back in.
 
the PDC FSMO is the DC where the GPOs most probably are edited. Every GPO
editing tool by default targets the PDC FSMO.

So at this time, I would say the PDC FSMO is the most reliable DC, but you
need to determine for yourself.

The number of GPOs in the SYSVOL does not say anything, as GPOs both live in
AD and in the SYSVOL.

The "good DC" containing 1 GPO isn't that good, because every domain by
default has 2 GPOs (default domain and default domain controllers)

the resource kit tool GPOTOOL can help you in your quest by comparing DCs
against each and comparing what is in AD and in the SYSVOL

start with that and report back

good luck

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
 
Seemed to straighten it out.

What i did:

On our "bad" DC which is actually the PDC Emulator, I Performed a D4
authoritative. It immediately cleared the journal issue and it syncronized
for some reason with the other DC. (probably because I did not disable FRS on
that box?!?) I copied over the missing GPO's from a file copy backup I did
and then ran GPOTOOL to compare SYSVOL items. I had one conflict with
versions on the default domain policy GPO which I just modified the GPO.ini
to the correct version. Re-ran the GPOTOOL and life's good. I've tested
replication again to confirm no issues. Even went as far as doing the full
battery of DCDIAG tests without any issues.

Just didn't want to get screwed up as I help operate a ski resort, it's our
bread and butter season and we couldn't afford much downtime.

Thanks for everyone's assistance.
 
Use the Group Policy Management Console (GPMC) SP1 and create backups of all
your GPOs.
Fix the journal wrap entries and then use GPMC to restore your GPO's.

--
Kind regards,

Erik Cheizoo
eXcellence & Difference - we keep your business running
============================================
Always test in a non-production environment before implementing
Guidelines for posting: http://support.microsoft.com/?id=555375
============================================
 
Back
Top