Journal Wrap Errors & Replication

[Guest]

Hi guys, hope someone can help me here, I'm going nutty trying to solve this!

For some time our 3 DCs were having issues replicating (sometimes Group
Policy would kick in, sometimes it wouldn't etc). One of our big mistakes
was to use dfs to replicate our user profiles across all servers for
redundancy reasons. I think the sheer amount of data being replicated has
caused us to go into journal wrap (something in the region of 50k-70k files).
Hindsight is a wonderful thing, but at the time we didn't know what the cause
was; in fact it looked like a corrupt Active Directory database on DCs 2 & 3,
so we demoted both DCs and now have a single directory on DC1. We built up a
new DC and promoted it, but AD refused to replicate from DC1 (obviously
because of the journal wrap problem).

So now I have 1 DC, in journal wrap, preventing me from promoting a new DC.
The only fixes I can see to come out of journal wrap is to perform a
non-authoritative restore - but I've demoted our other DCs so what can it
restore from? And I can't promote another DC because my only controller is in
journal wrap! Its chicken and egg. How can I remove the journal wrap error
without another DC to restore from?

I'm a little bit concerned that we might have fubar'd it.

 

[Guest]

Oh yeah, should have mentioned, this is on W2k with latest SP. Machine is a
dual 450 P3 with 384Mb. Replication of user profiles is now no longer
performed, so the underlying problem with the journal wrap error problem
*should* be resolved.