Configuration Rules for a Mixed HP 9000 / Integrity Serviceguard Cluster, March 2007
Table Of Contents
- Executive summary
- Version history
- Introduction
- Architectural rules and typical configurations
- Specific ISV information
- HP Superdome Hybrid Servers
- Typical configuration examples
- Transition to Integrity with HP Superdome hybrid servers and mixed clusters
- Adding one Integrity server to a two-node HP 9000 cluster
- Adding two HP Integrity servers to a two-node HP 9000 cluster
- Adding one critical application and two new Integrity nodes to existing four-node HP 9000 cluster
- Mixed clusters as transition aid from HP 9000 to Integrity in a multi-tier SAP environment
- HP 9000 to Integrity transition service utilizing HP Serviceguard cluster technology
- How to implement a mixed HP 9000 / Integrity HP Serviceguard cluster
- For more information
Figure 6. Original two-node HP 9000 cluster
App Server
Database Server
Failover
PA
PA
Node A
Node B
OK
New four-node mixed HP 9000 / Integrity cluster
After the two new Integrity servers are added to the cluster, the database and application server
packages are reconfigured. The database server is completely transitioned to the new Integrity
servers. The original primary database server (node B) gets redeployed as an application server. The
failover scenarios are:
• Node A fails.
– No failover occurs; node B takes over application server load for all users;
– Optionally, the application server instance from node A fails over to node B if more preferred by
the application.
• Node B fails.
– No failover occurs; node A takes over the application server load for all users.
– Optionally, the application server instance from node B fails over to node A if more preferred by
the application.
• Node C fails.
– Database server 1 fails over to node D; node D runs both database server 1 and 2.
• Node D fails:
– Database server 2 fails over to node C; node C runs both database server 1 and 2.
Note
Because the new Integrity nodes C and D run databases that don’t allow to
failover among heterogeneous nodes, only node C and D are configured to
run the database packages. Node A and B are not configured to run the
database.
20