HP Insight Control Software for Linux - Manual (Page 22)

The failed host recovery feature enables you to recover a failed virtualchines of Hyper-V R2 server and
leverage the ability of Systems Insight Manager SIM to detect hardware failures. For Microsoft Hyper-V R2
Server, virtual machines on failed hosts must meet the following requirements to be recovered on alternate
hosts:
•
The virtual machine must not be highly enabled.
•
The virtual machine configuration and disk files must be on cluster shared volumes.
•
The virtual machine must not have passed through disk(RDM) disk attached to it.
NOTE: For Microsoft Hyper-V R2 Server, the highly available virtual machines will be recovered by the
Microsoft ailover clustering feature in Microsoft Hyper-V.
Setting up the recovery feature
1. In Systems Insight Manager create a CriticalVmHost collection based on the system health parameters.
2. Set the alternate host for your virtual machines so that you have defined alternate hosts appropriately.
3. Schedule the recovery of failed virtual machine hosts based on the collection and events.
Recovery actions do not occur on virtual machine hosts or virtual machines unless you have set an
alternate host set, even if those virtual machine hosts or virtual machines are included in the CriticalVmHost
collection. To schedule the recovery of virtual machines of failed hosts for any system that has turned
critical and is part of the CriticalVmHost collection:
1. From the Systems Insight Manager toolbar, select Deploy
→Virtual Machine→Recover Virtual
Machines of Failed Host .
The Step 1: Select Target Systems screen appears.
2. From the Add targets by selecting from list, select CriticalVmHost.
3. Select Select “CriticalVmHost” itself as the target. Click Apply.
22 Using virtual machine management