Hyper-V servers failover problems
Posted: Thu Nov 13, 2014 3:51 pm
Okay, this isn't so much a tech support request as much as just asking the community whether my expectations are realistic... and it's gonna be long!
Our setup is two clustered Hyper-V servers, running Windows 2012 and Starwind native SAN for Hyper-V version 6.0.6399. There are two HA devices on each node - a large (~1.2TB) one for data and a small (1GB one for quorum). MS ISCSI initiator is used on both nodes to connect to both nodes, and cluster shared storage is set up in the usual way (as far as I know... I'm pretty new to clustering). Each server has one 1GB dedicated NIC connected to a dedicated NIC on the other server for Starwind synchronization, and another for Starwind heartbeat. In addition there's a management NIC connected to our LAN, and 4 other NIC ports that the VMs use to communicate to the LAN.
When we try to do a failover "cleanly", through the management tools, everything works fine. The VM or VMs stops on one server, starts up on the other one, birds chirp, the sun shines, and all is well.
But lately one server has been having hardware problems and when that happens failover does not occur. The other server is still running, but when you run failover cluster manager it pretty much acts as if the cluster doesn't exist. If you try to "Connect to cluster" the cluster shows in the selection list but when you actually try to connect it says the cluster service is not running... but it is in fact running (on that server).
In this condition, Starwind *seems* to be working... I didn't check ultra-thoroughly last time this happened as I was hurrying to get the system back up, but I could drill down from C: into "cluster shared storage" and everything seemed present and accessible.
Now here's the best part: my coworker, who's as green with clustering as I am, has convinced himself this is normal... if one server's hardware fails or connectivity between the two fails, he thinks the cluster is just supposed to stop.
I think that's crazy... otherwise what's the point of having a cluster.
So who's right?
Our setup is two clustered Hyper-V servers, running Windows 2012 and Starwind native SAN for Hyper-V version 6.0.6399. There are two HA devices on each node - a large (~1.2TB) one for data and a small (1GB one for quorum). MS ISCSI initiator is used on both nodes to connect to both nodes, and cluster shared storage is set up in the usual way (as far as I know... I'm pretty new to clustering). Each server has one 1GB dedicated NIC connected to a dedicated NIC on the other server for Starwind synchronization, and another for Starwind heartbeat. In addition there's a management NIC connected to our LAN, and 4 other NIC ports that the VMs use to communicate to the LAN.
When we try to do a failover "cleanly", through the management tools, everything works fine. The VM or VMs stops on one server, starts up on the other one, birds chirp, the sun shines, and all is well.
But lately one server has been having hardware problems and when that happens failover does not occur. The other server is still running, but when you run failover cluster manager it pretty much acts as if the cluster doesn't exist. If you try to "Connect to cluster" the cluster shows in the selection list but when you actually try to connect it says the cluster service is not running... but it is in fact running (on that server).
In this condition, Starwind *seems* to be working... I didn't check ultra-thoroughly last time this happened as I was hurrying to get the system back up, but I could drill down from C: into "cluster shared storage" and everything seemed present and accessible.
Now here's the best part: my coworker, who's as green with clustering as I am, has convinced himself this is normal... if one server's hardware fails or connectivity between the two fails, he thinks the cluster is just supposed to stop.
I think that's crazy... otherwise what's the point of having a cluster.
So who's right?