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

a machine different from this, the database vendor dependent steps have to be done on the host on
which the database was installed.
2. Cluster Node Synchronization - This section consists of steps performed on the backup nodes. This
ensures that the primary node and the backup nodes have a similar environment.
3. NOTE: Repeat the above steps for each node of the cluster that is different from the primary host.
4. Cluster Node Configuration - This section consists of steps performed on all the cluster nodes, regardless
if the node is a primary node or a backup node.
5. NOTE: Repeat the above steps for each node of the cluster including the primary host.
6. External Application Server Host Configuration - This section consists of steps performed on any host
outside of the cluster that runs another instance of the SAP component.
NOTE: Repeat the above steps for each host that has an external application server installed.
Performing some of the iterations in parallel is fine, just use caution in any complex setup situation.
Directory Structure Configuration
NOTE: The steps in this section are only performed once on the primary host.
The main purpose of this section is to ensure the proper LVM layout and the right distribution of the different
file systems that reside on shared disks.
Logon as root to the system where the SAP Central Instance is installed. If the database is installed on a
different host, also open a shell as root on the database machine.
Installation Step: IS009
All SAP Instances ( CI , SCS , ASCS , D ,...) must have instance numbers that are unique for the whole cluster.
For a clustered instance with instance number <INSTNR>execute the command:
ls -d /usr/sap/???/*<INSTNR>
It should not reply any match on all nodes. Otherwise refer to the SAP documentation how to change instance
IDs for the relevant instance type. It might be simpler to reinstall one of the conflicting instances.
Installation Step: IS010
Make sure that the volume group layout is compliant with the needs of the Serviceguard package(s) as
specified in the tables of Section "Planning a File System Layout for SAP in a Serviceguard/LX Cluster
Environment."
All directories that are labeled shared in these tables need to reside on logical volumes on a shared external
storage system. The recommended separation in different volume groups can also be taken from these tables.
Installation Step: IS030
Comment out the references to any file system that classified as a SHARED in Chapter 2 of this manual from
the /etc/fstab .
Installation Step: IS031
If /usr/sap/<SID> is a mountpoint that contains the Central Instance directory DVEBMGS<INSTNR> , you
have to move some files to a local logical volume and change the mountpoint.
For example:
mkdir /usr/sap/<SID>.new
cd /usr/sap/<SID>
df .
# Remember the file system column.
# It will be referred to as <dev_path> later.
find . -depth -print|cpio -pd
64 Step-by-Step Cluster Conversion