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 21
packages will then lead to a lack of necessary NFS ressources for
otherwise unrelated SAP Systems. The SAPNFS package avoids this
unpleasant dependency.
It is an option to move the system specific volume groups to the SAPNFS
package. This can be done, to keep HA NFS mechanisms completely
separate.
A valuable naming convention for most of these shared volume groups is
vg<pkgtype><SID> or alternatively vg<pkgtype><SID><INSTNR>. A
recommended naming convention for complete failover packages is
<pkgtype>SID or <pkgtype><SID><INSTNR>. Instance numbers would
only be added for additional Application Server packages. Table 1-1
provides an overview of the SAP specific mount points in a clustered
environment.
Table 1-1 Overview of SAP Specific Mount Points
Mount Point
Access
Point
Potential
Owning
Packages
Possible
Volume
Group
Volume
Group
Type
/usr/sap/<SID>/DVEBMGS<INSTNR> shared
disk
ci<SID>
dbci<SID>
vgci<SID>
vgdbci<SID>
SAP instance
specific
/usr/sap/<SID>/D<INSTNR> shared
disk
d<INSTNR>
<SID>
vgd<INSTNR><
SID>
SAP instance
specific
/export/sapmnt/<SID> shared
disk and
HA NFS
db<DBSID>
dbci<SID>
SAPNFS
vgdb<DBSID>
vgdbci<SID>
vgnfs
system
specific
/export/usr/sap/trans vgdb<DBSID>
vgdbci<SID>
vgnfs
environment
specific
/usr/sap/tmp local
disk
none vg00 host specific
/usr/sap/<SID> vg02 system
specific
/home/<sid>adm vg01