Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Understanding Serviceguard Extension for SAP on Integrity Linux
Planning the LVM Layout for Clustered SAP Environments
Chapter 1 29
needs to be configured for the shared logical volume to allow core
dumps. It is also obvious, that files of that size should not be
transferred via NFS.
• /var/spool/sql: This directory hosts local runtime data of all
locally running SAPDB/Livecache instances. Most of the data in this
directory would become meaningless in the context of a different host
after failover. The only critical portion that still has to be accessible
after failover is the initialization data in /var/spool/sql/ini. This
directory is usually very small (< 1Megabyte).
NOTE If you install several SAPDB RDBMS, it is a good advice to provide a
shared /var/spool/sql/ini before installation. This helps to prevent
error-prone merge operations on multiple versions of the registry files in
that directory.
Table 1-4 shows the file system layout for SAPDB clusters.
Table 1-4 File System Layout for SAPDB Clusters
Mount Point
Access
Point
Potential
Owning
Packages
Possible
Volume
Group
Volume
Group
Type
/sapdb/<DBSID>
/sapdb/<DBSID>/wrk
/sapdb/<DBSID>/data<nr>
/sapdb/<DBSID>/saplog<nr>
shared
disk
db<DBSID>
dbci<SID>
vgdb<DBSID>
vgdbci<SID>
db instance
specific
/export/sapdb/programs
/export/sapdb/data
/export/var/spool/sql/ini
shared
disk and
HA NFS
dbci<SID>
SAPNFS
vgdbci<SID>
vgnfs
environment
specific