Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Understanding Serviceguard Extension for SAP on Linux
Designing Serviceguard Extension for SAP on Linux Cluster Scenarios
Chapter 114
A cluster can be configured in a way that two nodes back up each other.
The principle layout is depicted in figure 1-1. This picture as well as the
following drawings are meant to illustrate basic principles in a clear and
simple fashion. They omit other aspects and the level of detail that would
be required for a reasonable and complete high availability
configuration.
Figure 1-1 Two-Package Failover with Mutual Backup Scenario
Each package name should include the SAP System Identifier (SID) of
the system to which the package belongs. If similar packages of the same
type get added later, they have a distinct name space because they have
a different SID.
It is strongly recommended to base the package naming on the package
type naming conventions. This should be done by prefixing the package
type to the SID to get the package name. This allows easy identification
and support.
Serviceguard Extension for SAP on Linux Cluster
Mutual Failover
node1
node2
dbSID
ciSIDDB and CI
package can fail
and recover
independently
Application servers not part of cluster
shared disks