DFSR event 2213 indicates that a database was not shut down cleanly on a Windows server

DFSR error 2213 appears in the DFS Replication event log of an affected server:

The DFS Replication service stopped replication on volume X:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.

Recovery Steps
1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:

wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" call ResumeReplication

The drive letter and GUID in the error message are system-dependent.

The affected server can no longer participate in DFS replication with its partners. If it is a domain controller, it no longer replicates SYSVOL data but may still replicate Active Directory data.

The most common cause of this issue is an unexpected shutdown of the operating system. This can happen for many reasons, such as loss of power, an operating system crash, or hardware failure. The issue can also occur if the DFSR service stops unexpectedly.

DFSR uses an Extensible Storage Engine (ESE) database to store metadata for the data being replicated. If the DFSR service stops when changes to the metadata have not yet been committed to this database, the database enters a "dirty shutdown" state. This indicates that the metadata in the database may not accurately reflect the state of the replicated data. The next time the DFSR service starts, this dirty shutdown is detected, and event 2213 is logged.

As shown above, the description of event 2213 includes a command that can be run to initiate the recovery process:

wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" call ResumeReplication

This command can be copied as-is from the event description and pasted into an elevated command prompt. (The event description contains the correct volume GUID rather than the Xs shown above.)

If recovery of the database is successful, the command's output includes the following:

{
	ReturnValue=0;
};

Any other return value indicates an error of some sort, but this is rare. To confirm that recovery has been successful, check the affected server's DFSR event log for event 2214:

The DFS Replication service successfully recovered from an unexpected shutdown on volume X:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. No user action is required.