Solved

DFSR guru question - crash recovery

Posted on 2013-01-22
1
714 Views
Last Modified: 2013-01-22
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
Comment
Question by:JohnDemerjian
1 Comment
 
LVL 5

Accepted Solution

by:
JohnDemerjian earned 0 total points
ID: 38806029
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

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Windows IPv6 DHCP server 8 61
Server configuration for MS Access - SQL Server app 8 72
RDS2012 vs RDS2008 4 38
Dropbox in Windows Server 2008 4 32
INTRODUCTION The purpose of this document is to demonstrate the Installation and configuration of the Data Protection Manager product. Note that this demonstration was prepared on the basis of Windows OS is 2008 R2 and DPM 2010. DATA PROTECTI…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question