Failover Cluster issues with vms moving

Hello Brandon,

When clustered VMs move or shut down unexpectedly, the cluster service is reacting to perceived failures. The most common causes are heartbeat loss between nodes, CSV I/O stalls, or scheduled maintenance such as Windows Update forcing reboots. You should check the Failover Cluster Manager and System Event Logs for Event IDs 1069, 1205, or 1135 to confirm whether the cluster is evicting nodes or failing over workloads. Also verify CSV health and storage paths, as latency or drops can trigger migrations. If updates are applied overnight, configure Cluster‑Aware Updating (CAU) to sequence patching properly. Finally, ensure quorum and witness configuration are stable, since quorum instability can cause nodes to evict themselves.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Harry.

It sounds like you're experiencing unexpected behavior with your failover cluster, where virtual machines (VMs) are moving to other hosts or shutting down without clear reasons. This can be caused by several factors:

1. Resource Failure: If a resource fails, the cluster may automatically move the affected VMs to another node to maintain availability.
2. Networking Issues: Problems such as node eviction due to network issues can trigger failover events.
3. Cluster Shared Volume (CSV) Issues: If there are issues with the CSV, such as being in a paused state, it can lead to VMs becoming unresponsive or shutting down.
4. Scheduled Tasks or Maintenance: Ensure that there are no scheduled tasks or maintenance operations that might be causing the VMs to move or shut down.

To troubleshoot this issue, consider checking the following:

• Review the System Event Log for any errors or warnings around the time the VMs moved or shut down.
• Check the cluster logs for any indications of resource failures or network issues.
• Ensure that all nodes are properly configured and that there are no misconfigurations in the networking setup.
• Monitor the performance of the storage and network components to identify any bottlenecks or failures.

If the problem persists, further investigation into the cluster configuration and logs may be necessary to identify the root cause.

References:

• Unexpected cluster failover troubleshooting guidance
• Troubleshoot storage issues in Hyper-V and Windows Server failover clusters