You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/workloads/disaster-recovery-sap-hana.md
+26-19Lines changed: 26 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,40 +1,42 @@
1
1
---
2
-
title: Add HSR third site to HANA Pacemaker cluster
3
-
description: Learn how to extend a highly available SAP HANA solution with a third site for disaster recovery.
2
+
title: Add additional secondary sites to HANA Pacemaker cluster
3
+
description: Learn how to extend a highly available SAP HANA solution with additional sites for disaster recovery.
4
4
author: msftrobiro
5
5
ms.author: robiro
6
6
ms.service: sap-on-azure
7
7
ms.subservice: sap-vm-workloads
8
8
ms.topic: how-to
9
-
ms.date: 01/16/2024
9
+
ms.date: 10/29/2024
10
10
ms.custom: template-how-to-pattern
11
11
---
12
12
13
-
# Add an HSR third site to a HANA Pacemaker cluster
13
+
# Add additional secondary sites to a HANA Pacemaker cluster
14
14
15
-
This article describes requirements and setup of a third HANA replication site to complement an existing Pacemaker cluster. Both SUSE Linux Enterprise Server (SLES) and RedHat Enterprise Linux (RHEL) specifics are covered.
15
+
This article describes the requirements and setup for configuring additional secondary HANA replication site to complement an existing Pacemaker cluster. Both SUSE Linux Enterprise Server (SLES) and RedHat Enterprise Linux (RHEL) specifics are covered.
16
16
17
17
## Overview
18
18
19
-
SAP HANA supports system replication (HSR) with more than two sites connected. You can add a third site to an existing HSR pair, managed by Pacemaker in a highly available setup. You can deploy the third site in a second Azure region for disaster recovery (DR) purposes.
19
+
SAP HANA supports system replication (HSR) with more than two connected sites. You can configure additional sites to an existing HSR pair that Pacemaker manages in a highly available setup. For example, you can deploy these additional sites in a second Azure region for disaster recovery (DR) purposes.
20
20
21
-
Pacemaker and the HANA cluster resource agent manage the first two sites. The Pacemaker cluster doesn't control the third site.
21
+
Pacemaker and the HANA cluster resource agent manage only the first two sites in HSR. The additional sites aren't controlled by the Pacemaker cluster.
22
22
23
-
SAP HANA supports a third system replication site in two modes:
23
+
SAP HANA supports additional secondary sites system replication in two modes:
24
24
25
-
-[Multitarget](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/ba457510958241889a459e606bbcf3d3.html) replicates data changes from primary to more than one target system. The third site is connected to primary replication in a star topology.
26
-
-[Multitier](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/f730f308fede4040bcb5ccea6751e74d.html) is a two-tier replication. A cascading, or chained, setup of three different HANA tiers. The third site connects to the secondary.
25
+
-[Multitarget](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/ba457510958241889a459e606bbcf3d3.html) replicates data changes from primary to more than one target system. The additional sites are connected to primary replication in a star topology.
26
+
-[Multitier](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/f730f308fede4040bcb5ccea6751e74d.html) is a cascading, or chained, set up of HANA system replication. The third site connects to the secondary.
27
27
28
28
For more conceptual details about HANA HSR within one region and across different regions, see [SAP HANA availability across Azure regions](./sap-hana-availability-across-regions.md#combine-availability-within-one-region-and-across-regions).
29
29
30
30
## Prerequisites for SLES
31
31
32
-
Requirements for a third HSR site are different for HANA scale-up and HANA scale-out.
32
+
Requirements for additional HSR sites are different for HANA scale-up and HANA scale-out.
33
33
34
34
> [!NOTE]
35
-
> Requirements in this article are only valid for a Pacemaker-enabled landscape. Without Pacemaker, SAP HANA version requirements apply to the chosen replication mode.
36
-
> Pacemaker and the HANA cluster resource agent manage only two sites. The third HSR site isn't controlled by the Pacemaker cluster.
35
+
>
36
+
> - Requirements in this article are only valid for a Pacemaker-enabled landscape. Without Pacemaker, SAP HANA version requirements apply to the chosen replication mode.
37
+
> - Pacemaker and the HANA cluster resource agent manage only two sites. The additional HSR site isn't controlled by the Pacemaker cluster.
37
38
39
+
- SUSE supports maximum of one additional system replication site to an SAP HANA database outside the Pacemaker cluster.
38
40
-**Both scale-up and scale-out**: SAP HANA SPS 04 or newer is required to use multitarget HSR with a Pacemaker cluster.
39
41
-**Both scale-up and scale-out**: Maximum of one SAP HANA system replication connected from outside the Linux cluster.
40
42
-**HANA scale-out only**: SLES 15 SP1 or higher.
@@ -43,20 +45,25 @@ Requirements for a third HSR site are different for HANA scale-up and HANA scale
43
45
44
46
## Prerequisites for RHEL
45
47
46
-
Requirements for a third HSR site are different for HANA scale-up and HANA scale-out.
48
+
Requirements for additional HSR sites are different for HANA scale-up and HANA scale-out.
47
49
48
50
> [!NOTE]
49
-
> Requirements in this article are only valid for a Pacemaker-enabled landscape. Without Pacemaker, SAP HANA version requirements apply for the chosen replication mode.
50
-
> Pacemaker and the HANA cluster resource agent manage only two sites. The third HSR site isn't controlled by the Pacemaker cluster.
51
+
>
52
+
> - Requirements in this article are only valid for a Pacemaker-enabled landscape. Without Pacemaker, SAP HANA version requirements apply for the chosen replication mode.
53
+
> - Pacemaker and the HANA cluster resource agent manage only two sites. The additional HSR sites isn't controlled by the Pacemaker cluster.
51
54
55
+
- RedHat supports one or more additional system replication sites to an SAP HANA database outside the Pacemaker cluster.
52
56
-**HANA scale-up only**: See RedHat [support policies for RHEL HA clusters](https://access.redhat.com/articles/3397471) for details on the minimum OS, SAP HANA, and cluster resource agents version.
53
57
-**HANA scale-out only**: HANA multitarget replication isn't supported on Azure with a Pacemaker cluster.
54
58
59
+
> [!Tip]
60
+
> The configuration illustrates how to setup third site outside Pacemaker cluster. On RHEL, if you have more than one additional sites outside the Pacemaker cluster, you would need to extend the setup to those other sites as well.
61
+
55
62
## HANA scale-up: Add HANA multitarget system replication for DR purposes
56
63
57
-
With SAP HANA HA hooks SAPHanaSR/susHanaSR for [SLES](./sap-hana-high-availability.md#implement-hana-resource-agents) and [RHEL](./sap-hana-high-availability-rhel.md#implement-the-python-system-replication-hook-saphanasr), you can add a third node for DR purposes. The Pacemaker environment is aware of a HANA multitarget DR setup.
64
+
With SAP HANA HA hooks SAPHanaSR/susHanaSR for [SLES](./sap-hana-high-availability.md#implement-hana-resource-agents) and [RHEL](./sap-hana-high-availability-rhel.md#implement-the-python-system-replication-hook-saphanasr), you can add additional sites to HANA system replication. The Pacemaker environment is aware of a HANA multitarget setup.
58
65
59
-
Failure of the third node won't trigger any cluster action. The cluster detects the replication status of connected sites and the monitored attribute for the third site can change between `SOK` and `SFAIL` states. Any takeover tests to the third/DR site or executing your DR exercise process should first place the cluster resources into maintenance mode to prevent any undesired cluster action.
66
+
Failure of additional sites doesn't trigger any cluster action. The cluster detects the replication status of connected sites and the monitored attribute for the third site can change between `SOK` and `SFAIL` states. Any takeover tests to the additional site or executing your DR exercise process should first place the cluster resources into maintenance mode to prevent any undesired cluster action.
60
67
61
68
The following example shows a multitarget system replication system. For more information, see [SAP documentation](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/2e6c71ab55f147e19b832565311a8e4e.html).
62
69
@@ -115,7 +122,7 @@ The following example shows a multitarget system replication system. For more in
115
122
116
123
With the SAP HANA HA provider [SAPHanaSrMultiTarget](./sap-hana-high-availability-scale-out-hsr-suse.md#implement-hana-ha-hooks-saphanasrmultitarget-and-suschksrv), you can add a third HANA scale-out site. This third site is often used for DR in another Azure region. The Pacemaker environment is aware of a HANA multitarget DR setup. This section applies to systems running Pacemaker on SUSE only. See the "Prerequisites" section in this document for details.
117
124
118
-
Failure of the third node won't trigger any cluster action. The cluster detects the replication status of connected sites and the monitored attribute for the third site can change between the `SOK` and `SFAIL` states. Any takeover tests to the third/DR site or executing your DR exercise process should first place the cluster resources into maintenance mode to prevent any undesired cluster action.
125
+
Failure of the third node doesn't trigger any cluster action. The cluster detects the replication status of connected sites and the monitored attribute for the third site can change between the `SOK` and `SFAIL` states. Any takeover tests to the third/DR site or executing your DR exercise process should first place the cluster resources into maintenance mode to prevent any undesired cluster action.
119
126
120
127
The following example shows a multitarget system replication system. For more information, see [SAP documentation](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/2e6c71ab55f147e19b832565311a8e4e.html).
121
128
0 commit comments