Journal Wrap errors d4/d2 sysvol restore

We have two domain controllers (both on site and global catalogs servers).  The main server (2008r2) that holds the FSMO roles has journal wrap errors due to hardware issues that were caused by a lot of dirty shutdowns.  Is it safe to do a d4/d2 restore from the secondary DC (2012r2) set as d4 to the primary DC (2008r2) set as d2.

Thanks
jediweaponAsked:
Who is Participating?
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

Perform an Integrity check against both server and make sure that the AD database is fine. Once you performed Integrity check, download the Active Directory Replication Status Tool http://www.microsoft.com/en-in/download/details.aspx?id=30005 and see which server has got good copy of SYSVOL.

Once you found the good copy of SYSVOL and goahead with d4/d2 restore from the good DC.
0
 
jediweaponAuthor Commented:
Does the integrity check have to be run from the AD Restore console, or can I just stop the services and run it from a command prompt?  Also, do I need to do this on both domain controllers?
0
 
Radhakrishnan RSenior Technical LeadCommented:
Just stop the ADDS service and perform the command from command prompt;

esentutl /G C:\NTDS\ntds.dit

Change the NTDS path according to your setup.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Radhakrishnan RSenior Technical LeadCommented:
Yes, both DC's to make sure both has got good copy.
0
 
jediweaponAuthor Commented:
How would I see which sysvol is the most accurate?  I already know which server has the journal wrap errors and which doesn't?
0
 
Radhakrishnan RSenior Technical LeadCommented:
As a test, create a text file under sysvol folder from one server and see it's replicated to another server? do the same from another server. This is to confirm whether the sysvol replicating each other.

Another thing to check the sysvol is count the number of folders in sysvol and compare with other server and see which one has got more numbers and recent modified dates.
0
 
jediweaponAuthor Commented:
Will the replication tool show which sysvol is the best?  I ran this and it wasnt giving much detail.
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

Replication status tool is to identify if any replications issues between the servers. You can use this command

dcdiag /test:netlogons

Check whether these tests has passed.
0
 
jediweaponAuthor Commented:
From your first response, I am just starting to go through this to fix the journal wrap errors.  The steps are:

1.  To test AD integrity
2.  Run the replication tool per your response to see which DC has a good copy of the sysvol (this is where I am trying to figure out which DC has the good sysvol using http://www.microsoft.com/en-in/download/details.aspx?id=30005, How do I determine this using this tool? )
3.  After I determine which DC has the good sysvol, I will make this the d4 and the other DC the d2.

Thanks
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

The server which is not showing any error will have the good copy of Sysvol. Also, another way to determine is as i mentioned earlier (creating notepad file and replicate). It was very easy to monitor replication in 2003 server as the replmon was very easy to handly but in 2008 server it has been replaced. Still you can try to copy the replmon from 2003 server and place it in 2008 server and see it works. I haven't used this method before. You can try this link http://blog.powershell.no/2009/09/18/replmon-exe-not-included-in-windows-server-20082008-r2/ and refer update @ "Iftikhar on October 12, 2011 at 09:58 said:
Replmon in Windows 2008 R2"

It's upto to you whether to use replmon in 2008 but MS doesn't recommend this.
0
 
jediweaponAuthor Commented:
At this point they do not replicate (I  did test),  due to the journal wrap error, I am using ntfrs and not dfrs.  I will assign the one without errors as d4  (2012r2) and the other which has the fsmo roles and the journal wrap error as d2 (2008r2).  This should work, right?

Thanks
0
 
Radhakrishnan RSenior Technical LeadCommented:
If you are using ntfrs then the procedure is much easier than authoritative method. Yes, you can goahead with this plan. As a precaution, take backup of the Sysvol for both servers and perform the steps.

Good luck
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.