Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Hot standby systems have a preferred default machine for the instance with the master role. This
should usually correspond to the hostname of the primary node of the package. The hostname of
the failover node defines the default secondary role, i.e. the default standby and alternative master
machine. For a hot standby system to become activated, the LC_PRIMARY_ROLE and the
LC_SECONDARY_ROLE need to be defined with physical hostnames. No virtual addresses can
be used here.
LC_PRIMARY_ROLE=<primary_node>
LC_SECONDARY_ROLE=<secondary_node>
A hot standby initialization during startup might require hardware-based copy mechanisms of the
underlying storage array. Currently HP StorageWorks XP arrays with BCV volumes are supported.
The following parameter needs to be set:
LC_COPY_MECHANISM=BUSINESSCOPY
Optional hot standby Installation Step: LC197
A hot standby initialization procedure can perform a plausibility check of its storage configuration .
A hot standby initialization procedure can perform a plausibility check of its storage configuration.
Presaved world-wide IDs of LUNs are compared with current world-wide IDs to prevent that outdated
configuration information is used for cloning. This adds to the robustness of the initialization process,
but for large implementations it significantly slows down the standby startup. By setting:
AVOID_WWID_CHECK=1
in sap.config the check can be turned off.
Optional hot standby Installation Step: LC198
The hot standby liveCache instance does not detect a regular liveCache master shutdown .
It will not reconnect to the restarted liveCache master. The sap.config parameter
LC_STANDBY_RESTART=1
will (re)start a remote hot standby system after the master liveCache instance package is started.
Optional hot standby Installation Step: LC200
You can optionally handle SAP ABAP Application Servers with a liveCache package .
Refer to chapter 3—“SGeSAP Configuration” to get more information on the usage of the parameters
ASSID, ASHOST, ASNAME, ASNR, ASTREAT and ASPLATFORM
liveCache Installation Step: LC205
Distribute the content of /etc/cmcluster/<LCSID> to all cluster nodes on which the liveCache
should be able to run .
liveCache Installation Step: LC210
Log in on the primary node that has the shared logical volumes mounted.
Create a symbolic link that acts as a hook that informs SAP software where to find the liveCache
monitoring software to allow the prescribed interaction with it. Optionally, you can change the
ownership of the link to sdb:sdba.
ln -s /etc/cmcluster/<LCSID>/saplc.mon /sapdb/<LCSID>/db/sap/lccluster
liveCache Installation Step: LC215
For the following steps the SAPGUI is required. Logon to the APO central instance as user SAP*.
Start transaction /nlc10 and enter LCA for the logical connection.
/nlc10 -> Logical connection -> LCA -> liveCache -> Create/Change/Delete Connection
Change liveCache server name to the virtual IP name for the liveCache and save it.
Change the liveCache instance name to <LCSID>. Redo the above steps for LDA.
132 SAP Supply Chain Management