Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

Infrastructure setup, pre-installation preparation (Phase 1)
This section describes the infrastructure that is provided with the setup of a NFS toolkit package
and a base package for the upcoming SAP Netweaver installation. It also describes the prerequisites
and some selected verification steps.
There is a one to one or one to many relationship between a Serviceguard package and SAP
instances and a one to one relationship between a Serviceguard package and a SAP database.
A package can only serve a maximum of one SAP SID and one DB SID at a time, but SAP SID and
DB SID are not required to be identical.
Common resources on which SAP instances depend must go into a single package and (unless
Serviceguard package dependencies are going to be used) instances depending on these resources
must be configured into the same package later.
Prerequisites
• Volume groups, logical volumes, and file system (with their appropriate sizes) must be setup
according to the storage layout described in Chapter 4“SAP cluster storage layout planning”
(page 30).
• Volume groups must be accessible from all cluster nodes.
• The file system mount points must be created on all the cluster nodes.
• Virtual hostnames (and their IP addresses) required for the SAP installation must exist and must
resolve on all the cluster nodes. Virtual hostnames are mandatory for the NFS toolkit package
setup. If no NFS toolkit setup is used, continue to Infrastructure Setup - SAP base package
setup (Phase 1b).
After completing the steps in this section everything is ready for starting the SAP installation. This
infrastructure consists of:
• A running sapnfs package exporting the relevant file systems (it depends upon the setup
chosen, as NFS may also be part of a SGeSAP package instead of a separate NFS toolkit
package).
• A working automount configuration on all the hosts that will run the SAP instance.
• One or more SGeSAP “base packages” providing the environment for the subsequent SAP
installation.
Node preparation and synchronization
Node preparation needs to be performed on every cluster node only once. If a node is added to
the cluster after the SGeSAP package setup, node preparation must be performed before the
packages are enabled on that node.
NOTE: It is critical for any of the following configuration and installation setup steps of phase1
that the prerequisites (setup of volume groups, logical volumes, file systems, mount points, and
virtual hostnames) must be implemented and synchronized on all the nodes before continuing the
configuration or installation.
Generally speaking synchronization refers that the secondary nodes in the cluster must be
coordinated with the configuration changes from the primary node.
For example, configuration file changes in the cluster are copied from one source location (primary)
to one or more target locations (secondary).
Synchronization in phase 1 is intermediate as the goal here is to identify and isolate configuration
issues at an early stage.
Phase 3 contains the final synchronization steps. For more information on final synchronization,
see “Post SAP installation tasks and final node synchronization (Phase 3a)” (page 59) section.
Infrastructure setup, pre-installation preparation (Phase 1) 47