If you only have a single DC then you should utilize D4 for an authoritative restore as it’s own contents are the valid contents and there is no where else to pull from.  You may need to restart FRS or possibly run a D2 on the new DC to get FRS replicating on that server as well.  Check out downloading Sonar.exe for viewing FRS stats so that you can see if your backlogged files start replicating between the DC’s once you do this.  FRSdiag is also useful if you need to troubleshoot as well.

 

Sonar

http://www.microsoft.com/downloads/details.aspx?FamilyID=158cb0fb-fe09-477c-8148-25ae02cf15d8&DisplayLang=en

 

FRSdiag

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=43CB658E-8553-4DE7-811A-562563EB5EBF

 

 

Kurt Falde


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Burg
Sent: Thursday, September 07, 2006 1:03 AM
To: [email protected]
Subject: [ActiveDir] NTFRS - Journal Wrap Errors

 

Hi-

 

I am new to the list and was hoping someone could help with an ugly situation I was brought in to clean up:

 

I am working with a W2K native mode domain with only ONE active domain controller (W2K SP4). There is a second DC, but it was brought on-line after the journal wrap errors (Event 13568 ) began and has never replicated sysvol (doesn't even exist on the box). It appears AD and such are working with the new DC... just not NTFRS.

 

The original DC does have sysvol and appears to be working to authenticate clients as normal. I need to get the journal wrap errors resolved so I can bring the second DC on-line, transfer FSMO roles and get the old box rebuilt since it doesn't even have redundant drives - Yikes!

 

Everything I have read says to do a D2 non-authoritative restore, but since I only have the one DC, where would it restore from? I have run an NT backup of c:\ and system state to try and get some comfort, but still am afraid of making matters worse.

 

Any suggestions/recommendations would be very much appreciated...I would like to get this cleaned up this week!

 

Thanks so much,

Aaron

Reply via email to