Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Integrate all SAP related CFS disk groups and file systems. The package dependencies to the system
multi-node package get created automatically. The mount points need to be created manually on
all alternate nodes first.
Here is an example for a disk group that was created with the following command sequence:
vxdg -s init dgC11 /dev/rdsk/c4t0d4
vxdg -g dgC11 set activation=sw
vxassist -g dgC11 make /dev/vx/rdsk/dgC11/cfs01 newfs -F vxfs \
/dev/vx/rdsk/dgC11/cfs01
To put the disk group into the Serviceguard cluster, use the following command sequence:
cfscluster config
cfscluster start
cfsdgadm add dgC11 all=sw
cfsmntadm add dgC11 cfs01 /usr/sap/<SID> all=rw
After these conversions, it should be possible to start the SAP System manually. If the installation
was done using virtual IPs, then the additional packages defined in that step need to be started
after starting the CFS packages, but prior to the SAP manual start.
Non-CFS Directory Structure Conversion
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. This section does not need to be consulted
when using the HP Serviceguard Storage Management Suite with CFS and shared access Option
3.
Logon as root to the system where the SAP Central Instance is installed (primary host). If the database
is installed on a different host, also open a shell as root on the database machine. Stop the SAP
Application Server and the database if they are not already.
Installation Step: IS010
The device minor numbers of the shared volume groups must be the same on all cluster hosts and
must not be in use on any of the cluster hosts .
To keep track of that, record all the minor numbers already in use on the cluster hosts. See
Table 15 (page 59).
To find these minor device numbers on each cluster hosts, type:
ll /dev/vg*/group|cut -c 44-45
Table 15 Hosts and Device Minor Numbers
device minor numbershostname
Installation Step: IS020
Verify that the existing volume group layout is compliant with the needs of the Serviceguard
package(s) as specified in the tables of chapter 2 .
1. Make sure that database specific file systems and Central Instance and/or System Central
Services specific file systems are separated onto different volume groups. 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.
A default mount point for SAP applications is /usr/sap/<SID>. For Serviceguard, change
this to /usr/sap/<SID>/<INSTNAME><INR>. If /usr/sap/<SID> is the mount point,
move some files to a local logical volume, and then change the mount point.
Example for a SAP Central Instance:
HP-UX Configuration 59