Designing High Availability Solutions with HP Serviceguard and HP Integrity Virtual Machines

3
Figure 1: Integrity VM components
2
Integrity VM can be used with other Matrix OE components for Workload Management and HP Instant Capacity on
VM hosts, including:
• HP Workload Manager (WLM)
• HP Global Workload Manager (gWLM)
• HP Temporary Instant Capacity (TiCAP)
• HP Global Instant Capacity (GiCAP)
These Matrix OE components can be implemented within the VM host to allocate system resources as-needed for the
VMs running on the host. HP-UX Processor Sets (PSETS), HP Process Resource Manager (PRM), WLM, and gWLM are
supported running inside a VM guest; however, the use of TiCAP and GiCAP inside a VM guest is not supported.
Serviceguard for high availability
HP Serviceguard creates high availability clusters using a networked grouping of HP Integrity and HP 9000 servers.
These servers are typically configured with redundant hardware and software components to eliminate single points
of failure (SPOFs). Serviceguard is designed to keep application services running in spite of hardware (for example,
system processing unit, disk, LAN, etc.) or software (for example, operating system, user application, etc.) failures. In
the event of a hardware or software failure, Serviceguard and other high availability subsystems coordinate
operational transfer between components.
2
This figure is applicable for Integrity VM versions B.04.00 through B.04.20.05. For Integrity VM version B.04.30, only HP-UX 11i v2 and 11i v3 are
supported as guest OS.
HP Integrity VM Host
Integrity Hardware
HP-UX 11i v2
app 1 app 2
Linux RH4
app 1
Windows
app 1
HP-UX 11i v3
app 1 app 2
Linux SLES 10
app 1
Windows
app 1
Processors Memory I/O
HP Integrity VM Host
Integrity Hardware
HP-UX 11i v2
app 1 app 2
Linux RH4
app 1
Windows
app 1
Windows
app 1
HP-UX 11i v3
app 1 app 2
Linux SLES 10
app 1
Windows
app 1
Windows
app 1
Processors Memory I/O