Users Guide

40 Implementing High Availability in Hyper-V
4 When prompted by the wizard, choose Virtual Machine as the resource
type and the wizard will automatically list all the VMs that meets the basic
requirements for an HA VM.
NOTE: If a specific VM is not listed here, make sure that VM has met all the
pre-requisites for HA VMs.
5 Select the appropriate VM and proceed with the configuration.
6 Upon completion, the High Availability wizard also generates a report of
the HA VM configuration that needs to be reviewed to make sure there
were no issues.
7 The VM is now an HA VM and is ready to be turned on from either the
Hyper-V Manager console or the Failover Management console.
8 At the end of this configuration, the Failover Cluster Management
console will list the newly created Resource Group,
Virtual Machine
(n)
, for the HA VM. This Virtual Machine (n) Resource Group
will list all the dependencies for the VM.
NOTE: It is recommended to run the dependency report for the Resource
Group to confirm that the cluster service has made the right dependency
mappings for the HA VM. Click on the "Show Dependency Report" available in
the Failover Clustering console to generate this dependency report.
9 It is recommended the name of the resource group be changed from
Virtual Machine (n) to a name that more closely reflects the VM
hosted within that group.
Migrating HA VMs Across Hosts in the Cluster
With the VMs configured as HA VMs, they are now capable of handling both
planned and unplanned downtime scenarios. For unplanned downtime, the
Failover Cluster service will take care of moving the HA VMs on the other
cluster nodes. For planned downtime scenarios, administrators can migrate
HA VMs to the other cluster nodes.
This activity is initiated from the Failover Cluster Management console.
1
Open the Windows Failover Cluster Management console and select the
appropriate
Resource Group hosting the HA VM that needs to be
migrated to another node.
2 Select Move virtual machine(s) to another node . The console will list the
available target nodes in the Hyper-V Host Cluster.