Add all relocatable IP address information to /etc/hosts. Remember to add the heartbeat IP addresses.

liveCache Installation Step: LC120

If you use DNS:

Configure /etc/nsswitch.conf to avoid problems. For example:

hosts: files[NOTFOUND=continue UNAVAIL=continue \

TRYAGAIN=continue]dns

HP-UX Setup for Option 4

This section describes how to install a hot standby instance on the secondary node.

hot standby Installation Step: LC143

The hot standby instance of storage option 4 can be installed with the installer routine that comes on the SAP liveCache media.

There is no special option for a hot standby provided by SAP yet, but installation is very straight-forward. "Install" or "patch" the master instance on the standby host. This creates local copies of all required directories, users, services and files. log files and data files should not be defined in this step.

hot standby Installation Step: LC145

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

HP-UX Setup for Option 4 101

Page 101
Image 101
HP Serviceguard Extension for SAP (SGeSAP) manual HP-UX Setup for Option, If you use DNS, HORCCMRCF=1 HORCMINST=0