Managing HP Serviceguard Extension for SAP for Linux, December 2013

local copies is possible, though not recommended because there are no administration tools that
keep track of the consistency between the local copies of these files on all the systems.
Using NFS toolkit filesystems underneath or export Table 10 (page 46) is required when multiple
MaxDB based components (including liveCache) are either planned or already installed. These
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.
4.5 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>
/sybase/<DBSID>/saptemp
4.6 IBM DB2 storage considerations
The SGeSAP supports failover of IBM DB2 databases as part of the SGeSAP NFS cluster option
1. It is possible to consolidate the SAP instances in SGeSAP IBM DB2 environments.
Table 12 File system layout for DB2 clusters
VG TypeOwning PackageAccess PointMount Point
DB specificDB only or combined
DB and CI package
Shared disk/db2/db2<dbsid>
/db2/db2<dbsid>/software
/db2/<DBSID>
/db2/<DBSID>
/db2/<DBSID>/log_dir
/db2/<DBSID>/sapdata<n>
/db2/<DBSID>/sapdata/saptemp1
/db2/<DBSID>/db2dump
/db2/<DBSID>/db2<dbsid>
4.7 Special liveCache storage considerations
Depending on the setup of the related Netweaver installation (usually an SCM or CRM application)
there are two additional options for setting up liveCache that can be used instead of the approach
described in the “MaxDB/liveCache storage considerations” (page 44).
4.5 Sybase ASE storage considerations 47