Help Center/ SAP Cloud/ SAP HA and DR Guide/ SAP HANA HA and DR/ Public Cloud HA and DR Scenarios/ SAP HANA Single-Node HA (System Replication + Preload on + SUSE HAE)
Updated on 2022-03-04 GMT+08:00
View PDF
Share

SAP HANA Single-Node HA (System Replication + Preload on + SUSE HAE)

SAP HANA HA within an AZ

Scenarios

The public cloud supports SAP HANA HA. In this scenario, deploy the primary and secondary SAP HANA systems in the same AZ and configure the System Replication function of SAP HANA and the SUSE High-Availability Extension (HAE) function to enable automatic switchover and realize HA. This applies to the scenario where a single SAP HANA node is deployed.

  • The System Replication function of SAP HANA provides data replication.
  • Enabling the Preload function of System Replication can preload data to the memory of the secondary system to reduce the switchover time and lower Recovery Time Objective (RTO).
  • Configuring SUSE HAE allows automatic system switchover. The public cloud provides scripts for automatic HAE configuration. For details, see the SAP HANA User Guide (Single Node Deployment).
  • The HA mechanism automatically monitors the health status of the primary SAP HANA system (SAP HANA process, OS, and data replication). When the primary system fails, failover and virtual IP address floating are automatically triggered to achieve HA of the HANA system.

Advantages

Based on the public cloud capabilities, SAP HANA System Replication, and SUSE HAE, SAP HANA provides reliable assurance for your core services.

In the production environment, you are advised to use the SAP HANA HA automatic switchover solution to reduce the RTO. Before using this solution, you need to disable the automatic recovery function of ECSs.

Deployment Plan

Figure 1 shows the deployment plan.

Figure 1 SAP HANA HA within an AZ

Cross-AZ SAP HANA HA

Scenarios

Deploy secondary SAP HANA systems in different AZs.

  • The System Replication function of SAP HANA provides data replication.
  • Enabling the Preload function of System Replication can preload data to the memory of the secondary system to reduce the switchover time and lower Recovery Time Objective (RTO).
  • Configuring SUSE HAE allows automatic system switchover. The public cloud provides scripts for automatic HAE configuration. For details, see the SAP HANA User Guide (Single Node Deployment).
  • The HA mechanism automatically monitors the health status of the AZ where the primary system (SAP HANA process, OS, and data replication) is located. When the AZ where the primary system is located fails, failover and virtual IP address floating are automatically triggered to achieve HA of the HANA system.

Advantages

Based on the public cloud capabilities, SAP HANA System Replication, and SUSE HAE, cross-AZ SAP HANA deployment provides reliable assurance for your core services.

Deployment Plan

Figure 2 shows the deployment plan.

Figure 2 Cross-AZ SAP HANA HA

Scenario 1: SAP HANA HA (System Replication + Preload off + DEV/QAS)

Scenarios

After the SAP HANA HA is deployed, the Preload function of System Replication is disabled. In this case, the secondary system can be used to deploy non-production systems.

  • After the preload function of System Replication is disabled, only a few resources (10%) need to be reserved for the secondary system for receiving synchronization data from the primary system. In addition, non-production systems can be deployed on the secondary system.
  • According to the SAP best practice, non-production systems on the secondary system have to use additional storage resources to avoid the impact on the production system after the switchover of the secondary system.
  • Before the switchover, disable non-production systems on the secondary system to ensure sufficient resources on the secondary system and then manually trigger the switchover.

Advantages

The secondary SAP HANA system can be fully utilized to reduce the overall cost based on public cloud capabilities and SAP HANA HA mechanism.

In the production environment, you are advised to use the SAP HANA single-node HA automatic switchover solution to reduce the RTO. Before using this solution, you need to disable the HA configuration function of ECSs.

Deployment Plan

Figure 3 shows the deployment plan.

Figure 3 SAP HANA HA within an AZ (System Replication + Preload off + DEV/QAS)