Single-Node Deployment Where HA Is Required

Single-node deployment is usually applied in OLTP scenarios. You can choose the HA configuration as required.

System Architecture

Figure 1 and Figure 2 show the system architecture in single-node scenario where HA is required.

In the single-node scenario where HA is required, active/standby switchovers can be manually performed, or automatically performed using scripts.

Figure 1 Single-node HA deployment within an AZ

Figure 2 Single-node HA deployment across AZs

The concepts involved in this scenario are the same as those involved in Single-Node Deployment Where HA Is Not Required. The differences between the two deployment modes are as follows: Two independent SAP HANA nodes in the same AZ or different AZs are connected to the SAP HANA Studio for management. The two SAP HANA nodes synchronize data and implement HA using System Replication.

Compared with the mode in which HA is not required in the single-node scenario, the mode in which HA is required has the following requirements:

• You must create two nodes and synchronize time, format disks, and install the SAP HANA software on them.
• The two SAP HANA nodes must connect to SAP HANA Studio.
• You must manually configure HA on the two SAP HANA nodes using System Replication.
• You must configure scripts for the two SAP HANA nodes for active/standby switchovers.

  This only applies to SAP HANA nodes running the OS SUSE Linux Enterprise Server 12 SP1 for SAP.

• In the single-node scenario where SAP HANA nodes are deployed across AZs for HA, the backup volume must be provided by Scalable File Service (SFS) and three ECSs are required. Each ECS is bound to a SCSI disk and iSCSI configuration is required for SBD.