Windows 2012 R2 Hyper-V clustering using "share nothing" strategy

greetings,

i have been trying embrace share nothing strategy microsoft has put forth hyper-v clustering.  definition, "a shared nothing architecture distributed computing architecture in each node independent , self-sufficient, , there no single point of contention across system. more specifically, none of nodes share memory or disk storage."  have plenty of experience failover clustering using iscsi , fc.  but, looking out of lab true hv cluster relied on das , move away iscsi , fc, not dependent on 1 file server defeat sn strategy.

i have spent week on lab , gotten nowhere.  know if possible , point me step-by-step or lab goes start finish on topic?  have read begin using iscsi targets or network shared storage. 

thanks in advance.

shared-nothing-live-migration protects planned downtime (say need patch windows on host or replace or upgrade hardware components). see:

shared nothing live migration

http://blogs.technet.com/b/uspartner_ts2team/archive/2012/07/23/shared-nothing-live-migration-on-windows-server-2012.aspx

for unplanned downtime need either vm ha (little downtime, little data loss, vm reboots) or guest vm cluster (no downtime, no data loss, vm turns other host). see:

vms high availability

http://technet.microsoft.com/en-us/library/cc753787.aspx

guest vm cluster ha

http://technet.microsoft.com/en-us/library/dn440540.aspx

both require sort (physical or virtual) shared storage. physical may need csv configured on either clustered storage spaces or iscsi or fc san or smb3 share. see:

torage type	description
shared virtual hard disk	new in windows server 2012 r2, can configure multiple virtual machines connect , use single virtual hard disk (.vhdx) file. each virtual machine can access virtual hard disk servers connect same lun in storage area network (san). more information, see deploy guest cluster using shared virtual hard disk.
virtual fibre channel	introduced in windows server 2012, virtual fibre channel enables connect virtual machines luns on fibre channel san. more information, see hyper-v virtual fibre channel overview.
iscsi	the iscsi initiator inside virtual machine enables connect on network iscsi target. more information, seeiscsi target block storage overview and blog post introduction of iscsi target in windows server 2012.

for virtual may use either vm-running (slow , raises "egg , chicken" problem) or native virtual san. see:

virtual san (no hardware storage)

http://www.starwindsoftware.com/starwind-virtual-san

you'll have configuration similar picture (below). see:

so no physical shared storage, san emulated das. high performance (no network i/o) , fault tolerant (even pair of nodes components @ least duplicated). 

there other companies doing similar things. steeleye datakeeper (more replication but...)

hope helped :)

---

starwind vsan [virtual san] clusters hyper-v without sas, fibre channel, smb 3.0 or iscsi, uses ethernet mirror internally mounted sata disks between hosts.

Windows Server  >  High Availability (Clustering)