Consider the following scenario:
- You use Distributed File System Replication (DFSR) to publish content to branch offices.
- All the changes to the replicated content occur on one server or on a subset of the servers that are members of the replicated folders. None of the other servers have any updates created on them.
In this scenario, you notice intermittent and unexplained spikes in the backlog. The number of spikes is approximately equal to the number of objects in the replicated folder.
The issue occurs because of the way the DFS Replication server determines stale membership of its replication partners. If a DFS Replication server does not receive an update from one of its replication partners in more than 60 days, the server determines that the partner is stale. The DFS Replication server then updates all records that are related to the stale partner. This operation generates a backlog on the DFS Replication server when it is processing tombstones that must be sent to all replication partners. Additionally, the stale partner must send out a notification that it is still active. If this scenario happens on multiple DFS Replication servers at the same time, you find very large increases in replication backlogs.
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, your computer must be running Windows Server 2008 R2. Additionally, you must install the Distributed File System (DFS) Replication role service on the computer.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
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 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 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
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Dfsrprovs.mof | Not Applicable | 75,200 | 13-Jul-2009 | 20:20 | Not Applicable |
| Dfsrs.exe | 6.1.7600.20787 | 4,516,864 | 24-Aug-2010 | 00:54 | x64 |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
| File name | Amd64_62a2334370337793e0d603da5418d13d_31bf3856ad364e35_6.1.7600.20787_none_f4b3968a8242241d.manifest |
| File version | Not Applicable |
| File size | 712 |
| Date (UTC) | 25-Aug-2010 |
| Time (UTC) | 17:42 |
| Platform | Not Applicable |
|
| File name | Amd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.1.7600.20787_none_fa0c45aeda941f09.manifest |
| File version | Not Applicable |
| File size | 35,681 |
| Date (UTC) | 25-Aug-2010 |
| Time (UTC) | 17:42 |
| Platform | Not Applicable |
|
| File name | Update.mum |
| File version | Not Applicable |
| File size | 2,316 |
| Date (UTC) | 25-Aug-2010 |
| Time (UTC) | 17:42 |
| Platform | Not Applicable |
|