Managing HP Serviceguard Extension for SAP for Linux, December 2013

1 Overview

1.1 About this manual

This document describes how to plan, configure, and administer highly available SAP Netweaver

systems on Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) systems using

HP Serviceguard high availability cluster technology in combination with HP Serviceguard Extension

for SAP (SGeSAP). To use SGeSAP, you must be familiar with the knowledge of Serviceguard

concepts and commands, Linux operating system administration, and SAP basics.

This manual has five chapters:

• Chapter 1—Overview

• Chapter 2— SAP cluster concepts

This chapter gives an introduction to the high-level design of a High Availability SAP server

environment.

• Chapter 3—SAP cluster administration

This chapter covers both SGeSAP cluster administration for IT basis administrators and clustered

SAP administration for SAP basis administrators.

• Chapter 4—SAP cluster storage layout planning

This chapter describes the recommended file system and shared storage layout for clustered

SAP landscape and database systems.

• Chapter 5—SAP cluster configuration

This chapter includes guidelines and configuration details for SGeSAP clusters.

• Chapter 6— Clustering SAP HANA System Replication using SGeSAP packages

This chapter describes SAP HANA system.

Table 1 Abbreviations

MeaningAbbreviation

System ID of the SAP system, RDBMS or other components in

uppercase/lowercase

SAP instance, For example, DVEBMGS, D, J, ASCS, SCS, ERS<INSTNAME>

Refers to either an SCS or an ASCS instance[A]SCS

Instance number of the SAP system<INSTNR>, <INR>

Names mapped to local IP addresses of the server LAN<primary>, <secondary>, <local>

Names mapped to relocatable IP addresses of Serviceguard packages

in the server LAN

<relocdb_s>, <relocci_s>, <relocdbci_s>

Names mapped to local IP addresses of the server LAN<primary_s>, <secondary_s>, <local_s>

Names mapped to relocatable IP addresses of Serviceguard packages

in the server LAN

<relocdb_s>, <relocci_s>, <relocdbci_s>

Other abbreviations are self-explanatory and can be derived from the

surrounding context

<...>

1.1 About this manual 7