Installation guide

Attribute Description Required
reference
mountpoint Path within file system hierarchy at which to
mount this file system.
Yes
device Block device, file system label, or UUID of file
system.
Yes
fstype File system type. If not specified, mount(8) will
attempt to determine the file system type.
No
force_unmount If set, the cluster will kill all processes using
this file system when the resource group is
stopped. Otherwise, the unmount will fail, and
the resource group will be restarted.
No
options Provides a list of mount options. If none are
specified, the NFS file system is mounted -o
sync.
No
self_fence If set and unmounting the file system fails, the
node will immediately reboot. Generally, this is
used in conjunction with force_unmount
support, but it is not required.
No
force_fsck If set, the file system will be verified (even if it
is a journaled file system). This option is
ignored for non-journaled file systems such as
ext2.
No
7.4.4 SAPInstance
Within SAP instances there can be several services. Typically, one will find the defined
services in the START profile of the related instance (Note: with SAP Release 7.10, the
START profile content was moved to the instance profile). Not all of those services are worth
monitoring by the cluster. For instance, failover of the SAP instance would not be preferred if
the central syslog collector daemon failed.
Services monitored by the SAPInstance resource agent:
 disp+work
 msg_server
 enserver
 enrepserver
 jcontrol
 jstart
The reserve conclusion of this is that a SAP instance without any of these services will not
work with the resource agent. One could think of a standalone gateway instance or a
44 | www.redhat.com