Another update of another update improves cluster resiliency in Windows Server 2012

Microsoft made available another update of a fix which improves cluster resiliency. I lost count now but believe this is the fourth try of Microsoft to fix a number of issues which are storage related.

One of the readers of my blog applied this latest hotfix KB2848344 and wrote me:

I’ve applied this fix on 2 nodes in a two node HV failover cluster. (LAB based on iSCSI shared storage)
DPM2012SP1 with latest rollups is still not able to backup a single VM on this cluster.
DPM encountered a retryable VSS error…

KB2848344 is titled  Update improves cluster resiliency in Windows Server 2012 and was released June 13, 2013.

I blogged about previous storage issue and the Microsoft attempts to solve this here:
Microsoft releases 2nd bug fix to fix issues on CSV backup of Windows Server 2012 Hyper-V
here
Storage issues on Windows Server 2012 Hyper-V. Microsoft struggling to fix!
and here
Important update that improves cluster resiliency in Windows Server 2012 is available

I guess you can make your own conclusions on the reliability of the storage integration with Windows Server 2012 Hyper-V! Quite a few customers have difficulties to make a proper backup or not able to make a backup at all without the risk of crashing volumes. Not good at all!

For an overview of issues which are backup related see this thread on Microsoft.com

BTW: Microsoft also released a bugfix for Offloaded Data Transfer (ODX) issues described in KB2796995.

As stated by Microsoft in this KB:

This update replaces a previous resiliency improvements update that is described in KB 2838669. Additionally, the following issues that you experience are resolved.

 

This article introduces an update for cluster resiliency improvements in Windows Server 2012. After you install this update, the issues that are described in the following Microsoft Knowledge Base (KB) articles are resolved:

2801054

      (http://support.microsoft.com/kb/2801054/            )

VSS_E_SNAPSHOT_SET_IN_PROGRESS error when you try to back up a virtual machine in Windows Server 2012

2796995

      (http://support.microsoft.com/kb/2796995/            )

Offloaded Data Transfers fail on a computer that is running Windows 8 or Windows Server 2012

2813630

      (http://support.microsoft.com/kb/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

2824600

      (http://support.microsoft.com/kb/2824600/            )

Virtual machine enters a paused state or goes offline when you try to create a backup of the virtual machine on a CSV volume in Windows Server 2012

2848727

      (http://support.microsoft.com/kb/2848727/            )

“Move-SmbWitnessClient” PowerShell command fails in Windows Server 2012

2799728

      (http://support.microsoft.com/kb/2799728/            )

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

Note This update replaces a previous resiliency improvements update that is described in KB 2838669.
Additionally, the following issues that you experience are resolved.

Issue 1

Assume that you have a Windows Server 2012-based failover cluster. A Cluster Shared Volume (CSV) is moved or is toggled between directed access and redirected access when the performance monitor is running. In this situation, the performance counters no longer function.

Issue 2

Consider the following scenario:

  • You have the Hyper-V server role installed on Windows Server 2012-based failover cluster nodes.
  • Virtual Hard Disk (VHD) files of the virtual machines are stored on a scale-out file share.
  • The cluster nodes are under heavy loads.

In this scenario, the cluster nodes may crash, and you may receive a Stop error message that resembles the following:

STOP: 0x000000C2 (parameter1, parameter2, parameter3, parameter4)

Add a Comment

Your email address will not be published. Required fields are marked *

Current ye@r *