Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Linux Configuration
Chapter 2 43
Directory Structure Configuration
The main purpose of this section is to ensure the proper LVM layout and
the right distribution of the different filesystems 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.
IS010 Installation Step:
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 the LVM layout for Clustered SAP Environments”. 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.
The volume groups can be made up of multiple devices of the MD
subsystem in case MD will be used to achieve multipathing.
Alternatively any supported multipathing feature of the fiber channel
PCI card drivers can be utilized.
IS020 Installation Step:
Make sure the volume groups get distributed to all nodes.
For more detailed information on this step, refer to Managing
Serviceguard for Linux user’s guide.
IS030 Installation Step:
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 filesystem column.
# It will be refered to as <dev_path> later.
find . -depth -print|cpio -pd /usr/sap/<SID>.new
cd /
umount /usr/sap/<SID>