Understanding SAP HANA Deployment Options, Scenarios, and High‑Availability Strategies

SAP is the world’s largest enterprise‑software vendor, offering ERP, SRM, BI and other applications, while SAP HANA is its high‑performance in‑memory database product.

HANA can be deployed as an integrated appliance or in the cloud, providing a revolutionary platform for real‑time analytics and applications by combining data processing, analytics and business‑logic in memory.

Hardware partners offer certified HANA appliances; deployment options include cloud services (HANA One, HANA Enterprise Cloud) and on‑premise solutions (HANA appliance, B1A, B1H).

Typical SAP HANA application scenarios:

Business Warehouse on HANA (BWoH) : OLAP workloads such as BW, BPC, BI, BO.

Business Suite on HANA (BoH) / S/4 HANA : OLTP workloads like ECC, SRM, CRM, HRM, EWM, Hybris.

Common SAP modules:

OLTP: SAP Business Suite (ECC, SRM, MDM, PI/PO, CRM, HRM, EWM, Hybris).

OLAP: Data Warehouse (BW, BPC, BI, FC).

Key product abbreviations:

SAP Business One (B1) is a low‑cost, easy‑to‑implement ERP for SMEs, typically deployed on a two‑node server where application and database reside together.

SoH (SAP Business Suite on HANA) runs on 4‑, 8‑, 16‑/32‑node configurations, usually scale‑up single nodes.

BWoH (SAP Business Warehouse on HANA) supports 4‑ or 8‑node setups and can be deployed as scale‑up single nodes or scale‑out clusters.

Scale‑Up vs. Scale‑Out:

Scale‑Up adds CPU and memory to a single node, offering performance advantages, high resource utilization, and lower cost for a given hardware vendor, but is limited by single‑node capacity and HA constraints.

Scale‑Out adds more nodes, providing horizontal scalability for large data volumes, automatic data distribution, and high‑availability via multiple standby nodes, though it incurs network overhead and higher infrastructure costs.

Certified hardware configurations can be found on the SAP certification website.

Tailored Data Center Integration (TDI): TDI allows customers to use existing certified servers and storage to build a HANA system, reducing cost but leaving performance guarantees to the customer.

HANA supports virtualization platforms such as vSphere and Huawei FusionSphere, provided both the hardware and the hypervisor are SAP‑certified.

Storage sizing for TDI follows the physical RAM of the HANA host; production logs should use SSDs, while development/test logs may use SAS drives.

Clustered HANA solutions are currently limited to Business Warehouse scenarios; OLTP workloads require single‑node appliances unless data volume exceeds the memory capacity of a single node.

High‑availability (HA) options include Host Auto‑Failover (cluster) and System Replication, with System Replication being the recommended native HA method. SAP HANA supports only active‑passive HA, not active‑active.

HANA cluster nodes are classified as Master (primary coordinator), Slave (worker/standby), and Standby (failover node without data).