Important The hotfix that corresponds to KB 2813630 has been included with the hotfix KB 2878635, which contains all fixes that were previously included in KB 2813630.
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.
You start the virtual machine.
You try to create a backup of the virtual machine on the CSV volume by using Microsoft System Center Data Protection Manager (DPM).
In this scenario, one of the following issues occurs:
The backup is created, and the virtual machine enters a paused state.
The CSV volume goes offline. Therefore, the virtual machine goes offline, and the backup is not created.
Additionally, the following events are logged in the Cluster log and System log respectively:
Software snapshot creation on Cluster Shared Volume(s) ('volume location') with snapshot set id 'snapshot id' failed with error 'HrError(0x80042308)(2147754760)'. Please check the state of the CSV resources and the system events of the resource owner nodes.
Log Name: System Source: Microsoft-Windows-FailoverClustering Date: Date and time Event ID: 5120 Task Category: Cluster Shared Volume Level: Error Keywords: User: SYSTEM Computer: Computer name Description: Cluster Shared Volume 'Volume1' ('name’) is no longer available on this node because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished.
Log Name: System Source: Microsoft-Windows-FailoverClustering Date: Date and time Event ID: 5142 Task Category: Cluster Shared Volume Level: Error Keywords: User: SYSTEM Computer: Computer name Description: Cluster Shared Volume 'Volume3' ('Cluster Disk 4') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
Note 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.
Additionally, the following behavior is also observed:
When an administrator starts a snapshot of a CSV volume, there may be an increase in the memory usage on the node owning the CSV resource. This corresponds to the number of bytes that are read from the snapshot volume by non-owning nodes. Installing this KB eliminates the increased memory usage.
The virtual machine enters a paused state because the Ntfs.sys driver incorrectly reports the available space on the CSV volume when the backup software tries to create a snapshot of the CSV volume. Additionally, the CSV volume goes offline because it does not resume from a paused state after an I/O delay issue or error occurs.
Note The CSV volume is resilient.
This hotfix prevents a CSV failover by fixing an underlying issue in NTFS and by increasing the overall resilience of the Cluster service and CSV during expected pause states.
To avoid CSV failovers, you may have to make additional changes to the computer after you install the hotfix. For example, you may be experiencing the issue described in the "Symptoms" section because of the lack of hardware support for Offloaded Data Transfer (ODX). This causes delays when the operating system queries for hardware support during I/O requests.
In this situation, disable ODX by changing the FilterSupportedFeaturesMode value for the storage device that does not support ODX to 1. For more information about how to disable ODX, go to the following Microsoft website:
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:
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.
To apply this hotfix, you must be running Windows Server 2012.
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
The hotfix that corresponds to KB 2813630 was superseded by hotfix KB 2878635. Hotfix KB 2878635 contains all fixes that were included in KB 2813630. You should use hotfix KB 2878635 to fix the issues that are described in KB 2813630. 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 notes
Important 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:
6.2.920 0.20 xxx
Windows Server 2012
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for and 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
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 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012