Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

Cluster Node Synchronization
NOTE: Repeat the steps in this section for each node of the cluster that is different than the primary host.
Logon as root to the system where the SAP Central Instance is installed (primary host) and prepare a logon
for each of its backup hosts - if not already available.
Installation Step: IS070
Open the groupfile file, /etc/group, on the primary side.
If any of the SAP and Database groups listed here (sapsys, dba, oper , sdba) exist on the primary node
and they do not exist on the backup node, copy them from the primary node to the backup node. If any
group exists, verify that it has the same GID on both the primary and backup nodes. Merge the group
members lists.
Installation Step: IS080
Open the password file, /etc/passwd , on the primary side.
If any of the SAP and database users listed here (<sid>adm, ora<sid>, sqd<sid>, sdb...) exist on the
primary node, recreate them on the backup node. Assign the users on the backup nodes the same user and
group ID as the primary nodes.
Installation Step: IS090
Look at the service file, /etc/services , on the primary side.
Replicate all SAP services listed here (sapdp<INR>, sapdb<INR>s, sapms<SID>, sapgw<INR>,
sapgw<INR>s, orasrv, tlissrv sql16...) on the Primary Node that exist on the primary node onto
the backup node.
Installation Step: IS100
Change the Linux kernel on the backup node to meet the SAP requirements. The entries on the primary node
may act as a reference.
Make sure the appropriate saplocales rpm packages are installed on all nodes of the cluster. Kernel
parameters are set in file /etc/sysctl.conf
Install all Linux kernel patches that are recommended for Serviceguard and patches recommended for SAP
R/3.
Installation Step: IS110
If the primary node has the Central Instance installed: Copy the <sid>adm home directory to the backup
node(s).
This is a local directory on each node. Default home directory path is /home/<sid>adm.
Installation Step: IS120
On the second node, in the <sid>adm home directory the start, stop and environment scripts need to be
renamed.
If some of the scripts listed in the following do not exist (For certain releases, such as SAP 6.x or higher),
these steps can be skipped.
su - <sid>adm
mv startsap_<primary>_<INR> startsap_<secondary>_<INR>
mv stopsap_<primary> <INR> stopsap_<secondary>_<INR>
mv .sapenv_<primary>.csh .sapenv_<secondary>.csh
mv .sapenv_<primary>.sh .sapenv_<secondary>.sh
mv .dbenv_<primary>.csh .dbenv_<secondary>.csh
mv .dbenv_<primary>.sh .dbenv_<secondary>.sh
mv .sapsrc_<primary>.csh .sapsrc_<secondary>.csh
mv .sapsrc_<primary>.sh .sapsrc_<secondary>.sh
mv .dbsrc_<primary>.csh .dbsrc_<secondary>.csh
mv .dbsrc_<primary>.sh .dbsrc_<secondary>.sh
Linux Configuration 67