EXTRA... EXTRA... READ ALL ABOUT IT

FROM: http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/47582917-9086-46a3-8fd1-5440e0a9c10f  

Cody Lewis

0 Points

 

0

Sign In to Vote

After many hours of reading logs and testing I have discovered the solution!

When the DFSR service is launched, it will detect the registry “HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CurrentVersion\ASR\RestoreSession\RestoredVolumes”, if this entry exists, DFSR knows a restore was once performed on the volume where the DFSR content resides, so DFSR will do an initial sync to confirm the local database is in a consistent state.

Problem is, this key is not getting removed, so when DFSR is disabled for backup, then enabled again, it believes it has just been recovered from backup and should sync again.

Remove the “RestoreSession” subkey under “HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CurrentVersion\ASR”.

Problem solved!

I hope this helps,

Cody

• Proposed

I have been experiencing a recurring error with DFS-R not syncing properly. After checking the logs, I discovered that DFS stops working every time Windows Server Backup begins to run. After changing my backups to every four hours only, replication began - in earnest! I triggered a replication storm! I also discovered this registry setting, and I hope that the solution is accurate. I hope to see some changes in my event viewer!