How many of you actually read through the release notes of a new vSphere release? Ok, I know that Maish does. If you read Maish’s post or read the vSphere 5.1 Release Notes you would see the following:
Windows Server 2012 Failover Clustering is not supported
If you try to create a cluster for Failover Clustering in Windows Server 2012, and select to run validation tests, the wizard completes the validation tests with warnings, and after that returns to running the validation tests again. The wizard in the Windows Server 2012 guest operating system does not continue to the cluster creation stage.
I admit I didn’t notice it myself and had it recently pointed out to me. It’s unfortunate that this piece of information is buried in the Release Notes and not listed in the VMware Knowledgebase, the vSphere 5.1 Clustering Guide, etc. Despite the fact that many in the industry despise virtualized Windows Failover Clusters, the fact remains that organizations use them and will continue to use them. vSphere HA can sometimes serve as a replacement but not always. More on my thoughts on this subject here.
To make sure everyone understands the issue here – when creating a Windows Failover Cluster, you can run through a validation process to make sure the cluster will function properly. Microsoft will only support a cluster (virtual or physical) if it has been validated. As you can see in the Release Notes, it appears that Windows 2012 Failover Clusters do not successfully complete the validation step.
I figured I’d give this a try and see if I can reproduce the issue and to my surprise I cannot. I’ve tried the traditional method of clustering virtual machines by using RDMs in physical compatibility mode. I’ve also tested using storage presented via the iSCSI initiator inside the virtual machine. In both cases I was able to validate the cluster and receive a validated rating that is good enough to qualify for Microsoft support.
I’m not sure what the actual problem is with Windows 2012 Failover Clusters but I’m unable to reproduce the behavior listed in the Release Notes. The behavior described in the Release Notes is what happens when the cluster fails the validation test and is actually expected. If your cluster passes the validation tests, as mine did in the tests I ran, it proceeds to create the cluster without an issue.
Hopefully VMware will clarify this issue for us and/or change their support stance. I firmly believe you should stick with what is supported when virtualizing business critical applications. In this case I can’t even figure out why it isn’t supported in the first place, but do have to recommend that organizations hold off on virtualizing Windows 2012 Failover Clusters until this support statement is changed.
Anyone else tried to virtualize a Windows 2012 Failover Cluster and see the behavior that VMware describes?