I have setup a new failover cluster. It has five members a witness disk and cluster storage for the VMs.
The hosts are new servers running server2019 and the version of VMM is also 2019.
The plan is to move VMs from our current hyperV cluster to this new one.
I validated my cluster without issue and I have been moving non essential VMs from the old to the new cluster. A couple of weeks ago I started experiencing an issue with the cluster. All of the VMs on a particular host report "Host not responding"
Despite this message the VMs work without issue, but I am unable to migrate the VMs to a different host. When I check the host it appears to be working ok but I cannot connect to hyperV within the host even though the services appear to be running. If I try and restart the host it fails to restart complaining that it cannot terminate failover cluster manager. The only method I have found to resolve the issue is to power off the host. Once back up everything works fine.
I thought it may have been an issue with AV or backup software, but I have removed the AV and the backup software runs without issue every day whereas this error can take several days before it reoccurs. It can be any of the hosts that has this issue and it doesnt appear to correspond with certain VMs being run by the host.
The hosts are new servers running server2019 and the version of VMM is also 2019.
The plan is to move VMs from our current hyperV cluster to this new one.
I validated my cluster without issue and I have been moving non essential VMs from the old to the new cluster. A couple of weeks ago I started experiencing an issue with the cluster. All of the VMs on a particular host report "Host not responding"
Despite this message the VMs work without issue, but I am unable to migrate the VMs to a different host. When I check the host it appears to be working ok but I cannot connect to hyperV within the host even though the services appear to be running. If I try and restart the host it fails to restart complaining that it cannot terminate failover cluster manager. The only method I have found to resolve the issue is to power off the host. Once back up everything works fine.
I thought it may have been an issue with AV or backup software, but I have removed the AV and the backup software runs without issue every day whereas this error can take several days before it reoccurs. It can be any of the hosts that has this issue and it doesnt appear to correspond with certain VMs being run by the host.