Chapter 1. Overview
Due to the growing demands on availability, one copy of data is not enough.
To ensure business continuity, a reliable and highly available architecture must replicate data across more than just one replication site. Using multitarget system replication, the primary site can replicate data changes to more than one secondary site. For more information, see SAP HANA Multitarget System Replication.
This document describes how to configure an additional replication site for disaster recovery using SAP HANA Multitarget System Replication on a 2-node cluster, installed as described in Automating SAP HANA Scale-Up System Replication using the RHEL HA Add-On.
A sample configuration looks like this:
The initial setup is as follows:
- Replicate Primary site 1 (DC1) to Secondary site 2 (DC2)
- Replicate Primary site 1 (DC1) to Secondary site 3 (DC3)
If the primary site fails, the primary site switches to secondary site 2 (DC2) and the former primary site 1 (DC1) will become a secondary site.
When failover occurs, this solution ensures that the configured primary site is switched at the third site as well. The configuration after failover is as follows:
- Primary running on DC2
- Secondary running on DC1 (synced from DC2)
- Secondary running on DC3 (synced from DC2)
The SAP HANA instance on remotehost3 will be automatically re-registered to the new primary as long as this instance is up and running during the failover.
This document also describes the example of switching the primary database to the third site.
Please note that further network configuration is required for the connection of the clients to the database. This is not within the scope of this document.
For further information, please check the following:
