Hyper-V 3.0 2012 Cluster KB’s to be Aware of…
I have over the last couple of months come across a couple of KB’s that really are must reads for anyone who has deployed or is planning a Windows Server 2012 Hyper-V cluster.
Unreliable Hyper-V 2012 Cluster, possibly backup related issues with event ID 1520…
This first one is a hotfix which as of writing hasn’t been included as an automatic update. If you are seeing lots of VMs randomly stopping, migrating, failing in general and lots of events related to storage being unavailable and it looks to you like it may be backup related it probably is. VSS aware backup products backing up VMs on a 2012 CSV will probably have some issues and in particular you will see lots of event ID 1520, I have seen DPM causing this issue on multiple occasions.
Read this first:
Then this, which supersedes the last one and is where you can request the hotfix:
Guest Clustering in Hyper-V 2012, creating cluster fails…
Another biggie I have come across is when creating guest clusters including DAG’s. Guest clustering to my mind is very important if Hyper-V will ever truly compete with VMware so it is very frustrating when trying to create, a DAG for example, and it repeatedly fails. When failing to create a DAG you might see something like this in the logs:
“[2013-09-11T15:02:36] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired”‘ failed. —> Microsoft.Exchange.Cluster.Replay.AmClusterApiException: An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API ‘”AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired”‘ failed.. —> System.ComponentModel.Win32Exception: This operation returned because the timeout period expired”
This doesn’t just affect DAGs, any guest cluster will run into issues. The problem is caused by the Windows Server 2012 teaming technology “Microsoft Failover Cluster Virtual Adapter Performance Filter”. The solution or more of a workaround really is to disable that technology on any teams in the parent cluster.
See this KB for details:
Hope this helps people clear up a few bugs in their 2012 Hyper-V clusters.