Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Directories that Reside on CFS
The following table shows a recommended example on how to design SAP file systems for CFS
shared access.
Table 7 File System Layout for SGeSAP CFS Clusters
DG NamePackage Name Example (legacy CFS packages)Access PointMount Point
SG-CFS-DG-<NR1>SG-CFS-MP-<NR1>shared disk and
CFS
/sapmnt/<SID>
SG-CFS-DG-<NR2>SG-CFS-MP-<NR2>/usr/sap/trans
SG-CFS-DG-<NR1>SG-CFS-MP-<NR3>/usr/sap/<SID>
The table can be used to document used volume or disk groups across all cluster nodes.
The /usr/sap/tmp might or might not be part of the local root file system. This is the working
directory of the operating system collector process saposcol. The size of this directory is usually
not more than a few Megabytes.
Database Instance Storage Considerations
SGeSAP internally supports clustering of database technologies of different vendors. The vendors
have implemented individual database architectures. The storage layout for the SGeSAP cluster
environments needs to be discussed individually for each of the following:
• Oracle Single Instance RDBMS
• Oracle Real Application Clusters
• MaxDB Storage Considerations
• DB2 Storage Considerations
• ASE Storage Considerations
Table 8 Availability of SGeSAP Storage Layout Options for Different Database RDBMS
Cluster Software BundlesSGeSAP Storage
Layout Options
Supported
Platforms
DB Technology
ItaniumOracle Single-Instance 1. Serviceguard or any Serviceguard Storage
Management bundle (for Oracle)
PA 9000
2. SGeSAP
3. Serviceguard HA NFS Toolkit
idle standby 1. Serviceguard
2. SGeSAP
3. Serviceguard HA NFS Toolkit (opt.)
CFS 1. Serviceguard Cluster File System (for Oracle)
2. SGeSAP
CFSOracle Real
Application Cluster
1. Serviceguard Cluster File System for RAC
2. SGeSAP
NFSSAPDB MaxDB 1. Serviceguard or any Serviceguard Storage
Management bundle
2. SGeSAP
3. Serviceguard HA NFS Toolkit
36 Planning the Storage Layout