Please excuse any inaccuracies with my understandings as I still have limited Windows Server 2012 experience and no clustering experience. I am trying to build a Windows Server 2012 two-node failover cluster in a test lab environment (but this configuration should also be deployable to small/mid-sized businesses) that provides continuous availability to Hyper-V virtual machines. My goal is to use consumer-grade hardware (i.e., Supermicro 4u towers, SATA drives, onboard SATA controllers or inexpensive RAID cards, etc.) without a single point of failure (e.g. a dedicated SAN that is either iSCSI connected, or SMB shares provided externally that go offline). The ideal situation is that all Hyper-V related files are self contained within the two nodes of the cluster such that if one node fails, the other node takes up all load without service disruption.
Based off of previous research and discussion, I have found that Starwind’s Native SAN for Hyper-V accomplishes this, but I haven’t found a clear answer if this can be accomplished or not using built in WS12 solutions. I would like to explore JBOD Storage Spaces as well as Cluster Shared Volumes.
Proposed Setup:
Node 1: RAID1 mirror for boot, three additional SATA hard drives for cluster storage.
Node 2: RAID1 mirror for boot, three additional SATA hard drives for cluster storage.
Create a Windows Server 2012 Failover Cluster.
Create a storage pool with all six SATA drives across both nodes. (all data is mirrored across six discs on two nodes)
Create a fixed discs for cluster shared volumes. (if one node goes down, there is transparent failover for continuous data access)
Will this scenario work, even if my steps might be slightly wrong? If not, what changes can be made in order to accomplish this?
Thank you