Users Guide

Clustering Implementations for High Availability 17
retained and there is possibility for data loss. To the guest operating system,
this is similar to an unexpected restart of the operating system. However, the
failover of VMs is automatically handled by the cluster service, and workloads
running within the VMs are back online in a short period of time. Here is a
high-level workflow of the unplanned failover scenario:
1
A node in the Hyper-V Host Cluster configuration fails. All states of the
VM (including guest OS and workloads within the VMs) that have not
been committed to SAN storage are lost.
2 Cluster service transfers ownership of SAN storage disk resources from the
failed node to other nodes in the Hyper-V Host Cluster.
3 VMs are restarted on the other nodes of the Hyper-V Host Cluster.
Figure 2-6. Hyper-V Host Cluster with Both Servers Running