HADR Installation in a Nutshell

Part II
Joachim Pfefferle
October 2015

Internal

General Information
This document describes how to install a disaster recovery solution in two
data centers with an SAP system in each data center.
This setup can only be used if a disaster recovery solution is desired, that is,
the SAP system in the primary data center should not connect to the ASE
database that is running in the standby data center after a failover has been
initiated.
Therefore, a seamless failover where the SAP application would automatically
reconnect to the failover database is not possible and the following
environment parameter cannot be set as described in SAP Note 1891560:
dbs_syb_ha = 1
dbs_syb_server = <primary hostname>:<standby hostname>
dbs_syb_port =<primary_port>:<standby_port>

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

General Information
Steps for a planned failover:
Shut down the SAP system in the primary data center.
Initiate a database failover using saphostctrl or the DR_agent.
Start up the SAP system in the standby data center.

Steps for an unplanned failover (ASE crashed in the primary data center and
cannot be restarted):
Shut down the SAP System in the primary data center.
Initiate an unplanned database failover using saphostctrl or DR_agent.
Start up the SAP system in the standby data center.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

General Installation Information

Follow the installation steps outlined in the general SAP Installation Guides
for SAP ABAP and/or JAVA. The installation guides are available on the SAP
Service Marketplace.
The disaster recovery setup with SAP Replication Server and SAP ASE is fully
integrated in SAPs installation tool SAPinst. The installation tool SAPinst will
install the replication software and create all required logins.
A manual setup of the SAP Replication Server or RMA Agent is not supported.
Any manual work will probably cause the SAPinst to fail in one of the setup
steps or you will see unexpected problems later on during productive use of
the system.
The following description is based on SWPM 1.0 SP 9.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

General Installation Information

Start SAPinst on the respective host by selecting the correct action for each
installation step:
Standby System - ASCS Instance
Standby System Database Instance
Standby System Primary Application Server
Replication Server on the Primary Host
Replication Server on the Standby Host

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Replication Topology Directory Structure

Setup: co-located SAP PAS on a separate server in both data centers
Primary Data Center

Standby Data Center

Host 1

Host 2
/sybase

ASE1

/<SID>

/ASE16_0

/sapdata
_n

/sapmnt
/<SID>

/sybase

/<SID>

/<SID>_REP

/REP15_5

/RMA15_5

/SCC3_2

Mount from SAP PAS

RS1
DR Agent

Host 3
SAP-PAS

/ASE16_0

/sapdata_
n

Global

ASE2

/<SID>_REP

/REP15_5

/RMA15_5

/SCC-3_2

Primary SAP System

Standby SAP System

Must be up during
normal operation

Must be down during

normal operation

RS2
DR Agent

Host 4
SAP-PAS

/sapmnt
/<SID>

/sapmnt
/<SID>

/exe

Standby

/sapmnt
/<SID>

Mount from SAP PAS

Active

profile

2015 SAP SE or an SAP affiliate company. All rights reserved.

/exe

Global

Public

profile

Installation Steps for a co-located ASE / SRS installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps
Standby System - ASCS Instance
Prerequisite
SAP System mount folder (/sapmnt/<SID>) of host 4 is mounted on host 2
SAP ASCS Instance and SAP Application Server are fully installed on host 3
Primary ASE is fully installed as a distributed database instance on host 1

Install a second NW system on host 2 and host 4, as described in the Installation

Guide:

Host 4
SAP Netweaver 7.4 Support Release 2 -> SAP ASE -> SAP Systems -> Application Server ABAP
-> Distributed System -> ASCS Instance

Select Custom mode for the installation

<SID> must be the same as on the primary system

UID for user <sid>adm and sapadm must be the same as on the primary system.

Group ID for sapsys must be the same as on the primary system

Provide the virtual host name if using virtual names

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps
Standby System Database Instance
Install a second NW system on host 2 and host 4, as described
in the Installation Guide:
Host 2
SAP Netweaver 7.4 Support Release 2 -> SAP ASE -> SAP Systems -> Application Server ABAP
-> Distributed System -> Database Instance

Select Custom mode for the installation

Checkmark Profiles Available under sapmnt/<SID>/profiles (must be mounted from host 4)

UID for user <sid>adm, sapadm and syb<sid> must be the same as on the primary system.

Group ID for sapsys must be the same as on the primary system

Database devices must have the same size as on the primary database, otherwise materialization will fail

Provide the virtual host name if using virtual names. The database ports can be the same as on the primary
database

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps
Standby System Primary Application Server
Install a second SAP NetWeaver system on host 2 and host 4, as
described in the Installation Guide:
Host 4
SAP Netweaver 7.4 Support Release 2 -> SAP ASE -> SAP Systems -> Application Server ABAP
-> Distributed System -> Primary Application Server Instance

Select Custom mode for the installation

Provide the virtual hostname if using virtual names.

After the installation has finished, stop the SAP system on host 4.
This SAP system should only be started after a database failover from the primary site to the
standby site.
Check with DR_admin command sap_status path that the standby site has the status
Primary:Active

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps for setting up
Replication Server on the Primary Host
Install the Replication Software on host 1, as described
in the Installation Guide:
Host 1
SAP Netweaver 7.4 Support Release 2 -> SAP ASE ->
Database Replication -> Setup of Replication Environment

Select Custom mode for the installation

Select Install the replication server software as installation option

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

10

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps for setting up
Replication Server on the Primary Host
Install the Replication Software on the host, as described
in the Installation Guide:
Host 1

Provide the virtual host name if using virtual names when asked for:

Provide amount of memory and CPUs SRS should be configured with.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

11

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps for setting up
Replication Server on the Standby Host
Install the Replication Software on host 2, as described
in the Installation Guide:
Host 2
SAP Netweaver 7.4 Support Release 2 -> SAP ASE ->
Database Replication -> Setup of Replication Server Environment

Select Custom mode for the installation

Select the following installation options:

Install the replication server software

Configure the replication system

Materialize the secondary database

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

12

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps for setting up
Replication Server on the Standby Host
Host 2
1.

Provide server information using virtual names when asked for:

2.

Provide amount of memory and CPUs the SRS should be configured with.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

13

Installation Steps for a co-located ASE / SRS Installation

SAP PAS installed in both data centers on different hosts
HADR Installation Steps for setting up
Replication Server on the Standby Host
Host 2
3.

Provide site information.

4. Choose Materialization method.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

14

 2015 SAP SE or an SAP 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 or an
SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and S AP SEs or its affiliated
companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

2015 SAP SE or an SAP affiliate company. All rights reserved.