Managing Serviceguard Extension for SAP Version B.05.10, September 2010

NOTE: Repeat the cluster node synchronization steps for each node of the cluster that is
different than the primary.
• 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.
NOTE: Repeat the cluster node configuration steps for each node of the cluster.
• External Application Server Host Configuration—this section consists of steps performed
on any host outside of the cluster that runs another ABAP instance of the SAP system.
NOTE: Repeat this section for each host that has an external application server installed
Performing some of the iterations in parallel is acceptable. Use caution in any complex setup
situation.
Rather than using the cut and paste mechanism, you can fill out the tables provided by first
analyzing the primary host(s). Afterwards, you can use the tables to synchronize all nodes.
Directory Structure Configuration
This section adds implementation practices to the architectural decisions made in the
chapter—"Storage Layout Considerations." If layout option 1 or option 2 is used, then the non-CFS
directory structure conversion must be performed. An implementation based on HP LVM is
described in this document. VxVM can similarly be used. Option 3 maps to the CFS configuration
for SAP. In this case, usage of VxVM and CVM are mandatory.
Cluster Filesystem Configuration
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. Make sure that all SAP
instances and the database were stopped manually.
NOTE: These steps are only required if HP Serviceguard Cluster File System is used for the
SAP instances.
Installation Step: IS009
Verify that the existing disk group layout is compliant with the needs of the Serviceguard
package(s) as specified in the tables for option 3 of chapter 2.
All directories that are labeled shared in these tables need to reside on logical volumes on a
shared external storage system. The volume management needs to be VxVM based. The volumes
can be converted using vxvmconvert(1m), if the SAP System was originally installed on HP
LVM volumes instead.
All SAP Instances (CI, SCS, ASCS, D,...) must have instance numbers that are unique for the
whole cluster. Exceptions are (A)REP instances that follow an old naming convention of sharing
the instance ID with their corresponding (A)SCS instance. This naming convention should no
longer be used, since it cannot be combined with the SAP startup framework. For a clustered
instance with instance number <INSTNR>, execute the command:
ls -d /usr/sap/???/*<INSTNR>
It should not reply any match on any node. 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: IS030
50 Step-by-Step Cluster Conversion