Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

DFS Replication does not work in a Windows Server 2008 R2-based failover cluster if you use a third-party storage management product


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You add the Failover Clustering feature on some computers that are running Windows Server 2008 R2.
  • You configure a failover cluster to use these computers.
  • You configure a highly available file server by using the Failover Cluster Manager Microsoft Management Console (MMC) snap-in.
  • You add this highly available file server to a Distributed File System (DFS) Replication replication group.
  • You configure the replication group to replicate a folder that is stored on a volume that is managed by a third-party storage management product.
In this scenario, the replication of the DFS Replication replicated folder does not initialize. Additionally, the following error is logged to the DFS Replication log:
Event ID = 9110
Severity = Error
General Message =
The DFS Replication service cannot verify the root or staging path of a replicated folder that is hosted by a failover cluster. This can occur if the shared disk hosting the root or staging path of the replicated folder is not online.
Using the Failover cluster Management UI, online the disk hosting the replicated folder 'XYZ' from the member 'ABC' in the replication group 'PQR'. Once the disk is online and available then DFSR will be able to verify the paths and start replicating.
This issue occurs only when a third-party storage management product is installed on the failover cluster. The third-party storage management product creates a third-party cluster resource for the volumes that you use to try to set up the replicated folders.

↑ Back to the top


Cause

This issue occurs because the DFS Replication service recognizes the physical disk resources only when the service initializes the replicated folders on a Windows Server 2008 R2-based failover cluster. This behavior causes the service not to recognize any third-party storage resources. Therefore, the service cannot initialize the replicated folders that are located on the volumes that are managed by a third-party storage management product.

↑ Back to the top


Resolution

To resolve this issue, install this hotfix on the affected computers that are running Windows Server 2008 R2. Additionally, contact the vendor of the third-party storage management product to check whether the product is fully supported for DFS Replication.

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 Web site: 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 Windows Server 2008 R2.

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 and for Windows 7" 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
File nameFile versionFile sizeDateTimePlatform
Dfsrprovs.mofNot Applicable75,20013-Jul-200920:20Not Applicable
Dfsrs.exe6.1.7600.207994,518,40014-Sep-201005:19x64

↑ Back to the top


Status

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

↑ Back to the top


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

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 nameAmd64_05ab4491b3dab81e289f9d1ff03d859b_31bf3856ad364e35_6.1.7600.20799_none_cfe679ec044103b4.manifest
File versionNot Applicable
File size712
Date (UTC)14-Sep-2010
Time (UTC)23:51
PlatformNot Applicable
File nameAmd64_microsoft-windows-dfsr-core-serveronly_31bf3856ad364e35_6.1.7600.20799_none_fa037656da9a6da8.manifest
File versionNot Applicable
File size35,681
Date (UTC)14-Sep-2010
Time (UTC)23:51
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,310
Date (UTC)14-Sep-2010
Time (UTC)23:51
PlatformNot Applicable

↑ Back to the top


Keywords: KB981609, kbexpertiseadvanced, kbclustering, kbautohotfix, kbfix, kbqfe, kbhotfixserver, kbsurveynew

↑ Back to the top

Article Info
Article ID : 981609
Revision : 4
Created on : 10/15/2010
Published on : 10/15/2010
Exists online : False
Views : 284