Using HP Serviceguard for Linux with VMware

A Serviceguard cluster consisting of a VM guest and a physical server is shown in Figure 8. This

cluster provides HA for the applications against failures of physical nodes, VMware ESX hypervisor,

VM guest, and failure of the application itself. A failed application can be restarted on the same VM

guest, or failed over to the physical node. This configuration allows consolidation of multiple active-

standby clusters where the primary active node remains a physical node and multiple standby nodes

are consolidated as VM guests on one host.

Packa

e Failover

Service

uard

Linux Cluster

VMwa

3.0.

sical server

VM Guest 1

Figure.9 Serviceguard cluster of VM guest and Physical node

Packa

e Failover

Service

uard

Linux Cluster

VM Guest 1

VMware ESX 3.0.2

Figure.10 Serviceguard cluster of VM guests on separate Physical nodes

A Serviceguard cluster consisting of VM guests on separate physical servers is shown in Fig.9. In

this configuration, SG provides high availability for applications against failures of physical nodes,

VMware ESX hypervisor, VM guest, and failure of application itself. A failed application can be

restarted on the same VM guest or failed over to another VM guest on a different physical node.

Data integrity during package failover

Virtual machines run on ESX server hypervisor. When a virtual machine dies, Serviceguard fails over

the applications running on the failed machine to another physical server or a VM running on another

machine. Serviceguard maintains data integrity between the failed application and the new instance

of it using persistent reservation of LUNs shared between nodes of the cluster. Shared storage used in