sap distributed system configuration with srs hadr
Post on 22-May-2022
23 Views
Preview:
TRANSCRIPT
Page 1
Page 2
Table of Contents
1.- SYSTEM DESCRIPTION ................................................................................................................................... 3
1.1.- Architecture ...................................................................................................................................................... 3
1.2.- Software Versions ............................................................................................................................................. 3
1.3.- Notes ................................................................................................................................................................ 4
1.4.- Installation Media ............................................................................................................................................. 4
2.- STEPS TO CREATE A DISTRIBUTED SAP SYSTEM ON SAP ASE .......................................................................... 4
2.1.- ABAP Central Services Instance installation ..................................................................................................... 5
2.2.- Database Instance Instalation ........................................................................................................................ 14
2.3.- Primary Application Server Instance installation ........................................................................................... 26
3.- STEPS TO CREATE AN SRS HADR SYSTEM ...................................................................................................... 37
3.1.- Installing an empty SAP ASE DB in standby system ........................................................................................ 37
3.2.- Installing SAP Replication Server in standby host .......................................................................................... 50
3.3.- Installing SAP Replication Server in primary host and configure HADR system ............................................. 58
4.- PLANNED FAILOVER ..................................................................................................................................... 67
5.- SAP HA SYSTEM VARIABLES CONFIGURATION TO RECONNECT AFTER ‘FAILOVER’ ........................................ 70
Page 3
1.- SYSTEM DESCRIPTION
1.1.- Architecture
This document describes how to install and configure a distributed SAP system with HADR using SAP
Replication Server. The system architecture is described in following picture:
A basic SAP system has 3 main components, namely Central Services instance, Database Server instance
and Primary Application Server instance. Those 3 components are installed in 2 different hosts and a third host is
used for the standby Database Server instance, so this system consists of 3 hosts in total:
- Node NW (hostname=mo-ecb9a7d18). This host has the Central Services instance and the
Primary Application Server instance.
- Node HADR1 (hostname=mo-8fc5167c). This host has the Primary Dataserver instance and
the primary SAP Replication Server.
- Node HADR2 (hostname=mo-11263a231). This host has the Standby Dataserver instance and
the standby SAP Replication Server.
1.2.- Software Versions
Taking into account SAP note 1891560 (Disaster Recovery Setup with SAP Replication Server) there are
only some supported SAP ASE-SRS combinations, for this installation latest combination supported on April 1st
2015 is used, that is SAP ASE 15.7 SP 132 and SRS 15.7.1 SP133.
Netweaver version used is 7.4 Support Release 2.
Page 4
1.3.- Notes
Platform used for this installation is Windows 2012 but process would be totally similar in other
platforms. Screen shots are shown for the configuration process to have clear details.
1.4.- Installation Media
Required software to install this environment is:
· SWPM 1.0 latest patch (Windows X64 SP07_3 used)
· NetWeaver 740 SR2 Installation Export (51048524_1)
· SAP Kernel 742 (51049350_10)
· SAP ASE 15.7 SP132 for BS
· SRS 15.7.1 SP133 certified for BS.
2.- STEPS TO CREATE A DISTRIBUTED SAP SYSTEM ON SAP ASE
Three steps need to be executed to install an SAP distributed SYSTEM, they appear in the first SAP installer window:
Page 5
Those steps are:
- Install ABAP Central Services instance.
- Install SAP ASE Database Server instance.
- Install Primary Application Server instance.
In a distributed system more than one host are used to install these components, as said in 1.1 in this case
the Central Services instance and Primary Application Server instance are placed in the same physical host and the
Database Server instance in a separate host.
2.1.- ABAP Central Services Instance installation
ASCS instance is installed in node NW (host=mo-ecb9a7d18), these are the screen shots that show all the
options selected and all properties configured:
Page 6
Page 7
Page 8
Page 9
Note: this is message about swap space is a warning and it works with less than 20 GB, it can be skipped.
Page 10
Page 11
Page 12
Page 13
Click next after the summary window and sometime later installation will finish:
SAPMMC shows both Message Server and Enqueue Server running:
Page 14
2.2.- Database Instance Instalation
Database Instance is installed in node HADR1 (hostname=mo-8fc5167c). Minimum required memory in
the host is 16 GB, with less installation will be aborted with an error (maybe adjusting number of r3load processes
could make it work):
Page 15
Note: profile folder used is the one in NW node (host=mo-ecb9a7d18)
Page 16
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23
Page 24
Page 25
Page 26
2.3.- Primary Application Server Instance installation
Primary application server is installed in node NW (host=mo-ecb9a7d18):
Page 27
Page 28
Page 29
Page 30
Page 31
Page 32
Page 33
Page 34
Page 35
Page 36
Page 37
3.- STEPS TO CREATE AN SRS HADR SYSTEM
3.1.- Installing an empty SAP ASE DB in standby system
Standby system is node HADR2 (hostname=mo-11263a231) so empty DB is installed in it:
Page 38
Page 39
Page 40
Page 41
Page 42
Page 43
Page 44
Page 45
Page 46
Page 47
Page 48
Page 49
Page 50
3.2.- Installing SAP Replication Server in standby host
HADR installation starts installing SRS software in standby host (hostname=mo-11263a231), notice that
SRS system is not configured yet:
Page 51
Page 52
Page 53
Page 54
Page 55
Page 56
Note: do not select “Configure replication environment”, this will be done in primary node.
Page 57
Page 58
3.3.- Installing SAP Replication Server in primary host and configure HADR system
Install SRS software in primary node (hostname=mo-8fc5167c) and configure SRS system:
Page 59
Page 60
Page 61
Page 62
Page 63
Note: this is primary node so select “configure replication environment” option
Page 64
Page 65
Page 66
Page 67
HADR system is configured properly:
4.- PLANNED FAILOVER
Planned failover happens when standby node is manually promoted to primary without having any
problem at primary node.
Page 68
Notice that primary node (host= mo-8fcf5167c) is active and has SAPSR3 connections:
Planned failover steps:
- Stop SAP Application Server
- Run sap_failover <primary_site>, <standby_site>, timeout
- Run sap_host_available <primary_site>
Notes:
- sap_failover is asynchronous so check completion with sap_status until finish or error
- sap_host_available is synchronous, it will take some time but finish when prompt appears
Page 69
sap_status path shows that old standby is now primary/active:
Page 70
Start SAP Application Server that is configured to connect to old primary SAP ASE and check that
connections are redirected automatically to new primary SAP ASE, this redirection is done by SAP ASE in a
transparent way from application point of view:
5.- SAP HA SYSTEM VARIABLES CONFIGURATION TO RECONNECT AFTER ‘FAILOVER’
If old primary is down for any reason (imagine for instance an unplanned failover because old primary
failed) then SAP ASE redirection would not work and SAP Application Server would not be able to connect to
Database server. Force this situation shutting down SAP Application Server and shutting down old primary SAP
ASE. Then start SAP Application Server again and check that connections to Database Server cannot be stablished,
this can be check with r3trans –d command:
Page 71
No SAPSR3 connections to new primary ASE:
Configure SAP HA system variables for <SID>adm user:
dbs_syb_ha=1
dbs_syb_server=mo-8fcf5167c:mo-11263a231
dbs_syb_port=4901:4901
Page 72
Start a new command prompt to execute r3trans –d or reboot SAP Application Server (so that configured
environment variables are set) and check that connection is stablished to Database Server:
Page 73
NOTE: once SAP HA environment variables are configured and SAP Application Server is restarted there
is no need to restart SAP Application Server again when a failover occurs, in that case SAP
Application Server is able to stablish connections to new primary without manual intervention.
Page 74
Copyright © 2015 SAP SE SE or an SAP SE affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE and its affiliated companies (“SAP SE Group”) for informational purposes only, without representation or warranty of any kind, and SAP SE Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP SE and other SAP SE products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
top related