Skip to content

Commit 7c8fbb5

Browse files
Xelu86Xelu86
committed
Freshness
1 parent 6b51ea9 commit 7c8fbb5

1 file changed

Lines changed: 54 additions & 50 deletions

File tree

‎articles/sap/workloads/high-availability-guide-rhel-with-hana-ascs-ers-dialog-instance.md‎

Lines changed: 54 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
title: Deploy SAP ASCS/SCS and SAP ERS with SAP HANA high-availability VMs on RHEL | Microsoft Docs
3-
description: Configure SAP ASCS/SCS and SAP ERS with SAP HANA high-availability VMs on RHEL.
2+
title: Deploy SAP ASCS/SCS and SAP ERS with SAP HANA high-availability VMs on RHEL
3+
description: Learn how to configure SAP ASCS/SCS and SAP ERS with SAP HANA high-availability VMs on RHEL.
44
services: virtual-machines-linux,virtual-network,storage
5-
author: apmsft
6-
manager: juergent
75
ms.service: sap-on-azure
86
ms.subservice: sap-vm-workloads
9-
ms.topic: tutorial
10-
ms.date: 06/19/2024
7+
ms.topic: how-to
8+
manager: juergent
9+
author: apmsft
1110
ms.author: ampatel
11+
ms.date: 03/02/2026
1212
ms.custom: sfi-image-nochange
1313
# Customer intent: As a system administrator, I want to deploy SAP ASCS/SCS and ERS with SAP HANA in a high-availability configuration on RHEL, so that I can optimize resource usage and ensure uninterrupted service for my SAP environment.
1414
---
@@ -17,74 +17,49 @@ ms.custom: sfi-image-nochange
1717

1818
This article describes how to install and configure SAP HANA along with ABAP SAP Central Services (ASCS)/SAP Central Services (SCS) and Enqueue Replication Server (ERS) instances on the same high-availability cluster running on Red Hat Enterprise Linux (RHEL).
1919

20-
## References
21-
22-
* [Configuring SAP S/4HANA ASCS/ERS with Standalone Enqueue Server 2 (ENSA2) in Pacemaker](https://access.redhat.com/articles/3974941)
23-
* [Configuring SAP NetWeaver ASCS/ERS ENSA1 with Standalone Resources in RHEL 7.5+ and RHEL 8](https://access.redhat.com/articles/3569681)
24-
* SAP Note [1928533](https://launchpad.support.sap.com/#/notes/1928533), which has:
25-
* A list of Azure virtual machine (VM) sizes that are supported for the deployment of SAP software.
26-
* Important capacity information for Azure VM sizes.
27-
* Supported SAP software and operating system (OS) and database combinations.
28-
* Required SAP kernel version for Windows and Linux on Azure.
29-
* SAP Note [2015553](https://launchpad.support.sap.com/#/notes/2015553) lists prerequisites for SAP-supported SAP software deployments in Azure.
30-
* SAP Note [2002167](https://launchpad.support.sap.com/#/notes/2002167) lists the recommended OS settings for Red Hat Enterprise Linux 7.x.
31-
* SAP Note [2772999](https://launchpad.support.sap.com/#/notes/2772999) lists the recommended OS settings for Red Hat Enterprise Linux 8.x.
32-
* SAP Note [2009879](https://launchpad.support.sap.com/#/notes/2009879) has SAP HANA guidelines for Red Hat Enterprise Linux.
33-
* SAP Note [2178632](https://launchpad.support.sap.com/#/notes/2178632) has detailed information about all monitoring metrics reported for SAP in Azure.
34-
* SAP Note [2191498](https://launchpad.support.sap.com/#/notes/2191498) has the required SAP Host Agent version for Linux in Azure.
35-
* SAP Note [2243692](https://launchpad.support.sap.com/#/notes/224362) has information about SAP licensing on Linux in Azure.
36-
* SAP Note [1999351](https://launchpad.support.sap.com/#/notes/1999351) has more troubleshooting information for the Azure Enhanced Monitoring Extension for SAP.
37-
* [SAP Community Wiki](https://wiki.scn.sap.com/wiki/display/HOME/SAPonLinuxNotes) has all required SAP Notes for Linux.
38-
* [Azure Virtual Machines planning and implementation for SAP on Linux](planning-guide.md)
39-
* [Azure Virtual Machines deployment for SAP on Linux](deployment-guide.md)
40-
* [Azure Virtual Machines DBMS deployment for SAP on Linux](dbms-guide-general.md)
41-
* [SAP Netweaver in Pacemaker cluster](https://access.redhat.com/articles/3150081)
42-
* General RHEL documentation:
43-
* [High-Availability Add-On Overview](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_overview/index)
44-
* [High-Availability Add-On Administration](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_administration/index)
45-
* [High Availability Add-On Reference](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/index)
46-
* Azure-specific RHEL documentation:
47-
* [Support Policies for RHEL High-Availability Clusters - Microsoft Azure Virtual Machines as Cluster Members](https://access.redhat.com/articles/3131341)
48-
* [Installing and Configuring a Red Hat Enterprise Linux 7.4 (and later) High-Availability Cluster on Microsoft Azure](https://access.redhat.com/articles/3252491)
49-
5020
## Overview
5121

52-
This article describes the cost-optimization scenario where you deploy SAP HANA, SAP ASCS/SCS, and SAP ERS instances in the same high-availability setup. To minimize the number of VMs for a single SAP system, you want to install SAP ASCS/SCS and SAP ERS on the same hosts where SAP HANA is running. With SAP HANA being configured in a high-availability cluster setup, you want SAP ASCS/SCS and SAP ERS also to be managed by cluster. The configuration is basically an addition to an already configured SAP HANA cluster setup. In this setup, SAP ASCS/SCS and SAP ERS are installed on a virtual host name, and its instance directory is managed by the cluster.
22+
This article describes the cost-optimization scenario where you deploy SAP HANA, SAP ASCS/SCS, and SAP ERS instances in the same high-availability setup. To minimize the number of virtual machines (VMs) for a single SAP system, you want to install SAP ASCS/SCS and SAP ERS on the same hosts where SAP HANA is running. With SAP HANA configured in a high-availability cluster, you also want to manage SAP ASCS/SCS and SAP ERS by the cluster. The configuration is basically an addition to an already configured SAP HANA cluster setup. In this setup, SAP ASCS/SCS and SAP ERS are installed on a virtual host name. The cluster manages the instance directory.
5323

5424
The presented architecture showcases [NFS on Azure Files](../../storage/files/files-nfs-protocol.md) or [Azure NetApp Files](../../azure-netapp-files/azure-netapp-files-introduction.md) for a highly available instance directory for the setup.
5525

5626
The example shown in this article to describe deployment uses the following system information:
5727

5828
| Instance name | Instance number | Virtual host name | Virtual IP (Probe port) |
5929
| ----------------------------------- | --------------- | ---------------- | ----------------------- |
60-
| SAP HANA DB | 03 | saphana | 10.66.0.13 (62503) |
61-
| ABAP SAP Central Services (ASCS) | 00 | sapascs | 10.66.0.20 (62000) |
62-
| Enqueue Replication Server (ERS) | 01 | sapers | 10.66.0.30 (62101) |
30+
| SAP HANA DB | 03 | `saphana` | 10.66.0.13 (62503) |
31+
| ABAP SAP Central Services (ASCS) | 00 | `sapascs` | 10.66.0.20 (62000) |
32+
| Enqueue Replication Server (ERS) | 01 | `sapers` | 10.66.0.30 (62101) |
6333
| SAP HANA system identifier | HN1 | --- | --- |
6434
| SAP system identifier | NW1 | --- | --- |
6535

6636
> [!NOTE]
6737
> Install SAP dialog instances (PAS and AAS) on separate VMs.
6838
69-
![Diagram that shows the architecture of an SAP HANA, SAP ASCS/SCS, and ERS installation within the same cluster.](media/high-availability-guide-rhel/high-availability-rhel-hana-ascs-ers-dialog-instance.png)
39+
![A diagram that shows the architecture of an SAP HANA, SAP ASCS/SCS, and ERS installation within the same cluster.](media/high-availability-guide-rhel/high-availability-rhel-hana-ascs-ers-dialog-instance.png)
7040

7141
### Important considerations for the cost-optimization solution
7242

7343
* SAP dialog instances (PAS and AAS) (like **sapa01** and **sapa02**) should be installed on separate VMs. Install SAP ASCS and ERS with virtual host names. To learn more about how to assign a virtual host name to a VM, see the blog [Use SAP Virtual Host Names with Linux in Azure](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/use-sap-virtual-host-names-with-linux-in-azure/ba-p/3251593).
7444
* With an HANA DB, ASCS/SCS, and ERS deployment in the same cluster setup, the instance number of HANA DB, ASCS/SCS, and ERS must be different.
75-
* Consider sizing your VM SKUs appropriately based on the sizing guidelines. You must factor in the cluster behavior where multiple SAP instances (HANA DB, ASCS/SCS, and ERS) might run on a single VM when another VM in the cluster is unavailable.
45+
* Consider sizing your VM SKUs appropriately based on the sizing guidelines. You must factor in the cluster behavior where multiple SAP instances might run on a single VM when another VM in the cluster is unavailable. Such as HANA DB, ASCS/SCS, and ERS.
7646
* You can use different storage (for example, Azure NetApp Files or NFS on Azure Files) to install the SAP ASCS and ERS instances.
47+
7748
> [!NOTE]
78-
> For SAP J2EE systems, it's not supported to place `/usr/sap/<SID>/J<nr>` on NFS on Azure Files.
79-
> Database file systems like /hana/data and /hana/log aren't supported on NFS on Azure Files.
49+
> For SAP J2EE systems, using `/usr/sap/<SID>/J<nr>` on NFS on Azure Files isn't supported. Database file systems like `/hana/data` and `/hana/log` aren't supported on NFS on Azure Files.
50+
8051
* To install more application servers on separate VMs, you can either use NFS shares or a local managed disk for an instance directory file system. If you're installing more application servers for SAP J2EE system, `/usr/sap/<SID>/J<nr>` on NFS on Azure Files isn't supported.
8152
* See [NFS on Azure Files considerations](high-availability-guide-rhel-nfs-azure-files.md#important-considerations-for-nfs-on-azure-files-shares) and [Azure NetApp Files considerations](high-availability-guide-rhel-netapp-files.md#important-considerations) because the same considerations apply to this setup.
8253

8354
## Prerequisites
8455

85-
The configuration described in this article is an addition to your already-configured SAP HANA cluster setup. In this configuration, an SAP ASCS/SCS and ERS instance are installed on a virtual host name. The instance directory is managed by the cluster.
56+
The configuration described in this article is an addition to your already-configured SAP HANA cluster setup. In this configuration, an SAP ASCS/SCS and ERS instance are installed on a virtual host name. The cluster manages the instance directory.
8657

87-
Install a HANA database and set up a HANA system replication (HSR) and Pacemaker cluster by following the steps in [High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux](sap-hana-high-availability-rhel.md) or [High availability of SAP HANA Scale-up with Azure NetApp Files on Red Hat Enterprise Linux](sap-hana-high-availability-netapp-files-red-hat.md) depending on what storage option you're using.
58+
* Install the HANA database.
59+
* Configure HANA system replication (HSR).
60+
* Configure a Pacemaker cluster.
61+
62+
Follow the steps in [High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux](sap-hana-high-availability-rhel.md). Depending on what storage option you're using, see [High availability of SAP HANA Scale-up with Azure NetApp Files on Red Hat Enterprise Linux](sap-hana-high-availability-netapp-files-red-hat.md).
8863

8964
After you install, configure, and set up the **HANA Cluster**, follow the next steps to install ASCS and ERS instances.
9065

@@ -106,12 +81,11 @@ This article assumes that you already configured the load balancer for a HANA cl
10681
1. **Interval**: Enter **5**.
10782
1. **Probe Threshold**: Enter **2**.
10883
1. **Idle timeout (minutes)**: Enter **30**.
109-
1. **Enable
110-
2. IP**: Select this option.
84+
1. **Enable Floating IP**: Select this option.
11185

112-
The health probe configuration property `numberOfProbes`, otherwise known as **Unhealthy threshold** in the Azure portal, isn't respected. To control the number of successful or failed consecutive probes, set the property `probeThreshold` to `2`. It's currently not possible to set this property by using the Azure portal. Use either the [Azure CLI](/cli/azure/network/lb/probe) or the [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig) command.
86+
The health probe configuration property `numberOfProbes`, otherwise known as **Unhealthy threshold** in the Azure portal, isn't respected. To control the number of successful or failed consecutive probes, set the property `probeThreshold` to `2`. It's currently not possible to set this property by using the Azure portal. Use either the [Azure CLI](/cli/azure/network/lb/probe) or the [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig) commands.
11387

114-
When VMs without public IP addresses are placed in the back-end pool of an internal (no public IP address) Standard Azure Load Balancer instance, there's no outbound internet connectivity unless more configuration is performed to allow routing to public endpoints. For steps on how to achieve outbound connectivity, see [Public endpoint connectivity for virtual machines using Azure Standard Load Balancer in SAP high-availability scenarios](high-availability-guide-standard-load-balancer-outbound-connections.md).
88+
When VMs without public IP addresses are placed in the back-end pool of an internal Standard Azure Load Balancer, they don't have outbound internet connectivity by default. Configuration is also required to enable routing to public endpoints. For steps on how to achieve outbound connectivity, see [Public endpoint connectivity for virtual machines using Azure Standard Load Balancer in SAP high-availability scenarios](high-availability-guide-standard-load-balancer-outbound-connections.md).
11589

11690
> [!IMPORTANT]
11791
> Don't enable TCP timestamps on Azure VMs placed behind Azure Load Balancer. Enabling TCP timestamps causes the health probes to fail. Set the parameter `net.ipv4.tcp_timestamps` to `0`. For more information, see [Load Balancer health probes](../../load-balancer/load-balancer-custom-probe-overview.md).
@@ -129,3 +103,33 @@ Thoroughly test your Pacemaker cluster:
129103

130104
* [Run the typical Netweaver failover tests](high-availability-guide-rhel.md#test-the-cluster-setup)
131105
* [Run the typical HANA DB failover tests](sap-hana-high-availability-rhel.md#test-the-cluster-setup)
106+
107+
## References
108+
109+
* [Configuring SAP S/4HANA ASCS/ERS with Standalone Enqueue Server 2 (ENSA2) in Pacemaker](https://access.redhat.com/articles/3974941)
110+
* [Configuring SAP NetWeaver ASCS/ERS ENSA1 with Standalone Resources in RHEL 7.5+ and RHEL 8](https://access.redhat.com/articles/3569681)
111+
* SAP Note [1928533](https://launchpad.support.sap.com/#/notes/1928533), which has:
112+
* A list of Azure VM sizes that are supported for the deployment of SAP software.
113+
* Important capacity information for Azure VM sizes.
114+
* Supported SAP software and operating system (OS) and database combinations.
115+
* Required SAP kernel version for Windows and Linux on Azure.
116+
* SAP Note [2015553](https://launchpad.support.sap.com/#/notes/2015553) has prerequisites for SAP-supported SAP software deployments in Azure.
117+
* SAP Note [2002167](https://launchpad.support.sap.com/#/notes/2002167) has the recommended OS settings for Red Hat Enterprise Linux 7.x.
118+
* SAP Note [2772999](https://launchpad.support.sap.com/#/notes/2772999) has the recommended OS settings for Red Hat Enterprise Linux 8.x.
119+
* SAP Note [2009879](https://launchpad.support.sap.com/#/notes/2009879) has SAP HANA guidelines for Red Hat Enterprise Linux.
120+
* SAP Note [2178632](https://launchpad.support.sap.com/#/notes/2178632) has detailed information about all monitoring metrics reported for SAP in Azure.
121+
* SAP Note [2191498](https://launchpad.support.sap.com/#/notes/2191498) has the required SAP Host Agent version for Linux in Azure.
122+
* SAP Note [2243692](https://launchpad.support.sap.com/#/notes/224362) has information about SAP licensing on Linux in Azure.
123+
* SAP Note [1999351](https://launchpad.support.sap.com/#/notes/1999351) has more troubleshooting information for the Azure Enhanced Monitoring Extension for SAP.
124+
* [SAP Community Wiki](https://wiki.scn.sap.com/wiki/display/HOME/SAPonLinuxNotes) has all required SAP Notes for Linux.
125+
* [Azure Virtual Machines planning and implementation for SAP on Linux](planning-guide.md)
126+
* [Azure Virtual Machines deployment for SAP on Linux](deployment-guide.md)
127+
* [Azure Virtual Machines DBMS deployment for SAP on Linux](dbms-guide-general.md)
128+
* [SAP Netweaver in Pacemaker cluster](https://access.redhat.com/articles/3150081)
129+
* General RHEL documentation:
130+
* [High-Availability Add-on Overview](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_overview/index)
131+
* [High-Availability Add-on Administration](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_administration/index)
132+
* [High Availability Add-On Reference](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/index)
133+
* Azure-specific RHEL documentation:
134+
* [Support Policies for RHEL High-Availability Clusters - Microsoft Azure Virtual Machines as Cluster Members](https://access.redhat.com/articles/3131341)
135+
* [Installing and Configuring a Red Hat Enterprise Linux 7.4 (and later) High-Availability Cluster on Microsoft Azure](https://access.redhat.com/articles/3252491)

0 commit comments

Comments
 (0)