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

If legacy-style HA NFS functionality is intended to be integrated into a legacy-style SGeSAP
package, copy the HA NFS toolkit scripts into the package directory.
Since the SGeSAP package directory can have entries for both, a database and a Central Instance
package, it is required to add a package type suffix to the NFS toolkit files during the copy
operation. Otherwise, all packages of the package directory would act as NFS server. This is
usually not intended. In standard setups, only the combined DBCI package or the dedicated
SAPNFS package or the DB package needs NFS server functionality.
In a package directory, only one package of any of these package types should exist. Renaming
is mandatory when using multiple package types. The monitoring script nfs.mon does not need
to be renamed.
The following is an example of copy operations, whereas <pkg_type> can be db, dbci or
sapnfs:
cp /opt/cmcluster/nfs/hanfs.sh etc/cmcluster/<SID>/hanfs.<pkg_type>
In the package control script <pkg_type>.control.script, specify:
HA_NFS_SCRIPT_EXTENSION=<pkg_type>
This will allow only the package control script of the <pkg_type>.control.script to execute
the HA NFS script.
Installation Step: LS540
The following steps will customize the hanfs.<pkg_type> scripts. It will customize all
required directories for the usage of the HA-NFS.
All directories that are handled by the automounter must be exported by the scripts if they are
part of the packages. Exported directories can usually be found beneath the special export
directory /export for storage option 1 of chapter 2. There are no cross-mounts via /export
required for option 2.
Example for option 1:
/export/sapmnt/<SID>
/export/usr/sap/trans
Example for option 2:
/sapmnt/<SID>
/usr/sap/trans
Exported directories can usually be found beneath the special export directory /export. The
directories to be exported are specified including their export options, using the XFS[*] array
of the hanfs.<pkg_type> script out of legacy-style HA-NFS toolkit package. This script is
called within the runtime by the standard Serviceguard control script. In modular-style packages,
specify the parameter nfs/hanfs_export/XFS instead.
The transport directory is also part of the package in standard installations. In those cases it also
has to be mentioned here.
Only allow access from machines inside of the cluster that are configured as backup hosts and
additional application servers of this specific SAP system. Make sure to allow access for all
addresses that the servers use so they can reach the directories. Allowing the right addresses is
essential if your hosts use more than one LAN card.
Example of an hanfs.db file using cross-mounts with storage layout option 1:
Legacy Style:
XFS[0]="-o root=node1:node2:node3:trans:db:sap /export/usr/sap/trans"
XFS[1]="-o root=node1:node2:node3:trans:db:sap /export/sapmnt/<SID>"
Modular Style:
nfs/hanfs_export/XFS "-o root=node1:node2:node3:trans:db:sap /export/usr/sap/trans"
nfs/hanfs_export/XFS "-o root=node1:node2:node3:trans:db:sap /export/sapmnt/<SID>"
Installation Step: LS550
94 Step-by-Step Cluster Conversion