Managing HP Serviceguard Extension for SAP for Linux, December 2013

4.7.1 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 13 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.

4.7.2 Option 2: Non-MaxDB environments

Cluster layout constraints:

• MaxDB or additional liveCache must not be running on cluster nodes. Especially, the SCM

System RDBMS must be based on Oracle, DB2, 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

way to deal with this is to make the client libraries available throughout the cluster via AUTOFS

cross-mounts from a dedicated NFS package.

Table 14 File system layout for liveCache in a non-MaxDB environment (Option 2)

Owning packagesStorage typeMount point

Dedicated liveCache package

(lc<LCSID>)

Shared disk/sapdb/data

/sapdb/<LCSID>/sapdata<n>

/sapdb/<LCSID>/saplog<n>

/var/spool/sql

sapnfs

Autofs shared/sapdb/programs

/sapdb/clients

This can be any standard, standalone NFS package. The SAP global transport directory must

already be configured in a similar package. This explains why this package is often referred to

as "the trans package" in related literature. A package serving SAP trans directory can optionally

be extended to also serve the global liveCache file shares.

48 SAP Netweaver cluster storage layout planning