The purpose of this KB is to describe a new behavior in the DFSR service and the new DFSR Event ID 2213. It covers the actions an administrator should take and how to reduce the number of 2213 events logged on a DFSR server. It also covers best practices regarding Auto Recovery from dirty shutdown in light of the latest DFSR patch.
Microsoft introduced a new behavior to the DFS Replication service for Windows Server 2008 R2 via the hotfix published in KB
2663685. After installing KB 2663685 or later versions of DFSRS.EXE on Windows Server 2008 R2, the DFSR Service will no longer perform automatic recovery of the Extensible Storage Engine (ESE)) database when the database suffers dirty shutdown. When the new behavior is triggered, Event ID 2213 is log in the DFSR Event Log. A DFSR administrator must manually resume replication when a dirty shutdown is detected by DFSR.
Windows Server 2012 uses this behavior by default.
1) Please do take all replicated folder backup on volume mentioned in event.
2) Run WMIC command (For WMIC command, open Event ID 2213 property > Recovery Steps and copy WMIC command from step 2 and paste as it into an elevated command prompt) to recover DFSR ESE database from error state.
Once done with recovery steps, DFSR information event ID 2214 gets generated on server which you can add as closing condition in our monitoring system.
The DFSR service maintains one ESE database per volume on volumes that host a replicated folder. DFSR uses this database to store metadata about each file and folder in the replicated folder. The integrity of the database must be maintained to ensure proper service function.
When DFSR is notified that the service must shutdown it will begin to commit all outstanding changes to the ESE database. Dirty Shutdown in DFSR occurs when the DFSR service cannot commit all pending changes to the DSFR ESE Database before the DFSR service is terminated. Upon startup the DFSR service will check the integrity of the database.
Dirty shutdown recovery can possibly cause high backlogs which may cause replication conflicts. In some cases, prior to the fix published in
KB 2780453, the winning file may not be the version that the end user wants. The change to stop replication on dirty shut down was intended as a safe guard which allowed administrators the opportunity to back up the data to capture deltas since the last backup was taken before resuming replication.
As of KB 2780453 it is no longer necessary to pause replication on dirty shutdown. Windows Server 2012 has the fix from
KB 2780453 included in the default media.
How to disable the Stop Replication on Auto Recovery behaviorTo have DFSR perform auto-recovery when a dirty database shut is detected edit the following registry value
after KB
2780453is installed on Windows Server 2008 R2. You can deploy this change to all on all versions of Windows Server 2012. If the value does not exist it will need to be created.
Key: HKLM\System\CurrentControlSet\Services\DFSR\Parameters
Value: StopReplicationOnAutoRecovery
Type: Dword
Data: 0
How to Resume Replication after Event 2213 is loggedTo resume replication after is has been paused will require an administrator to run a WMIC command. The command as it needs to be run will be provide in the text of Event ID 2213
Step 1: Event ID 2213 is logged on your DFSR server.