We are having multiple issues with a Hyper-V Cluster.

New to Hyper-V Clustering, but very familiar with VMware Clusters and High Availability.

A previous IT Company setup our new Client with 3 2012 R2 Hyper-V Hosts. Each Node has the same hardware.

They have an HP MSA 2040 SAN, and 3 Cluster Shared Volumes.

There was a second Cluster setup as a Scale out File Server, and it has its own Cluster Shared Volume for VDI template and User Profile Disks.

VMs on the main Cluster depend on the VDI template and UPDs on the second Cluster.

How do we unmake this mess?

What is the issue?  Why is it a mess?

We are having multiple issues with a Hyper-V Cluster.

New to Hyper-V Clustering, but very familiar with VMware Clusters and High Availability.

A previous IT Company setup our new Client with 3 2012 R2 Hyper-V Hosts. Each Node has the same hardware.

They have an HP MSA 2040 SAN, and 3 Cluster Shared Volumes.

There was a second Cluster setup as a Scale out File Server, and it has its own Cluster Shared Volume for VDI template and User Profile Disks.

VMs on the main Cluster depend on the VDI template and UPDs on the second Cluster.

How do we unmake this mess?

Create flat linear address space and have single big LUN and one CSV on top. Performance is going to suffer but because you have only 3 nodes and VDI profiles are seldom used it's irrelevant...

Hi BCT-Tech,

What are you trying to do now? The failover cluster use the shared storage as the necessary condition, if you are not very familiar with this model you can first refer the following article to understand it first.

How to configure two node Windows Server 2012 cluster on Virtual Machines for testing?

http://blogs.technet.com/b/babulalghule/archive/2013/02/16/how-to-configure-two-node-windows-server-2012-cluster-on-virtual-machines-for-testing.aspx

Im glad to be of help to you!