• SAP HANA

saphana
  1. Help Center
  2. SAP HANA
  3. User Guide (Single Node)
  4. Deployment
  5. Data Planning
  6. SAP HANA Nodes

SAP HANA Nodes

SAP poses specific requirements on HANA ECSs depending on application scenarios.

NOTE:

The time zone of the server on which SAP NetWeaver is deployed must be the same as that of SAP HANA nodes, excepting the specifications described in this section.

Specifications in SoH Scenario

In SoH scenario, SAP HANA works with SAP business suites, such as ERP or CRM. In this scenario, SAP HANA provides OLTP functions. The SAP HANA process latency is the key concern.

Table 1 lists the requirements on HANA ECSs in SoH scenario.

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

Specifications in BWoH Scenario

In 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 2 lists the requirements on HANA ECSs in BWoH scenario.

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

Requirements on OSs and Disks

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 scenarios

Scenario

Specifications

OS

SUSE Linux Enterprise Server 12 SP1 for SAP or later

NOTE:

In the scenario where HA is achieved within an AZ, you need to create an EVS disk for an SAP HANA node and use it as the SBD volume. After the EVS disk is created, bind it to another SAP HANA node.

In the cross-AZ HA scenario, you do not need to create SBD volumes for SAP HANA nodes. For details, see Configuring iSCSI (Cross-AZ HA Deployment).

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