Managing Serviceguard Extension for SAP, December 2007

Planning the Storage Layout
SAP Instance Storage Considerations
Chapter 256
The tables can be used to document used device minor numbers. The
device minor numbers of logical volumes need to be identical for each
distributed volume group across all cluster nodes.
/usr/sap/<SID> should not be added to a package, since using this as a
dynamic mount point would prohibit access to the instance directories of
locally installed additional SAP application servers. The
/usr/sap/<SID> mount point will also be used to store local SAP
executables. This prevents problems with busy mount points during
database package shutdown. Due to the size of the directory content, it
should not be part of the local root file system. The /usr/sap/tmp might
or might not be part of the root file system. This is the working directory
of the operating system collector process saposcol. The size of this
directory will rarely be beyond a few Megabytes.
If you have more than one system, place /usr/sap/put on separate
volume groups created on shared drives. The directory should not be
added to any package. This ensures that they are independent from any
SAP WAS system and you can mount them on any host by hand if
needed.
Table 2-3 System and Environment Specific Volume Groups
Mount
Point
Access
Point
Potential
owning
packages
VG Name
Device
minor
number
/export/sapmnt/<SID> shared
disk and
HA NFS
db<SID>
dbci<SID>
jdb<SID>
jdbjci<SID>
sapnfs
/export/usr/sap/trans
db<SID>
dbci<SID>
sapnfs
/usr/sap/put shared
disk
none