Install LifeKeeper

On both the Primary and the Backup servers, LifeKeeper software will now be installed including the following recovery kits:

• SAP

• appropriate database (i.e. Oracle, SAP MaxDB)

• IP

• NAS (required when data is hosted by an NFS server)

• Quorum (steeleye-lkQWK package) if using network shared devices

1. Stop Oracle Listener and SAP on both machines.

For Example, if the Oracle user is orastc, the Oracle listener is LISTENER_STC, and the SAP user is stcadm:

a. su to user orastc and run command lsnrctl stop LISTENER_STC

b. su to user stcadm and run command stopsap sap{No.}

c. From root user, make sure there are no SAP or Oracle user processes; if there are, enter “killall sapstartsrv”; even after this command, if there are processes, run “ps –ef” and kill each process

2. Go into /etc/hosts on both machines and ensure that host and/or DNS entries are properly specified.

3. Stop and remove the IP addresses from the current interfaces. Note: This step is required before the IP addresses can be protected by the LifeKeeper IP Recovery Kit.

ip addr delete {A/SCS VIRTUAL IP ADDRESS}/{NETMASK} dev eth0

ip addr delete {ERSv2 VIRTUAL IP ADDRESS}/{NETMASK} dev eth0

4. Verify the IP addresses have been removed by performing a connection attempt, for example using ping.

5. Following the steps in the LifeKeeper Installation Guide, install LifeKeeper on both the Primary server and the Backup server (DE, core, DataKeeper, LVM as well as the licenses). When prompted to select Recovery Kits, make sure you select the following:

SAP, appropriate database (i.e. Oracle), IP and NAS (if required)

The installation script does certain checking and might fail if the environment is not set up correctly as shown in this example:

SAP Services file /usr/sap/sapservices not found

SAP Installation is not valid; please check environment and retry

error: %pre(steeleye-lkSAP-7.3.1-1.noarch) scriptlet failed, exit status 2

error: install: %pre scriptlet failed (2), skipping steeleye-lkSAP-7.3.1-1

In the above example, the expected SAP file, /usr/sap/sapservices, is missing. It is very important for the environment to be in the right state before installation can continue.

Refer to the Recovery Kit Documentation for additional information about installing the recovery kits and configuring the servers for protecting resources.

6. Setup LifeKeeper Communication Paths between all servers.

7. Setup Quorum when using network shared devices (Quorum-Witness).
   In this example quorum is configured in “Majority Mode” with the following settings in /etc/default/LifeKeeper on each server:

QUORUM_MODE=majority

WITNESS_MODE=remote_verify