Windows – HyperV Failover Cluster (with/without CSV)

clusterhyper-vwindowswindows-server-2012windows-server-2012-r2

Been browsing a few websites, and it seems right now all hyper-v clusters are build on CSV ( clustered share volume ).

I have a current setup (2 node window failover cluster).

I have 2 vms running on node1 each in its own cluster disk e.g.

  • vmA (owner-node1) on clusterdisk1 (owner-node1)
  • vmB (owner-node1) on clusterdisk2 (owner-node1)

I have 1 vm running on node2 in its own cluster disk as well.

  • vmC (owner-node2) on clusterdisk3 (owner-node2)

q1) can the VMS in node1 run in the same clusterdisk ? (e.g. clusterdisk1) ?

q2) When node1 fail, node2 will take ownership of the clusterdisk1,2 and startup the VM;
So what is the difference between using clusterdisk and CSV ?

I am using window server 2012 r2

Best Answer

This link lists the benefits of CSVs

https://technet.microsoft.com/en-us/library/dd759255(v=ws.11).aspx

q1) can multiple VMs on Node1 run in the same clusterdisk?

I don't think that is possible (the article says no). Even if you could add multiple VMs to the same Clusterdisk it would mean if a single VM failed or needed to be moved it couldn't be moved independently. All the other VMs using the same clusterdisk would need to moved as well.

q2) When node1 fail, node2 will take ownership of the clusterdisk1,2 and startup the VM; So what is the difference between using clusterdisk and CSV ?

reduced number of LUNs, Better use of disk space, Reduced complexity. And I have found that failover / move is faster as well.

Related Topic