Changes that are not replicated to a downstream server are lost on the upstream server after an automatic recovery process occurs in a DFS Replication environment in Windows Server 2008 R2

This hotfix is also available at Microsoft Update Catalog.

To resolve this issue, install the following hotfix on both servers.

After you install the hotfix, the DFS Replication service no longer automatically recovers databases.

This behavior enables you to back up the replicated files before you start the recovery process. After the backup process is complete, use the Windows Management Instrumentation Command-line (WMIC) tool to resume DFS Replication. To do this, follow these steps:

1. Click Start, and then click Run.
2. In the Run dialog box, type WMIC, and then click OK.
3. At the WMIC command prompt, type /namespace:\\root\microsoftdfs path DfsrVolumeConfig Where volumeGuid="<GUID of the volume on the upstream server>" call ResumeReplication and then press Enter.

Note To enable the DFS Replication service to automatically recover databases, modify the following registry key:

Notes

• If the value of the StopReplicationOnAutoRecovery registry subkey is set to 1, the DFS Replication automatic recovery is disabled.
  When the error condition should occur you may note a DFS Replication warning event 2213 like the following:
  
  Log Name: DFS Replication
  Source: DFSR
  Event ID: 2213
  Task Category: None
  Level: Warning
  Keywords: Classic
  User: N/A
  Computer: MyDFSRMember.contoso.com
  Description:
  The DFS Replication service stopped replication on volume F:. 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.
  
  Additional Information:
  Volume: F:
  GUID: 4A5BAE4E-c19D-21E1-A4E7-007056B54182
  
  
• If the value of the StopReplicationOnAutoRecovery registry subkey is set to 0 or if the StopReplicationOnAutoRecovery registry subkey does not exist, the DFS Replication automatic recovery is enabled.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

• Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	SR_Level	Service branch
  6.1.760 0. 16xxx	Windows Server 2008 R2	RTM	GDR
  6.1.760 0. 21xxx	Windows Server 2008 R2	RTM	LDR
  6.1.760 1. 17xxx	Windows Server 2008 R2	SP1	GDR
  6.1.760 1. 21xxx	Windows Server 2008 R2	SP1	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2