Skip to Content

SAP HANA High Availability and Disaster Recovery Series #1

This is the first article of my new SAP HANA High Availability and Disaster Recovery (DR) series.

My purpose is to deep-dive into the entire SAP HANA high availability (HA), fault recovery (FR) and disaster recovery (DR) concept including the high-level overview of ALL available HA, FR and DR options, different configuration and setup methods and key benefits and trade-offs of each technology. I aim to provide deeper, clear and broader information in SAP HANA HA and DR technologies unlike the majority of confusing and contradictory information available on the internet. At the end of the day, you will be able to compare all available DR, FR and HA options, learn how to ensure your system’s operational continuity and decide the most suitable approach for your own data center readiness scenario to meet the business requirements.

This very first article is an introduction to the series and will mostly cover to the areas I am going to explain. Herewith some of the current SAP HANA capabilities from data center readiness point of view:

Before we start, we need to understand what our KPIs are when it comes to HA and DR from business continuity planning perspective, so we can make better-informed decisions. There are two main objectives:

Recovery Point Objective (RPO): Maximum tolerable period of time which operational data is lost without the ability to recover. This is your business continuity plan’s maximum allowable threshold for data loss. The RPO is expressed backwards in time (that is, into the past) from the point the failure occurs.

Recovery Time Objective (RTO): Maximum permissible time it takes to recover the system after a disaster (or disruption) for system operations to resume. This objective can include the time for trying to fix the problem without recovery options, the recovery itself and testing of services before handing over to the business users.

These two KPIs help system architects choose optimal high availability and disaster recovery technologies and procedures in SAP HANA platform.

Our target RPO for business-critical systems should be ZERO DATA LOSS and minimum possible RTO in all production environments. And the key requirement to achieve these is to apply the most effective data replication method in both HA and DR scenarios.

Agenda starting from the second article:

  • Single Points of Failure
  • High Availability Options
  • Fault Recovery Support
  • Disaster Recovery Support
  • Service Auto-Restart
  • Host Auto-Failover (with scale-out scenario, heartbeat and fencing capabilities)
  • Storage Replication (remote networked storage, both
  • System Replication (Covering all replication modes AND both operation modes in detail)
  • Backup and Recovery (filesystem, 3rd party backup tools, snapshots)
  • Near-Zero Downtime Maintenance
  • Comparison

Do you have any other related concept you want to learn more in SAP HANA HA & DR scenario? Leave a comment below, I would love to help you and learn from you as much as I can!

Feel free to share!

If you liked this post, you might like these relevant posts:
Choosing the Most Effective Approach for Technical Migration to SAP HANA
SAP HANA Multitenant Database Architecture
Choosing the right HANA Database Architecture

You must be Logged on to comment or reply to a post.

    Nice document ,

    Presently I am setting up a DR with  Multi tier System Replication ,  HANA DB is SP12

    According to SAP 2303243 - SAP HANA Multi-tier System Replication from SPS12 on-words below combination is supported.

    Replication Mode Combinations

    Tier1 to Tier 2= SYNCMEM

    Tier 2 to Tier 3=SYNCMEM

    Note "If the connection to tier 3 is too slow and the ASYNC replication buffer (an intermediate memory buffer) is running full, ASYNC replication can have an impact on the primary.----From, so we dont want use to ASYNC

    Do you see any issues if I used SYNCMEM among the Datacenters.





    • Hi Ravikiran,

      Sorry I don't check SAP blogs very regularly, sorry for my late answer. I usually am active on LinkedIn.

      Based on your description, it seems Tier 2 is HA and Tier 3 is for DR is it correct?

      If so, it would be better to configure ASYNC replication mode for DR site, especially if it is distant data center (>100km between sites). But you need to ensure that you have a fast network connection between Tier-2 and Tier-3 so you won't have an memory buffer issues.

      Kind regards,



  • Hello Alper,


    Very useful article, thanks for sharing! I have one question about HANA HA. If we want to use SUSE HA between two sets of BW on HANA system, let's say each one has 5 nodes. If it is possible to make the automate failover happen? BTW, each one has own storage.


    Best regards,


    • Hi Yue,

      Thanks for the comment and sorry for my late response as I usually am more active on LinkedIn. Is this a scale-out architecture? If so, automated failover is handled by SAP HANA nameserver. If you are planning to configure System Replication, then you need to use the external cluster manager (provided by SUSE) to implement automated failover.

      Kind regards,