Serviceguard Extension for SAP Release Notes Version B.05.10, December 2012

The native SAP software configuration settings of the instances that belong to the selected SAP
System ID get discovered from the cluster nodes and serve as input for Serviceguard package
parameter settings that populate package configuration files.
There are two options: the SGeSAP Multiple packages easy deployment scenario and the SGeSAP
Combined Packages easy deployment scenario.
The Multiple packages is the default and recommended option that allows you to distribute the
non-redundant SAP components across multiple, separate packages to avoid dependencies between
SAP components. This option must be selected if each non-redundant SAP component has exclusive
resources available (for example, volume groups, virtual hostnames, and IP addresses). For
previously unclustered SAP systems, this option creates a configuration that follows SAP
recommended HA settings.
The Combined Packages option allows you to combine the non-redundant SAP components of a
SAP system into very few packages, to keep the setup simple and save resources. In this option a
package can failover if any of the SAP component fails when multiple components are configured
in the same package.
Both SGeSAP easy deployment scenarios override their default behavior if they detect existing
packages that already include a relocatable IP that matches the virtual IP on which a software
instance is configured. In this case, the existing package configuration is extended by the software
instance instead of creating a new package configuration. This mechanism can be used in particular
to streamline the cluster creation for SAP new installs. For SAP installations on a virtual IP, the virtual
IP address must be configured on a network before SAP installation. The best way to achieve this,
is to create a simple Serviceguard package for this virtual IP and start it before SAP instance
installation. After SAP installation, the cluster setup can be completed in a quick and convenient
way with SGeSAP easy deployment.
HA NFS configurations are provided for the filesystems /sapmnt/<SID>/… and /usr/sap/trans
if they are shared or set up via automounter below /export/... The set of package configuration
files may be successfully applied if the SAP and cluster configuration were in place before
deployment.
The created package configurations can be reviewed and changed before applying them by
directly editing the package configuration files in the HP Serviceguard Manager.
Guided configuration and administration of SGeSAP modular packages through HP
Serviceguard Manager
• SGeSAP B.05.10 modular package creation and subsequent package configuration changes
can now be done in a set of , guided steps via the HP Serviceguard Manager . The feature
provides a sequence of interactive steps, while the easy package method discussed above is
fully automated. All SGeSAP features are covered in the guided dialog, but only one package
can be handled at a time.
• A discovery routine detects SAP software instances that are installed on any cluster node. The
native SAP software configuration settings are derived from those nodes and serve as input
for Serviceguard package parameter configurations. SAP Netweaver instances can be
discovered this way, as well as their underlying database instances and the SAP liveCache.
The administrator can select from the list of discovered instances or manually specify instances
that are to be clustered.
• After defining a subset of the discovered SAP software instances for clustering, the remaining
package parameter settings are preset based on the discovered software configurations. This
includes generic Serviceguard package parameter settings like cluster volume groups, file
systems, mountpoints and virtual IP addresses that are in use by the SAP software, as well as
all SGeSAP specific package parameters. SGeSAP service monitors and package resources
for ongoing health monitoring of the components in the package are suggested for inclusion
in the package.
6 Serviceguard Extension for SAP Version B.05.10 Release Notes