Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

Cluster Shared Volume (CSV) not failing over on Hyper-V 2-node Cluster

$
0
0

Hi,

We have a 2-node Hyper-V cluster in testing and I'm having a problem with the disks on it. Both nodes have 1 storage HBA each which connect to a SAN over 2 switches (the nodes stay connected as long as 1 switch is running). On the SAN I have a volume configured as a CVS that contains all VM info and VHDs. The quorum volume is also on the SAN.

In Failover Cluster Manager under Storage > Disks I have the Hyper-V volume and it's assigned to to Cluster Shared Volumes. It is set to owner node 1 in this instance.

Now whenever I simulate a HBA failure on Node 1 (I just remove the cables) the Hyper-V CVS will go offline and stay offline, taking the VM roles with it. Is it not supposed to failover to Node 2 and redirect access via Node 2 to Node 1? Should it be in redirected access? I also have the owner node of the Disk Witness set to Node 2 and when I "fail" the HBA on Node 2 the quorom also goes offline. My quorum is set to Node and Disk Majority, should it be Node and File Share Majority for a SAN volume?

I appreciate all the help in advance.

EDIT: just some more info, when the cluster fails to bring the CSV back online after the HBA fails and I try to move it to Node 2, it will give me an error: Move didn't complete can't find the file specified.


Viewing all articles
Browse latest Browse all 6672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>