Thank u very much :) Now we update to starwind v8 and playing around and have first problems.. Configuration 512mb FLAT, 32mb WT L1, L2 NaN, 2 MPIO links to Hyperv, 10G link 3tb LSFS Thin, no dedup, 3gb WB L1, 440gb WT L2 SSD, 4 MPIO links to Hyperv, 10G link data transmission stuck very often in lo...

lohelle wrote:I can say with many years of Starwind experience, that this should work. We are using Starwind for both VMware and Hyper-V clusters (HA).

Glad to here but in our environment, accordingly by manual setup this doesn't work. Planning to buy 3tb HA licence, but seems not Starwind solution

After lot of test we concluded.. Starwind HA not usable for failover cluster system. After one of two nodes is fail with VM on HA storage, migration failed with '0x80048007' or '0x80048005'. Seeking another software solution...

Our company deploy failover cluster based on Starwind SAN and Hyper-V according this manual (Starwind v6, Hyperv-v 2012) http://www.starwindsoftware.com/styles-v2/pdf/technical_papers/StarWind_HA_Hyper-V_6.0.pdf When we turn off one hyperv node, VM on HA storage entering in save state, then migrate ...