- 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).
- 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.
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.
Note The CSV volume is resilient.
Hotfix informationThis 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.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThe 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:
Article ID: 2813630 - Last Review: Jan 10, 2014 - Revision: 1