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/virtual-machines/workloads/sap/high-availability-guide-rhel-with-hana-ascs-ers-dialog-instance.md
+18-13Lines changed: 18 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: ampatel
16
16
17
17
# Deploy SAP ASCS/ERS with SAP HANA high availability VMs on Red Hat Enterprise Linux
18
18
19
-
This article describes how to install and configure SAP HANA along with ASCS and ERS instances on the same high availability cluster, running on Red Hat Enterprise Linux (RHEL).
19
+
This article describes how to install and configure SAP HANA along with ASCS/SCS and ERS instances on the same high availability cluster, running on Red Hat Enterprise Linux (RHEL).
20
20
21
21
## References
22
22
@@ -60,7 +60,7 @@ The example shown in this article to describe deployment uses following system i
@@ -72,19 +72,20 @@ The example shown in this article to describe deployment uses following system i
72
72
73
73
### Important consideration for the cost optimization solution
74
74
75
-
* SAP Dialog Instances (PAS and AAS) (like **sapa02** and **sapa04**), can be installed on separate VMs. Install SAP ASCS and ERS with virtual hostnames. To learn more on how to assign virtual hostname to a VM, refer to 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).
76
-
* With HANA DB, ASCS/SCS and ERS deployment in the same cluster setup, the instance number of HANA DB, ASCS and ERS must be different.
77
-
* Consider sizing your VM SKUs appropriately based on the sizing guidelines. You have to factor in the cluster behavior where multiple SAP instances (HANA DB, ASCS and ERS) may run on a single VM, when other VM in the cluster is unavailable.
75
+
* SAP Dialog Instances (PAS and AAS) (like **sapa01** and **sapa02**), should be installed on separate VMs. Install SAP ASCS and ERS with virtual hostnames. To learn more on how to assign virtual hostname to a VM, refer to 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).
76
+
* With 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.
77
+
* Consider sizing your VM SKUs appropriately based on the sizing guidelines. You have to factor in the cluster behavior where multiple SAP instances (HANA DB, ASCS/SCS and ERS) may run on a single VM, when other VM in the cluster is unavailable.
78
78
* You can use different storage (for example, Azure NetApp Files or NFS on Azure Files) to install the SAP ASCS and ERS instances.
79
79
> [!NOTE]
80
80
>
81
81
> For SAP J2EE systems, it's not supported to place `/usr/sap/<SID>/J<nr>` on NFS on Azure Files.
82
+
> DB files like /hana/data and /hana/log are not supported on NFS on Azure Files.
82
83
* To install additional application servers on separate VMs, you can either use NFS shares or local managed disk for instance directory filesystem. If you're installing additional application servers for SAP J2EE system, `/usr/sap/<SID>/J<nr>` on NFS on Azure Files isn't supported.
83
84
* Refer [NFS on Azure Files consideration](high-availability-guide-rhel-nfs-azure-files.md#important-considerations-for-nfs-on-azure-files-shares) and [Azure NetApp Files consideration](high-availability-guide-rhel-netapp-files.md#important-considerations), as same consideration applies for this setup as well.
84
85
85
86
## Pre-requisites
86
87
87
-
The configuration described in this article is an addition to your already configured SAP HANA cluster setup. In this configuration, SAP ASCS and ERS will be installed on a virtual hostname and its instance directory is managed by the cluster.
88
+
The configuration described in this article is an addition to your already configured SAP HANA cluster setup. In this configuration, SAP ASCS/SCS and ERS will be installed on a virtual hostname and its instance directory is managed by the cluster.
88
89
89
90
Install HANA database, set up HSR and Pacemaker cluster by following the documentation [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.
90
91
@@ -122,11 +123,6 @@ Once you've Installed, configured and set-up the **HANA Cluster**, follow the st
122
123
2. Load balancing rule for ERS
123
124
1. Repeat the steps under “5.1” to create load balancing rule for ERS (for example, **ers-lb**).
124
125
125
-
Based on your storage, follow the steps described in below guides to configure `SAPInstance` resource for SAP ASCS and SAP ERS instance in the cluster.
126
-
127
-
* NFS on Azure Files - [Azure VMs high availability for SAP NW on RHEL with NFS on Azure Files](high-availability-guide-rhel-nfs-azure-files.md)
128
-
* Azure NetApp Files - [Azure VMs high availability for SAP NW on RHEL with Azure NetApp Files](high-availability-guide-rhel-netapp-files.md)
129
-
130
126
> [!IMPORTANT]
131
127
>
132
128
> Floating IP is not supported on a NIC secondary IP configuration in load-balancing scenarios. For details see [Azure Load balancer Limitations](../../../load-balancer/load-balancer-multivip-overview.md#limitations). If you need additional IP address for the VM, deploy a second NIC.
@@ -139,8 +135,17 @@ Based on your storage, follow the steps described in below guides to configure `
139
135
>
140
136
> Do not enable TCP timestamps on Azure VMs placed behind Azure Load Balancer. Enabling TCP timestamps will cause the health probes to fail. Set parameter **net.ipv4.tcp_timestamps** to **0**. For details see [Load Balancer health probes](../../../load-balancer/load-balancer-custom-probe-overview.md).
141
137
142
-
Follow the steps in [High availability for SAP NetWeaver on Azure VMs on Red Hat Enterprise Linux with NFS on Azure Files](high-availability-guide-rhel-nfs-azure-files.md) or [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](high-availability-guide-rhel-netapp-files.md) to install, configure and set-up SAP ASCS and ERS instance. Use the above steps for the Load Balancer set-up for SAP ASCS and ERS.
138
+
## SAP ASCS/SCS and ERS Setup
139
+
140
+
Based on your storage, follow the steps described in below guides to configure `SAPInstance` resource for SAP ASCS/SCS and SAP ERS instance in the cluster.
141
+
142
+
* NFS on Azure Files - [Azure VMs high availability for SAP NW on RHEL with NFS on Azure Files](high-availability-guide-rhel-nfs-azure-files#prepare-for-sap-netweaver-installation)
143
+
* Azure NetApp Files - [Azure VMs high availability for SAP NW on RHEL with Azure NetApp Files](high-availability-guide-rhel-netapp-files.md#prepare-for-sap-netweaver-installation)
144
+
145
+
Follow the steps in [High availability for SAP NetWeaver on Azure VMs on Red Hat Enterprise Linux with NFS on Azure Files](high-availability-guide-rhel-nfs-azure-files.md) or [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](high-availability-guide-rhel-netapp-files.md) to install, configure and set up SAP ASCS and ERS instance. Use the above steps for the Load Balancer set-up for SAP ASCS and ERS.
143
146
144
147
## Test the cluster setup
145
148
146
-
Thoroughly test your pacemaker cluster. [Execute the typical failover tests](high-availability-guide-rhel.md#test-the-cluster-setup).
149
+
Thoroughly test your pacemaker cluster.
150
+
*[Execute the typical Netweaver failover tests](high-availability-guide-rhel.md#test-the-cluster-setup).
151
+
*[Execute the typical HANA DB Failover tests](sap-hana-high-availability-rhel#test-the-cluster-setup).
0 commit comments