Skip to main content

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link

In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started.

When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs. 

Operation Modes in Hana System Replication:

There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay.

1. Delta_datashipping:

In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to continuous log shipping.The shipped logs are persisted on secondary but not replayed. They are only replayed during the takeover from the position of last arrived delta data shipment. Since the logs are not replayed continuously, it has lower memory footprint and can also be used as a non-prod system.

2. Logreplay

This mode is only supported in Hana 1.0 SPS 11 or above. In this operation mode initially one full data shipping is done as part of replication setup and then redo logs are continuously shipped and immediately replayed on arrival. This continuous log replay helps to take over immediately when primary system fails. 

In case of connection disruption, the primary system retains the logs that have not been shipped to secondary due to connectivity issue. The retention can be configured with maximum retention size. When it reaches the size limit, the logs are claimed and overwritten by new logs to prevent log full situation in primary. After this situation, full data shipping needs to be performed again.

Since the logs are replayed continuously, the secondary system has a higher memory footprint and can't be simultaneously used as a non-prod system.

3. Logreplay_readaccess

This mode is only supported in Hana 2.0 SPS 00 or above. This operation mode is just a extended version of logreplay which allows read access on the secondary system. Apart from this extra feature, everything is same as logreplay. 

We talked about different operation modes. Now let's check what are various replication modes that are used during replication.

Replication Modes in Hana System Replication:

1. SYNCMEM - Synchronous in-memory 

In this, the secondary database sends an acknowledgement to the primary system when the log has been received in the memory. Since the secondary doesn't have to wait for the data to be written on disk before sending acknowledgement, system performance is better. This is designed to be used in close proximity or server in same region.

When the connection to secondary system is lost, after a default wait time of 30sec, the primary system continues the transaction processing and retains logs on local disk.

Data loss can occur:
  • when primary and secondary site fails at same time, some data was in memory but not written to disk on either of them. After restart the data which was in memory would be lost.
  • when a takeover is executed while the secondary is unavailable. Data arrived on secondary would be outdated as compared to primary.

2. SYNC - Synchronous 

This mode is also mostly used in scenarios where the servers are in same region or in very close proximity. In this, the secondary database sends an acknowledgement to the primary system when the log has been received and written to disk.

When the connection to secondary system is lost, after 30sec the primary system continues the transaction processing and retains logs on local disk.

Since the logs are written to disk, there would be no data loss due to site failure. 

Data loss can occur:

  • when a takeover is executed while the secondary is unavailable. Data arrived on secondary would be outdated as compared to primary.

2.1 Full Sync - Extension of SYNC

This is an extension to sync mode. It considers log write successful when the log buffer is written in both primary & secondary site's disk. When the secondary system is disconnected (for example, because of network failure), the primary system suspends the transaction processing until the connection to the secondary system is reestablished.

No data loss occurs in this scenario. But write operations on primary can't happen if connection to secondary site is not working.

This option can be set using parameter [system_replication]/enable_full_sync

3. ASYNC - Asynchronous 

In this, the primary system doesn't have to wait for any acknowledgement from secondary. Since the secondary doesn't have to wait for any acknowledgement, system performance is better without any delay.
It is more vulnerable to data loss. Data changes maybe lost during takeover.

That was all about replication & operation modes. In our next blog we will go through replication setup & it's pre-requisites. 


  1. Hello, It's a good will be even better if you can include how to change the operation mode( logreplay to delta_datashipping and vice-versa)and what are the steps needed for it.

    1. Hi, thanks for supporting us. To change operation mode, you need to reconfigure replication with required operation mode. For setup config check


Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

SAP Router and SAP Web Dispatcher

 SAP Router and SAP Web Dispatcher When I started reading about architecture , I was always confused what is the need and requirement of SAP Router , SAP Web dispatcher and thing that added to confusion was ICM , now we know the ICM handles the Web request but then why we need these two, These are Application level gateway provided by SAP and ICM happens to be on the SAP Application level , SAP Netweaver Application Server level. SAP ROUTER SAP WEB DISPATCHER Filtering Function  Load balancing and filtering HTTP(S) requests Used for Routing and Filtering traffic at the SAP Net work Interface Layer Filter requests based on the IP address or protocol Require that a password is sent with request Require that secure authentication and data encryption occurs at network layer using SCN , Secure Network Communication  To enforce access control, specify the IP addresses and address patterns that can access your SAP systems in the saprouttab configuration file The rules to use for filtering the