HANA high-availability pair
This scenario deploys a single-node HANA instance in two sites (primary and secondary), replicated on database level via HANA System Replication (HSR). This scenario is known as "high-availability pair" or "HA pair."
Table of contents
- This scenario already configures all resources required for the Pacemaker HA cluster, including:
- STONITH by device (SBD), via iSCSI target server
- SAPHanaSR and SAPHanaTopology Pacemaker resource agents (to facilitate HSR failover)
- azure-events Pacemaker resource agent (to anticipate scheduled maintenance events and trigger graceful failover)
- In this design, the SBD device uses a iSCSI target server on an additional VM; while this is optional, it allows for faster failover. For more details, please refer to the reference architecture of high-availability VM landscapes using Pacemaker on SuSE Linux Enterprise Server (SLES).
- At present, this HANA high-availability scenario is only supported for Azure VM deployments using SuSE Linux Enterprise Server (SLES) 12.3 or higher.
- For additional details on the underlying implementation, please see the documentation of the reference architecture.
- If you don't have a high-availability requirement, you can just deploy the HANA single-node scenario.
The following options can be customized in the single-node scenario:
|HANA version||Which version of HDB Server to install|
|HANA 1.0 SPS12 (PL13 or higher)||
|HANA 2.0 SPS2 or higher||
|Database containers *||Whether to install HDB with single or multiple database containers (tenants)|
|Single container (HANA 1.0 only)||
|Multi-database containers (MDC)||
|Bastion host *||Whether to deploy a bastion host ("jump box") through which the HANA VM can be accessed|
|No bastion host||
|Windows bastion host (incl. HANA Studio)||
|Linux bastion host (incl. HANA Studio)||
|SAP Applications||Which SAP applications to install on top of HANA (if any)|
|SAP HANA Cockpit (requires XSA)||
|SHINE Demo Content (requires XSA)||
|WebIDE (requires XSA)||
(Note: Features marked with an * are work in progress and not fully available yet.)
If you haven't already done so, please make sure you prepare your Azure Cloud Shell.
(Note: Please review the list of SAP downloads; depending on which features and applications you would like to include in your HANA installation, you may need additional packages.)
In your Azure Cloud Shell, change into the directory for the HANA high-availability pair:
terraform.tfvarsfile for your deployment. You can use the provided Boilerplate template for high-availability pair scenarios as a starting point and adjust the variables according to your requirements.
(Note: You need to rename the boilerplate template from
terraform.tfvars before you can use it.)
Should you wish to delete your HANA high-availability pair at a later point, you can simply follow the general instructions on the overview page.