Failover MS Cluster with Starwind

[nimeijer]

Situation: 2 Win2k8 r2 servers with Starwind HA disks, clustered for hyperv.
When I reboot one of the nodes, my VM's do a proper failover to the other node.
All disks, including the quorum disk do a proper failover to the other node.
Starwind syncs automaticly when I restart the lost node.
Everything looks great and works fine in this scenario.

But,
When I pull the plug from one of the nodes the cluster looses it's quorumdisk and the cluster goes offline.
Does anyone have any idea of the diffrence between a proper shutdown and a 'pull-the-plug' shutdown regarding Starwind ?

[anton (staff)]

It does not matter what you do put machine down in a graceful way, power it off with a low kick, blow with a torch or use nuclear blast to wipe if out everything should work fine. So what you see is WRONG behaviour of StarWind-powered cluster and we cannot live with it. Please re-produce the whole thing and send us logs from your both HA nodes (dead one after you'd recover it and the one left alive). In the wrong case be ready for our engineer jumping in on remote session. We really want to fix this before V5.7 release. Thank you very much for cooperation!

P.S. I assume you run the most recent build of V5.6 don't you?

Situation: 2 Win2k8 r2 servers with Starwind HA disks, clustered for hyperv.
When I reboot one of the nodes, my VM's do a proper failover to the other node.
All disks, including the quorum disk do a proper failover to the other node.
Starwind syncs automaticly when I restart the lost node.
Everything looks great and works fine in this scenario.

But,
When I pull the plug from one of the nodes the cluster looses it's quorumdisk and the cluster goes offline.
Does anyone have any idea of the diffrence between a proper shutdown and a 'pull-the-plug' shutdown regarding Starwind ?