You are here: Installation > Plan Your Configuration

Plan Your Configuration

  1. Determine which configuration you wish to use. The required tasks vary depending on the configuration.

  2. Determine whether the SAP system-wide /usr/sap/trans directory will be hosted on the SAP Primary Application Server or on a file server. It can be hosted either place as long as it is NFS shared and fully accessible. If it is hosted on the SAP Primary Application Server and located on a shared file system, it should be protected by LifeKeeper and included in the SAP hierarchy.
  3. Consider the storage requirements for SAP and DB as listed in the SAP Installation Guide. Most of the SAP files will have to be installed on shared storage. Consult the LifeKeeper for Linux Technical Documentation for the database-specific recovery kit for information on which database files are installed on shared storage and which are installed locally. Note that in an SAP environment, SAP requires local access to the database binaries, so they will have to be installed locally. Determine how to best use your shared storage to meet these requirements.

Also note that when shared storage resources are under LifeKeeper protection, they can only be accessed by one server at a time. If the shared device is a disk array, an entire LUN is protected. If a shared device is a disk, then the entire disk is protected. All file systems located on a single volume will therefore be controlled by LifeKeeper together. This means that you must have at least two logical volumes (LUNs), one for the database and one for SAP. 

  1. Virtual host names will be needed in order to identify your systems for failover. A new IP address is required for each virtual host name used. Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup, then proceed as follows:

  1. Create the new virtual ip addresses by using the command:

ifconfig eth0:1 {IPADDRESS} netmask {255.255.252.0} (use the right netmask for your configuration)

Note: To verify these new virtual ip addresses, either the ifconfig or ip addr show command can be used if using LifeKeeper 7.3 or earlier. However, starting with LifeKeeper 7.4, the ip addr show command should be used.

  1. Repeat with eth0:2 for the database virtual IP.

In order to associate the switchable IP addresses with the virtual server name, edit /etc/hosts and add the new virtual ip addresses.

Note: This step is optional if the Primary Application Server and the Database are always running on the same server and communication between them is always local. But it is advisable to have separate switchable IP addresses and virtual server names for the Primary Application Server and the Database in case you ever want to run them on different servers.

  1. Stop the caching daemon on both machines.

rcnscd stop

  1. Mount the software.

mount //{path of software} (no password needed)

  1. Run an X session (either an ssh -X or a VNC session -- for Microsoft Windows users, Hummingbird Exceed X Windows can be used).

Note: When sapinst is run, the directory will be extracted under /tmp

Important Note

The LifeKeeper SAP Recovery Kit relies on the SAP Host agent being installed. If this software is not installed, then the LifeKeeper SAP kit will not install. With SAP Netweaver Version 7.3, this host agent is supplied; however, prior versions require a download from SAP. It is recommended that you consult your SAP help notes for your specific version. You can also refer to the Help Forum (help.sap.com) for further documentation.

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.