HP Serviceguard Extension for SAP (SGeSAP) manual Creation of Replication Instance

Scan the old <SID>_DVEBMGS<INSTNR>_<local_ip> profile to see whether there are additional parameters that apply to either the Enqueue Service or the Message Service. Individual decisions need to be made whether they should be moved to the new profile.

Here is an example template for the startup profile START_DVEBMGS<INSTNR>_<DRELOC>

#-----------------------------------------------------------------------

SAPSYSTEMNAME = <SID>

INSTANCE_NAME = DVEBMGS<INSTNR_2>

#-----------------------------------------------------------------------

# start SCSA

#-----------------------------------------------------------------------

Execute_00 = local $(DIR_EXECUTABLE)/sapmscsa -n pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>

#-----------------------------------------------------------------------

# start application server

#-----------------------------------------------------------------------

_DW = dw.sap<SID>_DVEBMGS<INSTNR_2> Execute_01 = local rm -f $(_DW)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/disp+work $(_DW)

Start_Program_01 = local $(_DW) pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>

#-----------------------------------------------------------------------

# start syslog send daemon

#-----------------------------------------------------------------------

_SE = se.sap<SID>_<INSTNR_2> Execute_03 = local rm -f $(_SE)

Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)

Start_Program_02 = local $(_SE) -F pf=$(DIR_PROFILE)/<SID>_DVEBMGS<INSTNR_2>_<DRELOC>

#-----------------------------------------------------------------------

Creation of Replication Instance

This section describes how to add Enqueue Replication Services (ERS) to a system that has SAP kernel 4.6, 6.x or 7.0 ASCS and/or SCS instances. The section can be skipped for SAP kernel 7.10 and higher. Use the installation routines for ERS instances as provided by the SAP installer instead.

The ASCS (ABAP) or SCS (JAVA) instance will be accompanied with an ERS instance that permanently keeps a mirror of the [A]SCS internal state and memory. As a result, no information gets lost due to failing SAP System Central Services, if the SGeSAP package that includes [A]SCS fails over to the node that runs ERS during runtime.

NOTE: If both SCS and ASCS are intended to take advantage of Replicated Enqueue, then the following steps need to be taken twice.

Replicated Enqueue Conversion: RE070

Create a new mountpoint.

su - <sid>adm

mkdir /usr/sap/<SID>/ERS<INSTNR>

Replicated Enqueue Conversion: RE080

A volume group needs to be created for the ERS instance.

The physical device(s) should be created as LUN(s) on shared storage. Storage connectivity is required from all nodes of the cluster that should be able to run the Replicated Enqueue. For the volume group, one logical volume should get configured.

Mount the new logical volume to the mountpoint created in RE070.

NOTE: The <INSTNR> of the ERS has to be different from the instance number of the ASCS and SCS.

Replicated Enqueue Conversion: RE090

Create instance subdirectories in the mounted logical volume

42 Step-by-Step Cluster Conversion