Description

This document describes how to deploy SAP HANA systems within an AZ.

Scale-up and Scale-out

SAP HANA nodes can be expanded in the scale-up or scale-out mode.

Scale-up mode
Also called single-node system mode, in which an SAP HANA system contains only one valid node. If high availability (HA) is required, build such an architecture using two single nodes through system replication. In scale-up mode, when the system requires expansion, add CPUs, memory capacity, and hard disks to the node.

The public cloud does not support scale-up expansion for a node on which SAP HANA is running.
Scale-out mode
Also called cluster system mode, in which an SAP HANA system contains multiple nodes. In scale-out mode, when the system requires expansion, add more nodes to the system.

In accordance with the node expansion modes, SAP HANA can be deployed in the following scenarios:

Single-node deployment: applies in OLTP scenarios. You can choose HA configuration as required. SAP HANA receives and processes data quickly, provides processing results in a short period of time, and rapidly responds to user operations.
Cluster deployment: applies in OLAP scenarios. As a data warehouse, SAP HANA offers support for decision-makers and senior managers. It can quickly and flexibly process complex queries on a large amount of data based on the analysts' requests. It can also provide decision makers with the query results intuitively and clearly. Using SAP HANA, decision makers can obtain accurate information about the enterprise operating status, learn object demands, and make correct decisions.

Application Scenarios and Deployment Modes

Recommended deployment modes vary depending on systems.

Production (PRD): indicates the production system where SAP HANA is formally used.
Quality Assure (QAS): indicates the quality assurance system where SAP HANA functions, performance, and reliability are fully verified.
Development (DEV): indicates the development system where the development engineers configure and verify the compatibility between application software and SAP HANA and continuously optimize the application software.
Training (TRN): indicates the training and demonstration system where you provide a training or demonstration after deploying SAP HANA.
Test (TST): indicates the test scenario where the development engineers test application software and SAP HANA to verify the functions of application software after application software development is complete.

In Suite on HANA (SoH) scenario, SAP HANA works with SAP business suites, such as Enterprise Resource Planning (ERP) or Customer Requirement Management (CRM). In this scenario, SAP HANA provides OLTP functions. The SAP HANA process latency is the key concern.

In Business Warehouse on HANA (BWoH) scenario, SAP HANA works with SAP Business Warehouse. In this scenario, SAP HANA provides OLAP functions and supports rapid computing and analyzing on massive data. The SAP HANA processing performance and the network bandwidths between SAP HANA nodes are the key concern.

**Table 1** Systems and deployment schemes
System	SoH	BWoH (Single-Node)	BWoH (Cluster)
PRD	Single-node scenario where HA is required	Single-node scenario where HA is required	Cluster scenario where two NFS servers are deployed
QAS	Single-node, regardless of whether HA is required or not	Single-node, regardless of whether HA is required or not	Single-node scenario where HA is not required, cluster scenario where two NFS servers are required, or cluster scenario where single NFS server is required
DEV	Single-node scenario where HA is not required	Single-node scenario where HA is not required	Single-node scenario where HA is not required
TRN	Single-node scenario where HA is not required	Single-node scenario where HA is not required	Single-node scenario where HA is not required
TST	Single-node scenario where HA is not required	Single-node scenario where HA is not required	Single-node scenario where HA is not required