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

In this step, the correct storage layout to support the hardware based copy mechanisms for the
devspaces of the data files gets created .
On the Storageworks XP array pvol/svol pairs should be defined for all LUNs containing
DISKDnnnn information of the master. These LUNs should be used for devspace data exclusively.
Make sure that all pairs are split into SMPL (simple) state.
NOTE: A hot standby configuration requires the BCV copy mechanism to be preconfigured, but
LUNs will not be in synchronization mode during normal operation.
hot standby Installation Step: LC147
Manually create the same LVM volume group layout for the data files on the secondary node as is
in place on the primary .
Create temporary volume groups, logical volumes, filesystems and mountpoints by using the master
instance as a reference. Instead of using the same LUNs as the master, use the corresponding
svols that are in SMPL state. These svol LUNs will be synchronized later to become populated
with a copy of the master data. The hot standby instance will take the LVM volume group layout
created here as a reference on how to recreate its storage structure during startup.
hot standby Installation Step: LC149
The liveCache instances require full administration control to handle their storage configuration .
There is a special callback binary on the primary and secondary node that acts as a gateway to
these functions. The ownership and permissions of this binary need to be manually changed on
both nodes to have the root user confirm this step:
chmod 4750 /opt/cmcluster/sap/bin/hsscb
chown root:sdba /opt/cmcluster/sap/bin/hsscb
hot standby Installation Step: LC152
Add /opt/cmcluster/sap/lib/hpux64 to the root and <LCSID>adm SHLIB_PATH
environment variables on both nodes .
hot standby Installation Step: LC155
The XP Raidmanager needs to be installed and configured correctly on both nodes .
Unless defined differently in the root user environment, SGeSAP will default to the following settings:
HORCC_MRCF=1
HORCMINST=0
HORCM_CONF=/HORCM/etc/horcm0.conf
The Raidmanager binaries need to accessible via the PATH of root. Two HORCM instances can
be configured on each node
hot standby Installation Step: LC157
The activation of the hot standby happens on the master instance .
Logon to the instance via dbmcli and issue the following commands:
hss_enable node=<LCRELOC>
lib= /opt/cmcluster/sap/lib/hpux64/librtehssgesap.so
hss_addstandby <secondary_hostname> login=<osusr>,<pwd>
Alternatively, you can use the configuration dialog of the Hot Standby button in the SAP Database
Manager configuration to set these values. see Figure 4-2.
HP-UX Setup for Option 4 127