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

directories are shared between the instances and must be part of an instance package. Otherwise
the halt of one instance would prevent the other one to be started or run.
Sybase ASE storage considerations
SGeSAP supports failover of Sybase ASE databases as part of SGeSAP NFS cluster option 1. It is
possible to consolidate SAP instances in SGeSAP ASE environments.
Table 11 File system layout for Sybase ASE clusters
VG TypeOwning PackageAccess PointMount Point
DB specificDB only or combined DB and
CI package
Shared disk/sybase/<DBSID>
sybase/<DBSID>/sapdiag
sybase/<DBSID>/sybsystem
sybase/<DBSID>/sybtemp
sybase/<DBSID>/sapdata<n>
sybase/<DBSID>/saplog<n>
Special liveCache storage considerations
Depending on the setup of the related Netweaver installation (usually a SCM or CRM application)
there are two additional options to setup liveCache that can be used instead of the approach
described in the MaxDB storage consideration .
Option 1: Simple cluster with separated packages
Cluster layout constraints:
• The liveCache package does not share a failover node with the SCM central instance package.
• There is no MaxDB or additional liveCache running on cluster nodes.
• There is no intention to install additional SCM Application Servers within the cluster.
Table 12 File System Layout for liveCache package running separate from SCM (Option 1)
Owning packagesStorage typeMount point
Dedicated liveCache package
(lc<LCSID>)
Shared disk/sapdb/data
/sapdb/programs
/sapdb/clients
/sapdb/<LCSID>/sapdata<n>
/sapdb/<LCSID>/saplog<n>
/var/spool/sql
In the above layout all relevant files get shared via standard procedures. The setup causes no
administrative overhead for synchronizing local files. SAP default paths are used.
Option 2: Non-MaxDB environments
Cluster layout constraints:
• There is no MaxDB or additional liveCache running on cluster nodes. Especially the SCM
System RDBMS is either based on ORACLE or Sybase, but not on MaxDB.
Often SCM does not rely on MaxDB as underlying database technology. But independent from
that, all Instances of the SCM System still need access to the liveCache client libraries. The best
40 SAP cluster storage layout planning