Managing HP Serviceguard Extension for SAP for Linux, December 2013

4. Mount that file system to /export/sapmnt/DASID (create this directory if it doesn’t exist
yet) and export it via NFS.
5. Mount the exported filesystem to /sapmnt/DASID.
To make this exported filesystem highly available, the same mechanism as for other SAP SIDs can
be used.
1. Add the exported file system together with its volume_group, logical volume, and file system
mountpoints to a NFS toolkit package.
2. Add /sapmnt/DASID to the automount configuration.
3. Mountpoint /export/sapmnt/DASID must be available on all the cluster nodes where the
NFS toolkit package runs. /sapmnt/DASID must be available on all the nodes where the
dialog instances run.
5.2.5.5 Intermediate node sync and verification
For more information about synchronization of the other cluster nodes with the automount
configuration, see “Post SAP installation tasks and final node synchronization (Phase 3a)” (page
66) section.
It is possible to perform intermediate synchronization to test the NFS configuration.
For more information on synchronization with the other cluster nodes, see “NFS and automount
synchronization” (page 71) section.
Verification step(s):
1. Check if the package will start up on each cluster node, where it is configured.
2. Run showmount –e <sapnfs package ip_address> and verify if name resolution
works.
3. Run showmount –e <virtual NFS hostname> on an external system (or a cluster node
currently not running the sapnfs package) and check the exported file systems are shown.
On each NFS client in the cluster check the following:
• Run cd /usr/sap/trans command to check the read access of the NFS server
directories.
• Run touch /sapmnt/C11/abc; rm /sapmnt/C11/abc command to check the
write access.
NOTE:
• For more information on synchronization with the other cluster nodes, see “NFS and
automount synchronization” (page 71) section.
• For information on the final synchronization of the other cluster nodes with the automount
configuration, see “Post SAP installation tasks and final node synchronization (Phase
3a)” (page 66) section.
5.2.6 Infrastructure Setup - SAP base package setup (Phase 1b)
This step will finally make the basic infrastructure available to start the SAP installation afterwards,
which includes the instance and database file systems as well as the IP addresses of the virtual
hostnames used for the installation. While there are other manual ways to provide that basic
infrastructure, setting up a Serviceguard package is the recommended way.
SAP base package setup enables the available basic infrastructure to start the SAP installation.
This includes the instance and database file systems as well as the IP addresses of the virtual
hostnames used for the installation. Setting up a Serviceguard package is another recommended
method to set up the basic infrastructure.
There are two ways to set up the initial SAP base package:
60 Clustering SAP Netweaver using SGeSAP packages