Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 722
  • Last Modified:

DFSR guru question - crash recovery

EE,

The other day we experienced a network outage that caused our DFSR 2008 R2 infrastructure to crash hard.  After bringing the systems back online, DFS replication did not begin for hours though no matter what we did we could not see any problems in the logs.  We sat and waited for maybe 8 hours and even though replication and health checks passed and we could find no DFSR specific events in the logs and replcation would not continue.  Over night, magically, it began again.  This lead us to the conclusion that what it was doing during the long pause before replication began was comparing every file with its replication partner and learning if there were changes or not that needed to be replicated.  It needed to start from scratch because of the crash; it didn't know where it had left off.

My question is, does this sound like the correct assessment of the cause for the replication delay and do you know of a way to expose logging or event messages that would warn us in the future that this "start from the beginning comparison" process is in progress?
0
JohnDemerjian
Asked:
JohnDemerjian
1 Solution
 
JohnDemerjianAuthor Commented:
I found the answer...


“When the DFS Replication service is asked to resume replication and perform unexpected shutdown recovery, either via auto-recovery or via manual intervention, it performs the following steps:

1) The first thing that DFSR does is to validate if the “USN checkpoint” in the database is valid by comparing the database against referenced USN record in the journal. If the checkpoint itself is invalid, each entry for each file and folder in all replicated folders on the volume is examined for correctness by comparing the entry to the corresponding file or folder on the volume. So this could take some time, depending on how many files are in the replicated folder(s).”

http://blogs.technet.com/b/filecab/archive/2012/07/23/understanding-dfsr-dirty-unexpected-shutdown-recovery.aspx
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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