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
Configuration Scenarios
Chapter 256
Two ABAP DI’s and one ABAP SCS and one DB
Using the terminology of the previous example, the next configuration
scenario consists of one ABAP Central instance (= ABAP CI), one ABAP
Dialog instance (ABAP DI), one ABAP SAP Central Services (ABAP SCS)
and one Database instance (=DB). So compared to the previous example
one instance (ABAP SCS) will be added. This instance is identified by the
name “ASCS02”. By adding the ABAP SCS, the naming conventions of
the SAP components in this scenario have changed. The original ABAP
Central Instance (CI) became a ABAP Dialog Instance as the Message
Server and the Enqueue Server are now running within the ASCS and
not within the ABAP CI. To add an SAP ASCS instance to an existing
configuration only one new file system is required and that is
/usr/sap/C11/ASCS02.
The mount points to be analyzed in a cluster environment are:
SAP Instance
/usr/sap/tmp/
/usr/sap/trans/
/usr/sap/C11/DVEBMGS00/
/usr/sap/C11/D01/
/usr/sap/C11/ASCS02/ <--- new
/usr/sap/C11/SYS/exe/run
/sapmnt/C11/
/home/C11/adm
DB Instance
The file systems for the database have not changed and are now not
listed any more.