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

31
• SAP
– SAP software running on HP-UX 11i v2 or 11i v3
– For SAP, the latest information can be found on SAP’s Service Marketplace website
(
www.service.sap.com/notes Note: access to this site requires a support contract).
– Third party applications used by SAP depend on support by the third party
– SGeSAP is not supported on VM as Serviceguard package configurations
• ISV applications
– Integrity VM is binary compatible with HP-UX 11i v2 and 11i v3 Itanium native applications (Note that
applications with specific device dependencies should be reviewed for supportability)
• HP ECMT and Serviceguard developers Toolbox
– ECMT version B.05.00 (and later) and the developers Toolbox version A.01.00 is supported in VM as
Serviceguard node configurations
• HP Disaster Recovery solutions
– Serviceguard Extended Distance Clusters for VM as package configurations (for all Integrity VM-supported
Serviceguard versions)
– VM as Serviceguard package configurations using the following Metrocluster and Integrity VM version
combinations are supported:
 Metrocluster with Continuous Access EVA A.03.00—A.05.01/Integrity VM B.04.00—B.04.30
 Metrocluster with Continuous Access XP A.08.00—A.11.00/Integrity VM B.04.00—B.04.30
 Metrocluster with EMC SRDF A.07.00—A.09.01/Integrity VM B.04.00—B.04.30
– VM as Serviceguard node configurations using the following Metrocluster and Integrity VM version combinations
are supported:
 Metrocluster with Continuous Access EVA A.05.01/Integrity VM B.04.20—B.04.30
– Metrocluster with HP 3PAR Remote Copy is not currently supported with any HPVM configuration
– VM as Serviceguard package configurations using the following Continentalclusters and Integrity VM version
combinations are supported:
 Continentalclusters A.08.00/Integrity VM B.04.20—B.04.30 with any of the Metrocluster products that
support Metrocluster VM as Serviceguard package configurations
– VM as Serviceguard node configurations using the following Continentalclusters and Integrity VM version
combinations are supported:
 Continentalclusters A.08.00 / Integrity VM B.04.20—B.04.30 with Metrocluster with Continuous Access EVA
A.05.01 only.
HP Integrity VM high availability architecture considerations
Integrity VM provides the ability to create VMs, or virtual hardware systems implemented in software, consisting of a
collection of virtual hardware devices that interact with actual physical hardware (CPU, memory, I/O) on a host
system. With this virtual to physical hardware association, it is important to consider how these components interact
and how they affect the performance and availability of the VMs and the applications running within them. The
following sections describe several aspects of VM hardware and software configurations, in general, and with
Serviceguard, that should be considered prior to implementing any solution. Additional information on VM
configuration restrictions can be found in the HP Integrity virtual machines release notes and the HP Integrity virtual
machines installation, configuration, and administration guide (Integrity VM documentation available at
www.hp.com/go/hpux-hpvm-docs) associated with the Integrity VM version being deployed.