
Quick Contact
SAP Tutorial
- SAP HANA
- Features of SAP HANA
- Advantages and Disadvantages of SAP HANA
- SAP HANA Architecture
- SAP HANA Use Cases
- SAP Hana Installation
- SAP Hana Studio
- SAP HANA Studio Administration Console
- How to Use SAP HANA System Monitor
- How to Use SAP HANA on Azure
- SAP HANA Modeling – Attributes, Measures, Privileges, Modeling Objects
- Data Warehousing in SAP HANA – Components, Methods, Working & Benefits
- SAP HANA Attribute View – Create Attribute View in 9 Easy Steps
- SAP HANA Analytic View
- SAP HANA Calculation View
- Tables in SAP HANA
- SAP HANA Packages
- Schema in SAP HANA
- How to Create Analytic Privileges in SAP HANA
- SAP HANA Information Composer
- Import and Export in SAP HANA
- Major Components of SAP HANA
- Reporting in SAP HANA
- SAP Bussiness Objects Reporting Tool
- create relational connection in sap hana in 8 steps/
- steps to create olap connection in sap hana/
- How to Connect SAP Lumira with SAP HANA
- Connect Dashboard Designer to SAP HANA & Create Stunning Dashboards
- How to Connect Web Intelligence to SAP HANA in 4 Ways – Seamless Process
- Replication Modes and Types in SAP HANA
- SAP HANA Sidecar Scenario
- SAP HANA Security Guide
- SAP HANA License Management
- Difference between SAP HANA vs SAP S/4 HANA
- What is SAP S/4 HANA?
- S/4HANA Editions
- SAP S/4HANA Lines of Business
- >SAP S/4HANA Deployment Options
- >SAP S/4HANA Overview
- >Introduction of SAP ABAP
- >Overview of SAP ABAP
- >SAP R3 ARCHITECTURE
- >SAP Data Dictionary
- >SAP ABAB Views
- >SAP ABAB database Tables
- >ABAP Constants & Literals
- >ABAP Constants & Literals
- >Types of Tables in SAP
- >Sap Data Object
- >Internal Tables and Work areas
- >Internal Table Operations in SAP ABAP
- >ABAP Report uses Internal tables and Work Areas
- >Select single and Select up to 1 rows
- >Modularization Techniques
- >Techniques of debugging
- >Types Subroutines
- >Reports of Sap Abap
- >Using At Selection Screen Output
- >Select Statements
- >Function Modules
- >Modularization Techniques 2/
- >Subroutines In Sap Abap/
- >Report Of Sap Abap 2
- >Using At Selection Screen Output 2
- >Interactive Reports
- >Interactive Reports Development
- >Interactive Report Using Hide Technique
- >Interactive Report Using Get Cursor Technique
- >Tree List Report
- >Abap Alv Reports/
- >Sap scripts/
- >Purchase Order SAP Script/
- >SAP Smartforms/
- >What is BDC in SAP ? Types of BDC ?/
- >BDC Call transaction for Material Master MM01/
- >SD flow with T-Codes and tables/
- >Introduction to module pool programming in SAP/
- >Functional Specification/
- >ASAP methodology SAP
- >ABAP Development end to end process in Companies
- >SAP SD Sales and Distribution
Sap Abab
Sap FI
- Accounting Entries in SAP FICO
- Define Company in SAP
- Creating new companies
- Assign Company Code
- Business Area
- Functional Area
- Credit Control Area in SAP
- Financial Management in SAP
- Segments in SAP
- SAP Enterprise Structure
- General Ledger Accounting
- Fiscal Year Variant in sap
- Posting Period Variants in SAP
- Posting Period Variant to Company Code
- How to Assign company code to field status variants in SAP
- Posting Keys in SAP
- Tolerance Group for Employees in SAP
- Tolerance Groups For G/L Accounts
- Assign Users to Tolerance Groups in SAP
- Enter Global Parameters for Company Code OBY6
- Define Additional Local Currencies for Company code in SAP System
- Chart of Accounts in FICO
- Assign Company Code to Chart of Accounts in SAP
- How to Create G/L Account Group in SAP
- Define Sample Account Rule Types in SAP
- Data Transfer Rules
- Convolutional and recurrent neural network
- Assign company code to rule type in sap
- Create sample account in sap
- Accounting entries in sap fico sap accounting postings
- Financial statement versions in sap
- TAX Check Calculation Procedure in SAP
- Define New Condition types for Taxes
- How to Assign Country to Calculation Procedure
- Specify Structure for Tax jurisdiction code
- How to Create tax codes in SAP – FTXP "FI"
- Assign Tax Codes for Non-Taxable Transactions in SAP FI
- Define Tax Calculation Procedure for GST in SAP"FI"
- Assign Tax Calculation Procedure to Country in SAP for GST"FI"
- Define Access Sequence in SAP for GST"FI"
- Define Condition Types in SAP for GST"FI"
- How to create customer account groups in sap
- How to create number ranges for customer accounts
- Assign number ranges to customer account groups
- How to Assign Number Ranges to Vendor Account Groups in SAP F1
- How to Create Sundry Creditors GL Account in SAP FI
- How to Define Tolerance group for vendors /Customers
- How to Create Vendor Master Data
- Automatic Payment Program Configuration Steps SAP FI
- Create Vendor Account Groups in SAP
- How to Create Number Ranges for Vendor Accounts in SAP
- Maintain terms of payment SAP
- How to Create Customer master data by XD01
- How to Define Dunning Procedures in SAP
- Copy Reference Chart of Depreciation in SAP
- Assign Chart of Depreciation to Company code in SAP
- Specify account determination asset accountng
- How to create screen layout rules asset accounting
- SAP FI: Create Screen Layout Rules
- SAP FI: Maintain Asset Number Ranges – AS08
- Create Investment Program Types in SAP
- Investment profiles
- How to Investment Program Types to Operative objects in SAP
Replication Modes and Types in SAP HANA
Today, we are going to discuss the replication modes used in SAP HANA system replication. We will be discussing three main types of replication modes, i.e., Synchronous in-memory, Synchronous, Synchronous full sync and Asynchronous replication mode.
So, without wasting any time, let’s start the tutorial.
Replication Modes in SAP HANA
Before we start discussing the three types of replication modes in SAP HANA system replication, we must understand, what is system replication in SAP HANA.
System replication is the process of replicating or copying an SAP HANA database to a secondary location within the same or to an external data center. The SAP database can continuously and simultaneously synchronize with the primary system besides replication.
So, when you register a secondary system to replicate your HANA database, you have to select a replication mode to conduct in the system replication. System replication is primarily to support disaster recovery and high availability in SAP HANA.
There are primarily four types of replication modes for system replication:
- Synchronous in-memory (syncmem)
- Synchronous (sync)
- Synchronous (full sync)
- Asynchronous (async)
Let us learn about all four replication modes in detail, in the sections to follow.
-
Synchronous In-memory Mode
The synchronous in-memory mode is the default replication mode. The primary node waits for a confirmation message by the secondary node upon receiving the log successfully. Until then, the primary node/system commits no transactions.
In other words, the secondary system sends an acknowledgment back to the primary system upon receiving data successfully in its in-memory. The syncmem is an ideal replication mode for solutions focusing on high availability and disaster recovery.
Both the nodes reside on the same data center or in close proximity.
For successful data replication, all the services at both nodes (primary and secondary) must have ACTIVE status. If any one of the services fails, then this might result in data loss and replication failure. No data loss occurs if all the services stay in active mode during the log transfer.
One significant advantage of using this mode is that it offers shortest transaction delays. It is because the primary node halts its transactions until the secondary node sends an acknowledgment. The standard wait time is 30 seconds.
If the primary node does not receive any acknowledgment from the secondary system, it resumes the transactions without replicating data. This ensures the shortest possible transaction delays.
Also, this process is performance-optimized as the speed of disk I/O operations on the secondary system does not affect the primary system’s performance. Thus, the primary system doesn’t have to wait for any disk writing or I/O activity moving to the secondary system.
-
Synchronous Mode
In the synchronous mode of system replication, the primary node waits and halts its transactions till the time the secondary node sends an acknowledgment. The acknowledgment indicates the acceptance of the data log and persistence of the log volumes on its disk.
The main advantage of using sync mode is that it ensures and maintains consistency between the two nodes. The primary node ensures that it will not commit any transaction before the replication on the secondary node completes.
The waiting time of primary node for receiving an acknowledgment from secondary node is 30 seconds. It resumes its transactions without completing the replication process if no “receive” message arrives from the secondary system in 30 secs.
Also, this process is only prone to data loss when the two nodes disconnect during an ongoing replication. However, no data loss occurs when the connection is still intact but the primary node has resumed executing its transactions.
This replication mode is preferable in a high availability system replication setup, where both the nodes reside on the same data center.
-
Synchronous Full Sync Mode
In addition to the normal sync mode, another mode was introduced with SPS08 named full sync. The full sync mode ensures complete data protection, i.e., zero data loss because it blocks the transactions on the primary node until replication successfully completes on the secondary node.
The operations on the primary node are blocked until the secondary node sends an acknowledgment indicating that it has received the data logs and persisted the log volumes on the disk.
The full sync mode of replication is ideal for multi-tier system replication setups as their primary concern is data security and protection. Full sync mode guarantees zero data loss and thus should be used by systems using tier 2 and tier 3 nodes.
To activate the full sync mode in your HANA system, the parameter ‘enable_full_sync’ (in the global.ini file of system replication section) should be Enabled. Also, to completely activate the full sync mode, the connection to the secondary node should be established.
-
Asynchronous Mode
The asynchronous mode, as the name suggests, is where the primary and secondary nodes work asynchronously. In this mode, the primary node does not halt its transactions until the secondary node sends acknowledgment or confirmation.
Instead, the primary node commits a transaction that has been written on the log file of the primary system and sent to the secondary node. It then sends redo log buffers to the secondary system asynchronously.
The asynchronous mode is the best system replication mode in terms of performance as there are no transaction delays and it maintains data consistency throughout the process. Also, it is not necessary for replication mode to wait for the I/O operations on the secondary node.
However, this mode is more vulnerable to data loss as compared to other modes because unexpected failovers and unplanned takeovers may cause data loss.
Apply now for Advanced SAP Course