An outgoing replication backlog occurs after you convert a read/write replicated folder to a read-only replicated folder in Windows Server 2008 R2

Symptoms

Consider the following scenario:

  • You have a Distributed File System (DFS) Replication group that consists of computers that host replicated folders.

  • On a computer that is running Windows Server 2008 R2, you take one of the following actions:

    • You convert a read/write replicated folder to a read-only replicated folder.

    • Or, you create a new read-only replicated folder by using preseeded data that is copied from one of the read/write replicated folders.

In this scenario, you notice a persistent outgoing replication backlog on the computer that hosts the read-only replicated folder. This outgoing replication backlog does not decrease in size over time.

Cause

This issue occurs because the DFS Replication service calculates version information incorrectly. This incorrect behavior causes the outgoing replication backlog to occur. The backlog persists because the read-only replicated folder does not replicate changes to other replicated folders.

Note The hotfix does not repair the condition since it is caused during initial replication on the read-only partner. It only prevents the problem when the hotfix is already installed on the read-only partner and initial replication is performed.

Resolution

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:

http://support.microsoft.com/contactus/?ws=supportNote 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, your computer must be running Windows Server 2008 R2.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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

  • 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 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining 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

File name

File version

File size

Date

Time

Hashes

Platform

Dfsrprovs.mof

Not applicable

75,200

13-Jul-2009

20:20

Not applicable

Not applicable

Dfsrress.dll

6.1.7600.16385

2,048

14-Jul-2009

01:26

MD5: 1461DEFD250550CD82CFE284E6522AC0
SHA1: 19B3875C05D655885A5068F5161A30B8DCF8209D

x64

Dfsrs.exe

6.1.7600.20756

4,510,208

16-Jul-2010

10:44

MD5: 171E11370FEA1D4125C78358A6E0D4BF
SHA1: AD9B41A429B4E2BCD05C33DBDA7967BBBC773600

x64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


For more information, visit the following Microsoft webiste:

Make a replicated folder read-only on a particular member

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_b980ee021ad4dd28fd4728e54c46274e_31bf3856ad364e35_6.1.7600.20756_none_053946cffae55c50.manifest

File version

Not applicable

File size

712

Date (UTC)

16-Jul-2010

Time (UTC)

19:28

SHA-1 hash

Not applicable

MD5 hash

Not applicable

File name

Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.1.7600.20756_none_fa2bb528da7cb1df.manifest

File version

Not applicable

File size

35,681

Date (UTC)

16-Jul-2010

Time (UTC)

19:28

SHA-1 hash

Not applicable

MD5 hash

Not applicable

File name

Package_1_for_kb2285835~31bf3856ad364e35~amd64~~6.1.1.0.mum

File version

Not applicable

File size

2,689

Date (UTC)

16-Jul-2010

Time (UTC)

19:28

SHA-1 hash

Not applicable

MD5 hash

Not applicable

File name

Package_for_kb2285835_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum

File version

Not applicable

File size

2,315

Date (UTC)

16-Jul-2010

Time (UTC)

19:28

SHA-1 hash

Not applicable

MD5 hash

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×