Serviceguard Extension for SAP Version B.06.00.20 Release Notes for Linux, March 2014

The dbinstance module clusters the single-instance database of a Netweaver stack combining
the uniform SAP database handling and a fallback to database-technology native operations.
Supported database technologies include SAP Sybase, SAP MaxDB, and Oracle RDBMS.
The sapextinstance module allows triggering best-effort start and stop operations for non-clustered
SAP instances as part of regular package operations. These additional instances can belong to
the same System ID as the instances in the package or any other SAP system IDs. They can run on
cluster nodes or cluster-external servers. This functionality can for example be used to move SAP
Diagnostic Agents with their instances. An issue during relocation of the Diagnostic Agents would
not prevent proper relocation of the mission-critical instances.
The livecache module provides instance failover capabilities to SAP livecache instances. The
sapinfra module complements the SAP instance clustering with capabilities to cluster SAP
infrastructure software that does not become installed as part of a formal instance, including
saprouter, sapccmsr, and webdispatcher.
HP SGeSAP/LX modular package configuration files are created using cmmakepkg(1) command.
HP SGeSAP/LX modular package configuration changes can be verified using the
cmcheckconf(1) command before they become effective. HP SGeSAP/LX detects erroneous
SAP package configurations and prevents that they get applied with cmapplyconf(1). All SAP
cluster configuration changes are performed as atomic, consistent operations across all the cluster
nodes.
HP SGeSAP/LX modular packages maintain internal versioning, that allows keeping packages
with different versions within the same cluster. In particular, this allows adding new HP SGeSAP/LX
packages for additional SAP instances without the requirement to upgrade any already existing
HP SGeSAP/LX package to the same HP SGeSAP/LX revision simultaneously.
HP SGeSAP/LX package configuration supports three verbosity levels. HP SGeSAP/LX package
logging supports five verbosity levels.
Modular-style SGeSAP-packages support Serviceguard features including package maintenance
mode and Service Live Application Detach.
NOTE: Legacy-style packages created with HP SGeSAP/LX A.03.00 continue to operate in HP
SGeSAP/LX A.6.00 environments. However, new packages must be created as modular-style
packages and the existing packages must be migrated to modular-style packages as soon as
possible. See “Related information” (page 13) section for a reference to the user guidelines to
achieve this.
Automated SAP enqueue replication
Central part of any SAP HA cluster is the handling of SAP enqueue locking services that ensure
data consistency for the application.
A cluster-wide multi-node package of HP SGeSAP/LX keeps track of the status of all clustered
enqueue services and their remote replications and allows to treat them as Serviceguard generic
resources. This enables easy creation of clusters with two or more nodes that run one or more
Central Service/Replication Instance pairs in an automated fashion. The package pairs use a
Follow-and-push failover policy that ensures that SAP Central Service Instances can repeatedly
failover without transaction loss for the SAP applications.
It is not required to install, administer, and maintain several Replication Instances for one SAP
Central Service. HP SGeSAP/LX does not require active-passive setups for multiple replications
and avoids potential error sources that lie in the added complexity of such setups. If possible, the
single Replication Instance gets pushed out to another cluster node after a Central Service Instance
failover and rebuilds replication services at the new cluster node.
HP SGeSAP/LX ensures that administrator-triggered restarts of SAP Central Services do not invalidate
existing replication information. This allows to avoid disrupting business processes due to human
error.
6