Important The hotfix that corresponds to KB 2824600 has been included with the hotfix KB 2878635, which contains all fixes that were previously included in KB 2824600.
Symptoms
Consider the following scenario:
-
You enable the Cluster Shared Volumes (CSV) feature on a Windows Server 2012-based failover cluster.
-
You create a virtual machine on a CSV volume on a cluster node.
-
The CSV volume does not support the Offloaded Data Transfer (ODX) feature.
-
You start the virtual machine.
-
You try to create a backup of the virtual machine on the CSV volume by using the Microsoft System Center Data Protection Manager (DPM).
In this scenario, one of the following issues occurs:
-
The backup is created. However, the virtual machine enters a paused state.
-
The CSV volume goes offline. Therefore, the virtual machine goes offline, and the backup cannot be created.
Additionally, the following events are logged separately in the Cluster log and in the System log: Notes
-
This issue also occurs when you try to create a snapshot of the virtual machine by using backup software that uses the Microsoft Software Shadow Copy Provider.
-
If you experience this issue when the CSV volume supports the ODX feature, click the following article number to view the article in the Microsoft Knowledge Base:
2813630 Virtual machine enters a paused state or a CSV volume goes offline when you try to create a backup of the virtual machine on a Windows Server 2012-based failover cluster
Cause
This issue occurs because NTFS assumes that the ODX feature is supported by default. When the hardware does not support the ODX feature, NTFS still checks the ODX support status in both the read path and the write path. Therefore, more resources are required for CSV, and this increases the possibility of a CSV failover event.
Resolution
This hotfix is also available at Microsoft Update Catalog.
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 this specific problem. 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, submit a request to 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, you must be running Windows Server 2012.
Registry information
To use the hotfix in this package, 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
The hotfix that corresponds to KB 2824600 has been superseded with the hotfix KB 2878635, which contains all fixes that were previously included in KB 2824600. You should use the hotfix KB 2878635 to fix the issues described in KB 2824600. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2878635 Update is available that improves the resiliency of the cloud service provider in Windows Server 2012: December 2013
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 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.20 xxx
Windows Server 2012
RTM
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 2012" 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 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Ntfs.sys |
6.2.9200.20684 |
1,935,624 |
10-Apr-2013 |
01:24 |
x64 |
Workaround
Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.To work around the issue, disable the ODX feature by changing the value of the FilterSupportedFeaturesMode registry entry to 1. For more information about how to do this, go to the following Microsoft TechNet website:
General information about how to deploy the ODX feature
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
Additional file information
