Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Linux Configuration
Chapter 3 129
IS394 Installation Step:
Edit the automounter file/etc/auto.import, the indirect automounter
map file. In this file, all NFS client mounted directories will now be
configured to be accessed / mounted via the /import directory. This action
consists of several steps that belong together.
The idea behind the action to be performed here is that each path below
/export should be automounted into a placeholder directory that is
below /import.
NOTE There is NOT a straight relationship between the pathname below
/export and the pathname below /import (e.g:
/etc/export/usr/sap/trans gets mapped to /import/trans and NOT
/import/usr/sap/trans).
Refer to the section “Planning the LVM layout for Clustered SAP
Environments” to find out which file systems and their specified path
have to configured for the automounter.
For each directory that has a specified path that shows that it will be
mounted below /export, the following steps are necessary:
1. Unmount any file systems that will be part of the automounter
configuration. Make sure that these file systems are also commented
out of /etc/fstab on all cluster nodes. Some typical automount file
systems in an SAP environment are:
SAP instance:
umount /usr/sap/trans
umount /sapmnt/<SID>
MaxDB instance:
umount /sapdb/programs
umount /sapdb/data
umount /var/spool/sql/ini
2. Create new directories directly below /import. It should be possible
to use the last directory name of the specified path as new directory
name. The “last directory name” will be used by the automounter as
the key for mapping the mount points request onto a directory in
/import. Example file entries: