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

Planning a File System Layout for SAP in a Serviceguard/LX Cluster Environment
Overview Serviceguard packages
Chapter 2 69
•The package dbRIS is responsible for starting and stopping the
database application for SAP instance RIS.
•The package ciRIS is responsible for starting and stopping the SAP
central instance for id RIS.
•The package d01RIS is responsible for starting and stopping the SAP
dialog instance D01 for id RIS.
•The package sapNFS mount all NFS related storage volumes and
exports them to all cluster nodes
The naming convention is the following:
Lowercase instance type (ci, db, sap...)
Uppercase SAP instance name (RIS, NFS)
• Communication with a Serviceguard package is based on virtual IP
addresses dbris, ciris, d01ris and nfsris. Each package has its
own IP address.
• Each package has one or more file systems (storage volumes) that get
mounted when a package is started and unmounted when a package
is stopped.
• Normally any of the packages can be run or relocated on any of the
cluster nodes in any combination. So for example package dbRIS and
d01RIS can be run on the first node, sapNFS and ciRIS can be run on
the second node. Or package dbRIS can be run on the first node and
d01RIS, sapNFS and ciRIS can be run on the second or third or...
node. If the first cluster node fails all packages are relocated to the
second cluster node.
• As described in the above section, two file system categories
(SHARED NFS and LOCAL) are made available on all cluster nodes.
In this example these are:
— The NFS mount points /sapdb/data, /sapdb/programs....
— The LOCAL copy mount points /usr/sap/tmp,
/usr/sap/RIS/SYS.... The contents of these directories have to
be copied to all cluster nodes.
• File systems of type EXCLUSIVE get relocated together with its
Serviceguard package.