Configuration Rules for a Mixed HP 9000 / Integrity Serviceguard Cluster, March 2007

Table Of Contents

Figure 9. New six-node mixed HP 9000 / Integrity cluster

Node

NFS

IPF

Node

ERP

Node

Standby

Node

Financials

(FI)

Node

CRM

IPF

Mixed clusters as transition aid from HP 9000 to Integrity in a multi-tier

SAP environment

This example shows how a customer who initially uses a homogeneous cluster of four HP 9000 nodes

and takes advantage of the mixed cluster support to transition to an Integrity cluster in several steps.

This example is based on a SGeSAP configuration with Informix, DB2, or MaxDB at the database

layer.

Note:

For a configuration with single instance Oracle at the database layer, the

example would look less complicated since all systems would be allowed to

fail over between all nodes in the mixed cluster.

Initial four-node homogenous HP 9000 cluster

The initial cluster consists of four HP 9000 nodes, of which three are running mission-critical SAP

systems:

• Node A runs the database of the ERP system.

• Node B runs the central instance of the ERP system.

• Node C runs the database and central instance of the business warehouse (BW)—the SAP name for

the data warehouse application, which is used for online reporting—in a single HP Serviceguard

package.

The forth node (node D) runs a non-critical application server of the ERP system at normal times and is

configured to be the failover node for the applications running on node A, B, and C.