<div>
<div class="content wysiwyg-content">
EE,<br />
<br />
The other day we experienced a network outage that caused our DFSR 2008 R2 infrastructure to crash hard. &nbsp;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. &nbsp;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. &nbsp;Over night, magically, it began again. &nbsp;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. &nbsp;It needed to start from scratch because of the crash; it didn't know where it had left off.<br />
<br />
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 &quot;start from the beginning comparison&quot; process is in progress?
</div>
</div>


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?

DFSR guru question - crash recovery

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).