Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

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.
The combination of Serviceguard package name, virtual IP address, the EXCLUSIVE file system and the
application to start and stop are considered to be an entity.
Conclusion: Mount Points, Access Types and SGeSAP/LX Package
The following gives a final overview of some mount points, the access type and the SGeSAP/LX package
that will us the mount point.
Table 2-7 SAP CI mount point and SGeSAP/LX package
SGeSAP/LX PackageAccess TypeMount Point
ci<SID> or dbci<SID>EXCLUSIVE/usr/sap/<SID>/DVEBMGS<INSTNR>
d<INSTNR><SID>/usr/sap/<SID>/D<INSTNR>
sapNFS or db<SID>, dbci<SID>NFSlink /sapmnt/<SID>-> /import/sapmnt/<SID>/
nfsreloc:/export/sapmnt/<SID> /import/sapmnt/<SID>
link /usr/sap/trans -> /import/trans/
nfsreloc:/export/usr/sap/trans /import/trans
noneLOCAL/usr/sap/tmp/usr/sap/<SID>/home/<sid>adm
Table 2-8 Other SAP component mount points and SGeSAP/LX packages:
SGeSAP/LX PackageAccess TypeMount Point
jci<SID>EXCLUSIVE/usr/sap/<SID>/SCS<INSTNR>
ci<SID>/usr/sap/<SID>/ASCS<INSTNR>
rep<SID> (1)/usr/sap/<SID>/ERS<INSTNR>
arep<SID> (1)/usr/sap/<SID>/ERS<INSTNR>
NOTE: The (1)indicates that the ABAP and the JAVA Enqueue Replication Services have different instance
numbers.
MaxDB mount points and SGeSAP/LX packages
The considerations given below for MaxDB will also apply to liveCache clusters unless otherwise noticed.
• /sapdb/programs: this can be viewed as a central directory with all MaxDB executables. The
directory is shared between all MaxDB instances that reside on the same host. It is also possible to
share the directory across hosts. But it is not possible to use different executable directories for two
MaxDB instances on the same host. Furthermore, it might happen that different MaxDB versions get
42 Planning a File System Layout for SAP in a Serviceguard/LX Cluster Environment