• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 689
  • Last Modified:

Question about the Event ID 13568 The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Hi all,

I will briefly explain out environment, multiple domain controllers across the globe, with one Operations Master based in UK.

A server based in the US has the following error:

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 
etc...



Can anyone please confirm if the method above is recommended, as I keep reading this is not recommended for anything above Windows 2000 (server having the replication issue is Windows 2003)

The recommended is the below, Nonauthoritative restore, kb below

http://support.microsoft.com/kb/290762
 
Can anyone confirm how the above is meant to be used, do you apply the D2 burflag on the server having the issue? Do I need to make any changes to a healthy server for it to pull the data from?

Any advise will be greatly appreciated.
0
Mikoyan_2010
Asked:
Mikoyan_2010
  • 5
  • 5
  • 4
2 Solutions
 
Sushil SonawaneCommented:
You have to apply "D2" on the server having issue and D4 on the domain controller which don't have the issue.

Before perfrom the action stop the file replication service then make registry changes and start the file replicaton service on the both server. Both server gives you event id 13516 in event viewer---> file replication service.

The event id 13516 indicate the both DC health is good and issue resolve on the server.
0
 
Sarang TinguriaSr EngineerCommented:
Simple steps

1)Login to healthy server
2)Check FRS logs if its health and connectivity with Problem server using \\Problem_server
3)Stop NTFRS service on Healthy
4)Navgate to HKLM\...\Backup/Restore at startup\burflag
5) Set this to D4 -> Restart NTFRS-> Wait for 13516 to come
6) Login to Problem server
7) Follow step 4 and set the Burflag to D2 ->-> Restart NTFRS-> Wait for 13516 to come
0
 
Mikoyan_2010Author Commented:
Thanks for the comments guys, doing the D4 on the healthy server will not rebuild anything on the healthy server right?

Im guessing this will only effect a server I set the D2 flag on (and not effect any other we have around the globe)

Your examples above also show this for an authoritative restore, it is only one dc that is having the issue shouldn't I use the non-authoritative restore?
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
Sarang TinguriaSr EngineerCommented:
You are correct

The D2 DCs will then sync the SYSVOL Replica Set contents when you restart the FRS service on these computers. They will contact the D4 DC to compare and sync the changed files. This process is called D4-D2 restore.

Source: http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2008/AdminTips/Admin/FRSD2D4-WhenShouldYouUseThem.html
0
 
Mikoyan_2010Author Commented:
ok looks like this applies to my problem server as it has a journal wrap error.

Can you confirm that once I set the D4 flag on the healthy dc, and the D2 on errorserver, it then syncs, but do I need to delete the D2/D4 registry entries I made previously after this point?
0
 
Sarang TinguriaSr EngineerCommented:
Those will automatically get reverts to zero after you restart NTFRS service
0
 
Sushil SonawaneCommented:
you don't require to delete the d2/d4 registry entries. After restart the service it will automaticaly revert.
0
 
Mikoyan_2010Author Commented:
Thanks for the info, one final question.

What are the risks of doing an restore like above? This is for a server based in the US and wondering if anything can critically go wrong?

I mean the above error is currently active so it needs to be fixed, just a heads up if possible?
0
 
Sarang TinguriaSr EngineerCommented:
You can proceed US, UK , Japs ..Doesn't matter ..Technology is same of Microsoft
0
 
Sushil SonawaneCommented:
Perfrom only D2 on the server based in the US in registry and restart the file replication service.
0
 
Mikoyan_2010Author Commented:
Thanks so it's best to start with a non auth restore first?  On the problem server
0
 
Sushil SonawaneCommented:
Yes. Non-authorative automaticaly find authorative domain.
0
 
Mikoyan_2010Author Commented:
When using the d2 option then how would I know which server it deems as the upstream partner? Or does it select any random server?
0
 
Sushil SonawaneCommented:
Yes it will be select automaticaly authorative or upstream domain controller.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now