Solved Hyper-V Failover Clustering
-
Anyone know if Failover Clustering can be enabled on two existing Hyper-V hosts with VMs running, and replication occurring between the two hosts for a single VM?
-
@DustinB3403 said in Hyper-V Failover Clustering:
@travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.
Looking at different ways to try and remediate this from occurring again.
You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.
Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.
-
@DustinB3403 said in Hyper-V Failover Clustering:
Anyone know if Failover Clustering can be enabled on two existing Hyper-V hosts with VMs running, and replication occurring between the two hosts for a single VM?
Can it be, sure. Does anyone in their right mind want to tackle it, nope.
The pain point will be getting the storage setup to make it happen. My first thought would be a couple Starwind VMs to handle storage replication for that VM. Lots of overhead for not much gained I don't think.
Does it have to be true HA? Could they survive 5-10 minutes for Veeam to boot a backup copy if the VM goes down?
-
@travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.
Looking at different ways to try and remediate this from occurring again.
-
@DustinB3403 said in Hyper-V Failover Clustering:
@travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.
Looking at different ways to try and remediate this from occurring again.
You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.
Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.
-
@travisdh1 said in Hyper-V Failover Clustering:
@DustinB3403 said in Hyper-V Failover Clustering:
@travisdh1 The issues stem from the hypervisors being rebooted out of order, causing a server to start up before the DC which was on the other hypervisor.
Looking at different ways to try and remediate this from occurring again.
You never put a DC into an HA environment as all of that functionality is built into the DC itself, and trying to force it can create problems.
Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.
I agree with one DC on each host. Otherwise, that is a lot of additional complexity to have a cluster and shared storage just for this one issue...
-
@travisdh1 said in Hyper-V Failover Clustering:
Best thing to do is have a DC on both hypervisors. Either another VM, or add the role to a current VM on the host.
This was my same thinking.
-
You can have replication if you have Starwind Clustering on the hosts (That's how I have some customers). That said, even on those situations I have a DC on the Local Host Hyperv of one of the servers or have a Site to Site VPN with a DC on Azure or AWS as a failsafe.
