Installation guide

The database directories can also completely reside on GFS. Follow the database file system
setup recommendations from the SAP installation guide. It is recommended to have
physically different mount points for specific directories.
The GFS mounts from shared storage must be added to /etc/fstab so they get mounted at
system boot.
6.3.3.3 NFS Mounted File Systems
The /sapmnt/<SID> file system should resist on a high available NFS to be available to
additional application server outside the cluster.
The transport directory /usr/sap/trans should also be exported via NFS according to the SAP
landscape.
6.3.3.4 Before Starting the SAP Installation
Before installing SAP NetWeaver, mount all the necessary file systems. Be conscious of the
overmount-effect by mounting the hierarchically highest directories first.
6.3.4 Installation with sapinst
When starting the SAP installation tool sapinst, specify the virtual host name.
sapinst SAPINST_USE_HOSTNAME=<virtual hostname>
For each SAP and database instance installed, choose the installation option "High-
Availability System" as it is described in the SAP installation guide.
6.3.5 lnstallation Post-Processing
6.3.5.1 Users, Groups and Home Directories
By using shared root, users and groups on the second node already exist.
Depending on the Installation Master CD that was used for the SAP installation, the login
profiles for the SAP administrator user (<sid>adm) and the database administrator user might
be different. In older and non-HA installations the user login profiles look similar to this one:
.sapenv_hostname.csh
Using the host name in the user login profiles is a problem in a highly available environment.
By default the profiles .login, .profile and .cshrc will search for two types of user login profiles:
first for the one including the local host name (e.g., .dbenv_hostname.csh) and then for a
version without the host name included. Later versions of the InstMaster CDs will install both
versions of the user login profiles. This could lead to some confusion for the administrator,
with regard to which version is used in which case. Removing all user login profiles (that
include a host name in the file name) is recommended. Do this for both the SAP
administrator, <sid>adm, as well as the database administrator user.
38 | www.redhat.com