HANA and ABAP On One Server Replication

Installation Guide CUSTOMER
Document Version: 1.1 2015-12-09
SAP Systems Based on the Application

Server ABAP of SAP NetWeaver with
the SAP HANA Database
High-Availability Setup Based on SAP HANA System
Replication
SAP HANA SPS07 with SAP Systems Based on SAP
NetWeaver AS ABAP 7.4
Content
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 Exporting the Shared File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Setting Up Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 Installation of SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Downloading the SAP HANA Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Preparing the Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Binding Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Installation of SAP NetWeaver AS ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Mounting the Shared File Systems to Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Binding the Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reviewing the Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Preparing the Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Backing Up the New SAP HANA Database Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Disabling Autostart of Enqueue Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Adapting hdbuserstore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4 Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
6 Post-Installation Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SAP Systems Based on the Application Server ABAP of SAP NetWeaver with the SAP HANA
CUSTOMER Database
2 2015 SAP SE or an SAP affiliate company. All rights reserved. Content
6.1 Configuration of SAP HANA System Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Enabling SAP HANA System Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Registering the Secondary SAP HANA System for Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2 Configuring Memory Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3 Diagnostics Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7 Failover for Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7.1 Moving the Virtual IPs and Virtual Host Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Performing Takeover of the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.3 Registering and Starting Failed Instance Services and Instances from Host A on Host B. . . . . . . . . . . . .33
8 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.1 Checking SAP Host Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2 Checking Replication of the Lock Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.3 Checking SAP HANA System Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Database CUSTOMER
Content 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
1 Introduction
1.1 Goal
This how-to guide contains a step-by-step description for the installation of SAP systems based on SAP
NetWeaver Application Server ABAP 7.4, together with the SAP HANA database on the same host. The scenario
features a replication cluster to ensure high availability:
You therefore need to install the SAP HANA database and SAP NetWeaver AS ABAP on both hosts.
This guide applies to the following releases:
SAP NetWeaver 7.4

SAP Enhancement Package 7 for SAP ERP 6.0
SAP Enhancement Package 3 for CRM 7.0
SAP Enhancement Package 3 for SCM 7.0
SAP Enhancement Package 3 for SRM 7.0
CUSTOMER Database
4 2015 SAP SE or an SAP affiliate company. All rights reserved. Introduction
1.2 Overview
1.2.1 Installation
Context
You need to perform the following main steps to complete the installation:
Procedure
1. Check the prerequisites.

2. Prepare the installation.
3. Install the SAP HANA database instance and SAP NetWeaver AS ABAP:
a. Install the empty SAP HANA database instance on the two hosts:
i) Install the SAP HANA database instance on the primary host.
Install the SAP HANA database instance on the secondary host.
ii) Install the enqueue replication server (ERS) instance on the secondary host.
b. Install the instances of SAP NetWeaver AS ABAP distributed on the two hosts:
i) Install the ASCS instance on the primary host.
ii) Install the enqueue replication server (ERS) instance on the secondary host.
iii) Install the contents of the SAP HANA database instance on the secondary host remotely into the
primary host.
iv) Install the primary application server (PAS) instance on the primary host.
4. Perform the post-installation configuration of the system:
a. Configure SAP HANA database system replication.
b. Configure memory settings on SAP HANA and SAP NetWeaver AS ABAP.
c. Install the required Diagnostics Agents.
Related Information
Prerequisites [page 7]
Preparation [page 9]
Installation of SAP HANA [page 11]
Installation of SAP NetWeaver AS ABAP [page 15]
Post-Installation Configuration [page 27]
Database CUSTOMER
Introduction 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
1.2.1.1 Failover for Disaster Recovery
Context
In the event of failure of the primary host (host A), you need to perform takeover to recover the system on host B:
Procedure
1. Move the virtual IPs and host names.

2. Perform takeover of the SAP HANA database.
3. Start the missing instance agents and instances on host B.
Related Information
Failover for Disaster Recovery [page 31]
CUSTOMER Database
6 2015 SAP SE or an SAP affiliate company. All rights reserved. Introduction
2 Prerequisites
Shared file system suitable for high availability and shared between data centers for ABAP host names
Adaptive computing approach required for all ABAP instances. No local storage or file systems.
2.1 Hardware and Software Requirements
The hosts need to be able to support the SAP HANA database plus SAP NetWeaver AS ABAP. Make sure that
both hosts meet these combined requirements:
SAP HANA database see section Hardware and Software Requirements in the SAP HANA Server
Installation Guide.
SAP NetWeaver AS ABAP see section Hardware and Software Requirements at:
http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.4 Installation SAP
NetWeaver Systems Installing Systems Based on NW 7.1 or Higher-SW Prov. Mgr. 1.0 SAP HANA
Database Linux ABAP
For more information on sizing, see SAP Note 1793345 . Note that each host must meet the requirements
for the SAP HANA appliance plus SAP NetWeaver AS ABAP.
The required file systems are created during installation of the SAP HANA database and SAP NetWeaver AS
ABAP. However, if required you can set them up before the installation and specify them during the
installation procedure.
For more information, see section Recommended File System Layout in the SAP HANA Server Installation
Guide.
Operating system:
SUSE Linux Enterprise Server (SLES) 11 as listed in the Product Availability Matrix (PAM) .
For information about installing SLES 11 in an SAP environment, see SAP Note 1310037 . For
information about optimal settings for SLES 11, see SAP Note 1824819 .
Red Hat Enterprise Linux (RHEL) 6 as listed in the Product Availability Matrix (PAM) .
For general information about installation and configuration of RHEL6 for running SAP applications, see
SAP Note 1496410 . For HANA-specific settings, see SAP Note 2136965 (RHEL6.6) or 2013638
(RHEL6.5).
2.2 SAP Notes
Make sure that you have the up-to-date version of the main SAP Notes, which you can find at http://
service.sap.com/notes .
Database CUSTOMER
Prerequisites 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
Table 1:
SAP Note Title
1514967 SAP HANA: Central Note
2021789 SAP HANA Revision and Maintenance Strategy
2004651 SAP HANA Platform SPS 08 Release Note
1523337 SAP HANA Database: Central Note
1680045 Release Notes for Software Provisioning Manager
855498 Installation Prerequisites Checker
1793345 Sizing for SAP Suite on HANA
1872170 Suite on HANA Memory Sizing
1704753 Inst. Systems based on SAP NetWeaver 7.1 and higher: UNIX
1706930 Inst. SAP Sys. Based on NW 7.3 and higher: SAP HANA DB, UNIX
1310037 SUSE LINUX Enterprise Server 11: Installation notes
1824819 SAP HANA DB: Recommended OS settings for SLES11/SLES4SAP SP2
1496410 Red Hat Enterprise Linux 6.x: Installation und Upgrade
2136965 SAP HANA DB: Recommended OS settings for RHEL 6.6
2013638 SAP HANA DB: Recommended OS settings for RHEL 6.5
886535 Downloading multispanning archives
CUSTOMER Database
8 2015 SAP SE or an SAP affiliate company. All rights reserved. Prerequisites
3 Preparation
Context
Procedure
3.1 Exporting the Shared File System
Context
Procedure
Export the shared file systems. The shared file systems are /usr/sap/<SID> and /sapmnt/<SID>.
3.2 Setting Up Users and Groups
Context
Database CUSTOMER
Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
Procedure
Make sure that the following user IDs and group IDs are identical on both hosts so they can be accessed in the
same way via the shared file system. You can do this either by setting up the users on each host now (that is,
before starting the installation) or when prompted during the installation:
Central groups:
sapsys, sapinst
Central users:
<sid>adm (diagnostics agent), <sid>adm (ABAP system), <sid>adm (HANA database) sapadm (SAP host
agent)
CUSTOMER Database
10 2015 SAP SE or an SAP affiliate company. All rights reserved. Preparation
4 Installation of SAP HANA
You need to install the SAP HANA database using the SAP HANA installer (hdblcm) tool on both hosts, the
primary (host A) and secondary (host B). For more information, see the SAP HANA Server Installation Guide.
Note
You install the software in the same way on both host A and host B that is, the same SIDs and instance
numbers for both databases. This is important for system replication and (if required) failover to function
correctly. We use the system ID HAN in the examples in this section.
Caution
You must use a different SAP system ID (SID) for the SAP HANA database than the one you later specify for the
installation of the SAP NetWeaver AS ABAP.
4.1 Preparation
4.1.1 Downloading the SAP HANA Software
Procedure
1. Download the most recent version of the SAP HANA software from the SAP Software Download Center to a
single download directory on the local host:
http://service.sap.com/swdc under Installations and Upgrades A-Z Index Installations and

Upgrades H SAP In-Memory (SAP HANA) HANA Platform Edition SAP HANA PLATFORM EDITION
SAP HANA PLATFORM EDIT. 1.0 Installation
The software is available as a multispanning archive in file format rar.
2. See SAP Note 886535 for more information on how to unpack multispanning archives.
3. Copy or mount the media to make them available on the target host.
4.1.2 Preparing the Hosts
Make sure you meet the minimum hardware and software requirements on each host.
Database CUSTOMER
Installation of SAP HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
Related Information
Hardware and Software Requirements [page 7]
4.2 Installation
4.2.1 Prerequisites
You use the tool hdblcm or the GUI version hdblcmgui to install SAP HANA. In this documentation we use
hdblcm.
You must run the installer (hdblcm or hdblcmgui) as root user from the following directory where you
downloaded and extracted the installation medium:
<DVD root directory>/DATA_UNITS/HDB_LCM_LINUX_X86_64
4.2.2 Installing SAP HANA
Prerequisites
You must run the installation described below on host A and on host B.
Caution
Make sure that the operating system and database users and groups are exactly the same on host A and host
B.
Procedure
1. Change to the directory containing hdblcm and enter the command hdblcm to start the installation.
2. Choose Install new system and select the additional components required:
Option Description
SAP HANA Studio Installs the components of the SAP HANA Studio
SAP HANA Lifecycle Manager Installs the components of the SAP HANA Lifecycle Manager
CUSTOMER Database
12 2015 SAP SE or an SAP affiliate company. All rights reserved. Installation of SAP HANA
Option Description
SAP HANA Database Client Installs the components of the SAP Database Client
3. Specify the required installation parameters.

In most cases you can accept the default values unless you have specific requirements, such as for the SAP
system ID.
Next Steps
If required, you can check that the SAP Host Agent is running although it should normally be running
automatically.
Related Information
Checking SAP Host Agent [page 34]
4.2.3 Binding Virtual Host Names
Context
Procedure
As root on host A, execute the SAP Host Agent (which is already installed) to bind all virtual host names as
below:
/usr/sap/hostctrl/exe/saphostctrl -function ACOSPrepare -op ifup -iface eth0 -vhost
<virtual host name of database> -nmask <subnet mask of network adapter>>
Example
/usr/sap/hostctrl/exe/saphostctrl -function ACOSPrepare -op ifup -iface eth0 -vhost
hadrdbhan -nmask 255.255.252.0
Database CUSTOMER
Installation of SAP HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. 13
4.3 Result
You now have a SAP HANA system with an empty database on host A and on host B, a shared file system (for the
installation of SAP NetWeaver AS ABAP), and a virtual host name for the SAP HANA database, as shown in the
figure below.
If required, you can check that the SAP Host Agent is running, although it should normally be running
automatically.
Now you are ready to install SAP NetWeaver AS ABAP on host A and on host B.
Related Information
Installation of SAP NetWeaver AS ABAP [page 15]

Checking SAP Host Agent [page 34]
CUSTOMER Database
14 2015 SAP SE or an SAP affiliate company. All rights reserved. Installation of SAP HANA
5 Installation of SAP NetWeaver AS ABAP
You need to install the instances of SAP NetWeaver AS ABAP distributed on both hosts using the Software
Provisioning Manager as follows:
1. On host A, you install the primary application server and the ASCS instances.
2. On host B, you install the enqueue replication server instance.
Caution
You must use a different SAP system ID (SID) for the SAP NetWeaver AS ABAP system than that already
specified for the installation of the SAP HANA database.
Note
In this chapter, we use SAP system ID (SID) AMG as an example for the new system to be installed. You can
choose any other SID.
There are references to the installation guide in this section. You can find the installation guide for SAP
NetWeaver AS ABAP here:
http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.4 Installation Installation SAP

NetWeaver Systems Installing Systems Based on NW 7.1 or Higher SAP HANA Database UNIX ABAP
5.1 Preparation
5.1.1 Mounting the Shared File Systems to Directories
Context
On host A and on host B, do the following:
Procedure
1. Create the following directories:

mkdir -p /usr/sap/<SID>
Database CUSTOMER
Installation of SAP NetWeaver AS ABAP 2015 SAP SE or an SAP affiliate company. All rights reserved. 15
mkdir -p /sapmnt/<SID>
2. Mount the shared file systems to these directories:
mount <hostname>:<export name / path>/usr/sap/<SID>
mount <hostname>:<export name / path>/sapmnt/<SID>
5.1.2 Binding the Virtual Host Names
Context
Execute the following commands to bind the virtual host names on the corresponding network adapter of the
installation hosts.
Note
In most cases you can accept the default values unless you have specific requirements, such as for the SAP
system ID.
Procedure
1. On host A, execute a SAP Host Agent function to bind all virtual host names to the subnet mask of the
network adapter:
/usr/sap/hostctrl/exe/saphostctrl -function ACOSPrepare -op ifup - iface eth0 -
vhost <virtual host name of ASCS instance> -nmask <subnet mask of network adapter>
vhost <virtual host name of PAS instance> -nmask <subnet mask of network adapter>
Example
vhost hadrcsamg -nmask 255.255.252.0

vhost hadrciamg -nmask 255.255.252.0
2. On host B, execute a SAP Host Agent function to bind all virtual host names to the subnet mask of the
network adapter:
vhost <virtual host name of ERS instance> -nmask <subnet mask of network adapter>
CUSTOMER Database
16 2015 SAP SE or an SAP affiliate company. All rights reserved. Installation of SAP NetWeaver AS ABAP
Example
vhost hadreramg -nmask 255.255.252.0
5.1.3 Reviewing the Installation Parameters
Procedure
During the installation, the installer prompts you for several parameters. To review these before starting the
installation, see section Basic SAP System Installation Parameters in the installation guide of SAP NetWeaver AS
ABAP.
5.1.4 Preparing the Installation Media
Procedure
Download and set up the installation media, making sure you always use the current version. This comprises:
The software provisioning manager, containing the installer, which you can find here:
http://service.sap.com/sltoolset Software Logistics Toolset 1.0 System Provisioning
The software for the installation of SAP Business Suite
For more information, see section Preparing the Installation Media in the installation guide of SAP NetWeaver AS
ABAP.
5.2 Installation
5.2.1 Prerequisites
You use the installer of the Software Provisioning Manager to install the various instances comprising the
system SAP Business Suite.
You check that you meet the prerequisites described in Prerequisites of section Running the Installer in the
installation guide.
Database CUSTOMER
You use the installation options for a High-Availability System in the installer, as described below.
5.2.2 Running the Installer
5.2.2.1 Installing the ABAP SCS Instance on Host A
Context
Procedure
1. Log on to host A as the root user and change to the directory where you set up the Software Provisioning
Manager.
2. Perform the following steps on host A to install the ABAP SCS (ASCS) instance:
a. Enter the following command to start the installer:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name of ASCS instance>
Example
./sapinst SAPINST_USE_HOSTNAME=hadrcsamg
b. On the Welcome screen, choose the option:
SAP Business Suite powered by SAP HANA <your Business Suite scenario> SAP HANA Database
SAP Systems Application Server ABAP High-Availability System ASCS Instance
c. Choose Next.
d. Follow the instructions in the installer, entering the parameters you defined.
Caution
You must use a different SAP system ID (SID) for the SAP NetWeaver AS ABAP system than that
already specified for the installation of the SAP HANA database.
e. On the Parameter Summary screen, check all the parameters

If required, you can revise the parameters before starting the installation.
f. To start the installation, choose Start.
CUSTOMER Database
Results
The installer starts the installation and displays the progress of the installation. When the installation has finished,
the installer shows the message:
Execution of <Option_Name> has completed.
Related Information
Reviewing the Installation Parameters [page 17]
5.2.2.2 Installing the Enqueue Replication Server Instance on

Host B
Context
Procedure
1. Log on to host B as the root user and change to the directory where you set up the Software Provisioning
Manager.
2. Perform the following steps on host B to install the enqueue replication server (ERS) instance:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name of ERS instance>
Example
./sapinst SAPINST_USE_HOSTNAME=hadrerhan
SAP Business Suite powered by SAP HANA <your Business Suite scenario> SAP HANA Database
SAP Systems Application Server ABAP High-Availability System Enqueue Replication Server
Instance
c. Choose Next.
Database CUSTOMER
Caution
Do not select the parameter Get the (A)SCS instance restarted because it is currently not working.

The installer starts the installation and displays the progress of the installation. When the installation has
finished, the installer shows the message:

3. On host A, restart the ASCS instance by entering this command:
sapcontrol nr <ASCS instance number> function RestartInstance
A message like the following appears to confirm that the instance has been restarted:
29.10.2013 08:53:31
RestartInstance
OK
Results
Related Information
5.2.2.3 Installing the Contents of the Database Instance

from Host B to Host A
Context
You need to remotely (that is, from host B) bring the contents of the pre-installed database instance on host B to
the pre-installed database on host A. Therefore, you need to perform the installation instructions in this section on
host B.
CUSTOMER Database
Procedure
1. Log on to host B as the root user and change to the directory where you set up the Software Provisioning
Manager.
2. On host B, perform the following steps to install the contents of the SAP HANA database into the existing SAP
HANA database instance on host A:
./sapinst
Example
./sapinst SAPINST_USE_HOSTNAME=hadrdbhan
SAP Business Suite powered by SAP HANA your Business Suite scenario SAP HANA Database
SAP Systems Application Server ABAP High-Availability System Database Instance
c. Choose Next.
Caution
When the installer prompts you for the database host, make sure that you specify the virtual host
name bound to the network interface on host A.
In addition, make sure that you specify the same database ID as you entered during the installation of
SAP HANA.

Results
Database CUSTOMER
5.2.2.4 Installing the Primary Application Server Instance on
Host A
Context
Procedure
1. Log on to host A as the root user and change to the directory where you set up the Software Provisioning
Manager.
2. Perform the following steps on host A to install the primary application server (PAS) instance:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name for PAS instance>
Example
./sapinst SAPINST_USE_HOSTNAME=hadrciamg
SAP Business Suite powered by SAP HANA your Business Suite scenario SAP HANA Database
SAP Systems Application Server ABAP High-Availability System Primary Application Server
Instance
c. Choose Next.
Caution
When specifying the profile directory, use a different SAP system ID (SID) than that already specified
for the installation of the SAP HANA database.

Results
CUSTOMER Database
Related Information
5.3 Post-Installation
If required, you can check the replication of the lock table of the SAP ABAP enqueue replication server (ERS
instance).
Related Information
Checking Replication of the Lock Table [page 34]
5.3.1 Backing Up the New SAP HANA Database Installation
Procedure
Use the backup tool in the SAP HANA Administration Console of the SAP HANA studio to back up the new
installation. Make sure you perform a Complete Data Backup.
For more information, see section The Backup Console in the SAP HANA Administration Guide.
5.3.2 Disabling Autostart of Enqueue Replication Server
Context
Database CUSTOMER
Procedure
Disable autostart of the enqueue replication server (ERS) instance by editing the value of the profile parameter
Autostart to 0 in the following file:
/usr/sap/<SID>/ERS11/profile/<ERS instance profile name>
5.3.3 Adapting hdbuserstore
Context
On host A and B, the installer writes the physical host names of the SAP HANA database to hdbuserstore.
However, the virtual host names are required. This procedure describes how to achieve this.
Perform the following procedure on both hosts.
Procedure
1. Log on as the <sid>adm user of SAP NetWeaver AS ABAP.

2. Delete the current entry of hdbuserstore with the following command:
hdbuserstore delete default
3. Make the new entry as follows:
hdbuserstore set default <virtual host name of SAP HANA database>:3<instance number
of SAP HANA database>15 SAP<SAP ABAP Schema SID> <schema password defined during
installation>
4. To check, execute the following command as the <sid>adm user of the system SAP NetWeaver AS ABAP:
R3trans -d
Results
The results should look like:
R3trans finished (0000)
CUSTOMER Database
5.4 Result
You now have a full system for SAP NetWeaver AS ABAP, with a loaded database on host A, an empty database
on host B, a shared file system, and a set of virtual host names:
In the SAP Management Console (SAP MC) and the SAP Microsoft Management Console (SAP MMC) with snap-in
SAP Systems Manager, you can see the instances that are started initially, as in the examples in the screenshots
below, where:
<ABAP SID> = AMG with instances:

ASCS01 (virtual host: hadrcsamg)
ERS11 (virtual host: hadreramg)
DVEBMGS10 (virtual host: hadrciamg)
<HANA SID> = HAN (instance HDB00) running on physical hosts:
hdshanar17
hdshana02
Database CUSTOMER
For more information on how to start and stop SAP instances, see section Starting and Stopping SAP System
Instances in the installation guide, which you can find here:
http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.4 Installation SAP NetWeaver

Systems Installing Systems Based on NW 7.1 or Higher-SW Prov. Mgr. 1.0 SAP HANA Database Linux
ABAP
CUSTOMER Database
6 Post-Installation Configuration
Context
Procedure
6.1 Configuration of SAP HANA System Replication
Context
Procedure
6.1.1 Enabling SAP HANA System Replication
Context
Database CUSTOMER
Post-Installation Configuration 2015 SAP SE or an SAP affiliate company. All rights reserved. 27
Procedure
1. In the SAP HANA Administration Console of the SAP HANA studio, right-click the secondary system and
choose Stop.
2. In the SAP HANA Administration Console of the SAP HANA studio, select the primary system, right click and
choose System Replication Enable System Replication and choose Next.
3. Enter the Primary System Logical Name and choose Finish.
6.1.2 Registering the Secondary SAP HANA System for

Replication
Context
Procedure
1. In the SAP HANA Administration Console of the SAP HANA studio, select the primary system, right click and
choose System Replication Register Secondary System .
2. Enter the details for the secondary system, including logical name, physical host name, and user and
password.
If required, you can also select Start the secondary system after registration.
3. Choose Finish.
4. If you did not start the secondary system in a previous step, perform this action in the SAP HANA
Administration Console of the SAP HANA studio.
Next Steps
If required, you can check SAP HANA system replication.
Related Information
Checking SAP HANA System Replication [page 35]
CUSTOMER Database
28 2015 SAP SE or an SAP affiliate company. All rights reserved. Post-Installation Configuration
6.2 Configuring Memory Settings
Context
This procedure is necessary so that the systems that is, SAP NetWeaver AS ABAP and SAP HANA database
on each host do not compete for memory resources. The exact settings depend on the size of your hosts and the
sizing required for each system, SAP HANA database and SAP NetWeaver AS ABAP.
SAP ABAP and the SAP HANA database can only run together on one server if the sizing of ABAP plus the sizing of
HANA does not exceed the total size of the HANA server in terms of memory. You configure the values resulting
from the ABAP sizing (see SAP note 1793345 ) with PHYS_MEMSIZE and you configure the values for the SAP
HANA database with GLOBAL_ALLOCATION_LIMIT (see SAP note 1872170 ). If you have extra memory
available, allocate it to the SAP HANA database.
Procedure
1. Change the profile for the SAP HANA database either by using the SAP HANA Administration Console of the
SAP HANA studio or at the command line as follows:
a. On host A, modify the following file as user <SID>adm:
/usr/sap/<DB_SID>/SYS/global/hdb/custom/config/global.ini
It must look as follows:
[memorymanager]
global_allocation_limit = <your HANA sizing result>

b. Repeat this step on host B.
2. Change the profile for SAP NetWeaver AS ABAP:
a. Log on to SAP NetWeaver AS ABAP on host A.
b. Start transaction RZ10.
c. Edit the profile for the primary application server instance.
d. Select Extended maintenance.
e. Set the parameter PHYS_MEMSIZE to a value suitable for your host size.
Database CUSTOMER
Post-Installation Configuration 2015 SAP SE or an SAP affiliate company. All rights reserved. 29
6.3 Diagnostics Agent Installation
Context
You must install a Diagnostics Agent for each installed virtual instance.
Procedure
Iinstall a diagnostics agent as described below:

SAP Note 1365123 Installation of Diagnostic Agents
SAP Note 1833501 Diagnostics Agent - Installer Versions
http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+and+HA+Support
CUSTOMER Database
30 2015 SAP SE or an SAP affiliate company. All rights reserved. Post-Installation Configuration
7 Failover for Disaster Recovery
You perform the procedures below if host A fails so that the system can resume operation on host B.
Note
All SAPGUI sessions are disconnected following failure of host A.
If you have not already done so, mount the shared file systems of the SAP NetWeaver AS ABAP.
7.1 Moving the Virtual IPs and Virtual Host Names
Context
Procedure
1. If host A is still running, enter the following commands as root on host A to unbind the virtual IPs and host
names (assuming that eth0 is the production network interface):
/usr/sap/hostctrl/exe/saphostctrl -function ACOSPrepare -op ifdown - iface eth0 -
vhost <virtual host name of DB instance> -nmask <subnet mask of network adapter>
Example:



vhost hadrdbhan -nmask 255.255.252.0
2. On host B, enter the following commands to bind the virtual IPs and host names on the new host:
Database CUSTOMER
Failover for Disaster Recovery 2015 SAP SE or an SAP affiliate company. All rights reserved. 31
vhost <virtual host name of DB instance> -nmask <subnet mask of network adapter>
Example:



vhost hadrdbhan -nmask 255.255.252.0
7.2 Performing Takeover of the SAP HANA Database
Context
Procedure
On host B, enter the following commands to take over the SAP HANA database on the secondary host:
su hanadm
hdbnsutil sr_takeover
Next Steps
You can also do this using the SAP HANA Administration Console of the SAP HANA Studio: right-click the
secondary system and choose System Replication Perform Takeover .
CUSTOMER Database
32 2015 SAP SE or an SAP affiliate company. All rights reserved. Failover for Disaster Recovery
7.3 Registering and Starting Failed Instance Services and
Instances from Host A on Host B
Context
On host B, do the following to start the required instance agents and instances so that SAP NetWeaver AS ABAP
can resume operation.
Procedure
1. Log on as root user to the operating system and copy the following entries (retrieved from host A) to
the /usr/sap/sapservices file on host B:
LD_LIBRARY_PATH=/usr/sap<SID>/ASCS<number of ASCS instance>

/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH;
/usr/sap/<SID>/ASCS<number of ASCS instance>/exe/sapstartsrv
pf=/usr/sap/<SID>/SYS/profile/<SID>_ASCS<number of ASCS
instance>_<virtual host name of ASCS instance> -D -u <sid>adm
LD_LIBRARY_PATH=/usr/sap/<SID>/DVEBMGS<number of PAS
instance>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH;
/usr/sap/<SID>/DVEBMGS<number of PAS instance>/exe/sapstartsrv
pf=/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<number of PAS
instance>_<virtual host name of PAS instance> -D -u <sid>adm
Example:
LD_LIBRARY_PATH=/usr/sap/AMG/ASCS01/exe:$LD_LIBRARY_PATH; export
LD_LIBRARY_PATH; /usr/sap/AMG/ASCS01/exe/sapstartsrv
pf=/usr/sap/AMG/SYS/profile/AMG_ASCS01_hadrcsamg -D -u amgadm
LD_LIBRARY_PATH=/usr/sap/AMG/DVEBMGS10/exe:$LD_LIBRARY_PATH; export
LD_LIBRARY_PATH; /usr/sap/AMG/DVEBMGS10/exe/sapstartsrv
pf=/usr/sap/AMG/SYS/profile/AMG_DVEBMGS10_hadrciamg -D -u amgadm
2. Log on to host B as the operating system user <sid>adm:

su <sid>adm
3. Enter the following commands to start the instance agents of the ASCS and PAS instances:
sapcontrol -nr <number of ASCS instance> -function StartService <SID>
sapcontrol -nr <number of PAS instance> -function StartService <SID>
4. Enter the following commands to start the ASCS and PAS instances:
sapcontrol -nr <number of ASCS instance> -function Start
sapcontrol -nr <number of PAS instance> -function Start
Database CUSTOMER
Failover for Disaster Recovery 2015 SAP SE or an SAP affiliate company. All rights reserved. 33
8 Additional Information
8.1 Checking SAP Host Agent
Context
Procedure
1. Check that the SAP Host Agent is installed and running by entering this command:
/usr/sap/hostctrl/exe/saphostexec status
If the SAP Host Agent is running, you see something like this:
saphostexec running (pid = 21942)
sapstartsrv running (pid =21944)
2. If the SAP Host Agent is installed but not running, enter one of the following commands:
/etc/rc.d/sapinit start
/etc/rc.d/sapinit restart
Next Steps
For more information on SAP Host Agent, including how to download and install it, see SAP Note 1031096 .
8.2 Checking Replication of the Lock Table
Context
CUSTOMER Database
34 2015 SAP SE or an SAP affiliate company. All rights reserved. Additional Information
Procedure
Check that the lock table from the enqueue server of the ASCS instance for the SAP NetWeaver AS ABAP is being
replicated correctly by entering a command as the operating system user <sid>adm like the following on host B,
where the enqueue replication server (ERS) is running:
ensmon pf=/sapmnt/<SID>/profile/<profile name of ERS instance> 2
Results
This message is displayed if replication is running correctly:
Replication is enabled in server, repl. Server is connected
Replication is active
8.3 Checking SAP HANA System Replication
Context
Procedure
1. In the SAP HANA Administration Console of the SAP HANA studio, choose the Overview tab for host A.
The entry for System Replication Status is as follows if SAP HANA system replication is functioning correctly:
All systems are active and in sync
2. Choose Landscape System Replication .

The entry in the column REPLICATION_STATUS for each host is as follows if SAP HANA system replication is
functioning correctly:
ACTIVE
Database CUSTOMER
Additional Information 2015 SAP SE or an SAP affiliate company. All rights reserved. 35
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
CUSTOMER Database
36 2015 SAP SE or an SAP affiliate company. All rights reserved. Important Disclaimers and Legal Information
Database CUSTOMER
Important Disclaimers and Legal Information 2015 SAP SE or an SAP affiliate company. All rights reserved. 37
www.sap.com/contactsap
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. 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 or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP 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.
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. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

HANA and ABAP On One Server Replication

Uploaded by

Copyright:

Available Formats

HANA and ABAP On One Server Replication

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HANA and ABAP On One Server Replication

Uploaded by

Copyright:

Available Formats

Installation Guide CUSTOMER

Document Version: 1.1 2015-12-09

SAP Systems Based on the Application

4 Installation of SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 Installation of SAP NetWeaver AS ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7 Failover for Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

This guide applies to the following releases:

SAP NetWeaver 7.4

1. Check the prerequisites.

1. Move the virtual IPs and host names.

Failover for Disaster Recovery [page 31]

2.1 Hardware and Software Requirements

2.2 SAP Notes

1514967 SAP HANA: Central Note

2021789 SAP HANA Revision and Maintenance Strategy

2004651 SAP HANA Platform SPS 08 Release Note

1523337 SAP HANA Database: Central Note

1680045 Release Notes for Software Provisioning Manager

855498 Installation Prerequisites Checker

1793345 Sizing for SAP Suite on HANA

1872170 Suite on HANA Memory Sizing

1310037 SUSE LINUX Enterprise Server 11: Installation notes

1824819 SAP HANA DB: Recommended OS settings for SLES11/SLES4SAP SP2

1496410 Red Hat Enterprise Linux 6.x: Installation und Upgrade

2136965 SAP HANA DB: Recommended OS settings for RHEL 6.6

2013638 SAP HANA DB: Recommended OS settings for RHEL 6.5

886535 Downloading multispanning archives

3.1 Exporting the Shared File System

3.2 Setting Up Users and Groups

4.1.1 Downloading the SAP HANA Software

http://service.sap.com/swdc under Installations and Upgrades A-Z Index Installations and

4.1.2 Preparing the Hosts

Hardware and Software Requirements [page 7]

4.2.2 Installing SAP HANA

3. Specify the required installation parameters.

Checking SAP Host Agent [page 34]

4.2.3 Binding Virtual Host Names

Installation of SAP NetWeaver AS ABAP [page 15]

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.4 Installation Installation SAP

5.1.1 Mounting the Shared File Systems to Directories

On host A and on host B, do the following:

1. Create the following directories:

5.1.2 Binding the Virtual Host Names

/usr/sap/hostctrl/exe/saphostctrl -function ACOSPrepare -op ifup - iface eth0 -

5.1.3 Reviewing the Installation Parameters

5.1.4 Preparing the Installation Media

5.2.2 Running the Installer

5.2.2.1 Installing the ABAP SCS Instance on Host A

b. On the Welcome screen, choose the option:

e. On the Parameter Summary screen, check all the parameters

Reviewing the Installation Parameters [page 17]

5.2.2.2 Installing the Enqueue Replication Server Instance on

b. On the Welcome screen, choose the option:

e. On the Parameter Summary screen, check all the parameters

Execution of <Option_Name> has completed.

Reviewing the Installation Parameters [page 17]

5.2.2.3 Installing the Contents of the Database Instance

b. On the Welcome screen, choose the option:

e. On the Parameter Summary screen, check all the parameters