• SAP HANA

saphana
  1. Help Center
  2. SAP HANA
  3. Product Overview
  4. Application Scenarios
  5. Single-Node Deployment Where HA Is Not Required

Single-Node Deployment Where HA Is Not Required

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

System Architecture

Figure 1 shows the system architecture in single-node scenario where HA is not required.

Figure 1 Single-node scenario where HA is not required

The concepts involved in the preceding figure are as follows:

  • VPC network: All SAP HANA nodes are deployed within a VPC network, and all nodes in the HANA system belong to the same AZ to ensure network security.
  • Public subnet:
    • Network Address Translation (NAT) instance ECS: allows you to access SAP HANA nodes using SSH.
    • SAP HANA Studio ECS: runs the SAP HANA Studio software. You can use RDP or SSH to access the SAP HANA Studio ECS and manage the SAP HANA system.
  • Private subnet:
    SAP HANA node: used for deploying the SAP HANA software. An SAP HANA server has the following disks attached:
    • OS disk: provides the directory for installing the OS.
    • Data volume: periodically stores the data transmitted from the SAP HANA IMDB (a database running in high-performance memory). The period is 5 minutes by default.
    • Log volume: stores the data triggered by an event. When an event, for example, a record or a batch of records are updated, is triggered for the server IMDB, the system will write the latest IMDB data into the log volume.
    • Shared volume: stores the SAP HANA installation software and SAP HANA database log files.
    • Backup volume: stores SAP HANA database backup files.
    • Usr/sap: used to mount to the /usr/sap directory.
    • Swap volume: Linux swap space.

Requirements on SAP HANA Nodes

SAP HANA node specifications used in SoH scenario must meet the following requirements:

Table 1 E1 ECS specifications

Flavor

vCPUs

Memory (GB)

Virtualization Type

Hardware

e1.xlarge

4

128

XEN

  • CPU: Intel® Xeon® Processor Haswell E7-8880
  • Business network: 10GE SR-IOV passthrough IP network
  • Storage network: 56 Gbit/s InfiniBand network
  • Disk type: high I/O (performance-optimized I) and ultra-high I/O (latency-optimized)

e1.2xlarge

8

256

XEN

e1.4xlarge

16

470

XEN

e1.8xlarge

32

940

XEN

SAP HANA node specifications used in the BWoH scenario must meet the following requirements:

Table 2 E2 ECS specifications

Flavor

vCPUs

Memory (GB)

Virtualization Type

Hardware

e2.2xlarge

8

128

XEN

  • CPU: Intel® Xeon® Processor Haswell E7-8880
  • Business network: 10GE SR-IOV passthrough IP network
  • Storage network: 56 Gbit/s InfiniBand network
  • Disk type: high I/O (performance-optimized I) and ultra-high I/O (latency-optimized)

e2.3xlarge

12

256

XEN

e2.4xlarge

18

445

XEN

e2.9xlarge

36

890

XEN

SAP HANA OSs and disks must meet the following requirements:

NOTE:
  • SAP HANA ECS volumes include log volumes, data volumes, shared volumes, backup volumes, and /usr/sap volumes.
  • A shared disk can be attached to multiple ECSs, while a non-shared disk can only be attached to one ECS.
Table 3 Requirements on HANA ECS OS in single-node deployment mode

Item

Specifications

OS

SUSE Linux Enterprise Server 12 SP1 for SAP or later

Table 4 Requirements on E1 and E2 HANA ECS disks in single-node deployment scenarios

Disk

Type

Sharing Mode

Size

OS volume

High I/O (Performance optimized I)

Non-shared disk

N/A

Log volume

Ultra-high I/O (Latency optimized) (production system) or High I/O (Performance optimized I) (non-production system)

Non-shared disk

  • When the memory size is less than or equal to 512 GB, the log volume capacity is half of the memory size and rounded up for decimal places.
  • When the memory size is greater than 512 GB, the log volume capacity is 512 GB.

Data volume

Ultra-high I/O (Latency optimized) (production system) or High I/O (Performance optimized I) (non-production system)

Non-shared disk

The recommended size is at least 1.2 times that of the memory size.

Shared volume

High I/O (Performance optimized I)

Non-shared disk

The recommended size is at least 1.2 times that of the memory size.

Backup volume

SFS

N/A

The recommended capacity is three times or more of the memory size.

SBD volume

High I/O (Performance optimized I)

Shared disk (SCSI)

10 GB

/usr/sap volume

High I/O (Performance optimized I)

Non-shared disk

50 GB

Swap volume

High I/O (Performance optimized I)

Non-shared disk

10 GB

Requirements on Other Nodes

Other nodes include the NAT server and SAP HANA Studio nodes. Table 5 lists the requirements on these nodes.

Table 5 Data planning for other nodes

Node

Specifications

SAP HANA Studio

  • OS:
    NOTE:

    Based on service requirements, use a Windows or Linux ECS to deploy SAP HANA Studio.

    • Windows: Windows Server 2012 R2 or Windows Server 2008 R2
    • Linux: SUSE Linux Enterprise Server 12 SP1 or later
  • Flavor: s1.xlarge (4 vCPUs and 16 GB memory capacity)
  • Disk: 80 GB system disk

NAT server

  • OS:

    SUSE Linux Enterprise Server 12 SP1 or later

  • Flavor: s1.medium (1 vCPU and 4 GB memory capacity) or higher
  • Disk: 40 GB system disk

Deployment

For instructions about how to create ECSs or HANA ECSs on the management console and install the SAP HANA software on the ECS or HANA ECS, see the SAP HANA User Guide (Single-Node Deployment).For instructions about how to create ECSs or HANA ECSs using an API and manually install the SAP HANA software on the ECS or HANA ECS, see the SAP HANA User Guide (API).