Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

In clustered SAP environments prior to 7.x releases, install local executables. Local executables
help to prevent several causes for package startup or package shutdown hangs due to the
unavailability of the centralized executable directory. Availability of executables delivered with
packaged SAP components is mandatory for proper package operation. Experience has shown
that it is a good practice to create local copies for all files in the central executable directory. This
includes shared libraries delivered by SAP.
To automatically synchronize local copies of the executables, SAP components deliver the sapcpe
mechanism. With every startup of the instance, sapcpe matches new executables stored centrally
with those stored locally.
Directories that reside on shared disks
Volume groups on a SAN shared storage get configured as part of the SGeSAP package.
Instance-specific volume groups are required by only one SAP instance or one database instance.
They usually get included with exactly the package that is set up for this instance. In this configuration
option, the instance-specific volume groups are included in the package.
System-specific volume groups get accessed from all instances that belong to a particular SAP
System. Environment-specific volume groups get accessed from all instances that belong to any
SAP System installed in the whole SAP scenario. System and environment-specific volume groups
must be set up using NFS toolkit to provide access capabilities to SAP instances on nodes outside
of the cluster. The cross-mounting concept of option 1 is not required.
A valuable naming convention for most of these shared volume groups is vg<INSTNAME><SID>
or vg<INSTNAME><INR><SID>. Table 6 (page 35) provides an overview of SAP shared storage
for this special setup and maps them to the component and package type for which they occur.
Table 6 File systems for the SGeSAP package in NFS idle standby clusters
RemarksAccess PointMount Point
RequiredShared disk and NFS toolkit/sapmnt/<SID>
Shared disk/usr/sap/<SID>
OptionalShared disk and NFS toolkit/usr/sap/trans
If you have more than one system, place /usr/sap/put on separate volume groups created on
shared drives. The directory must 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.
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. Due to its similiarity to
MaxDB this section also contains liveCache storage considerations, although it cannot be considered
as a dataset instance being part of a Netweaver installation. All supported platforms are Intel
x86_64 only:
• Oracle Single Instance RDBMS Storage Consideration
• MaxDB/liveCache Storage Considerations
• Sybase ASE Storage Considerations
• Special liveCache Storage Considerations
Database instance storage considerations 35