SAP HANA Nodes

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 specifications of HANA ECSs certified by SAP on HUAWEI CLOUD.

**Table 1** Large-memory E3 ECS specifications
ECS Type	vCPUs	Memory (GB)	Flavor
Large-memory	28	348	e3.7xlarge.12
Large-memory	56	696	e3.14xlarge.12

**Table 2** Memory-optimized M6 ECS specifications
ECS Type	vCPUs	Memory (GB)	Flavor
Memory-optimized	32	256	m6.8xlarge.8
Memory-optimized	64	512	m6.16xlarge.8

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 3 lists the specifications of HANA ECSs certified by SAP on HUAWEI CLOUD.

**Table 3** Large-memory E3 ECS specifications
ECS Type	vCPUs	Memory (GB)	Flavor
Large-memory	28	348	e3.7xlarge.12
Large-memory	56	696	e3.14xlarge.12

Requirements on OSs and Disks

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 4** Requirements on HANA ECS OS in single-node deployment scenarios
Scenario	Specifications
OS	SUSE Linux Enterprise Server for SAP Applications 12 SP3 SUSE Linux Enterprise Server for SAP Applications 12 SP4 SUSE Linux Enterprise Server for SAP Applications 12 SP5 SUSE Linux Enterprise Server for SAP Applications 15 SUSE Linux Enterprise Server for SAP Applications 15 SP1

In the same AZ HA scenario, to prevent split-brain, 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 5** Requirements on E3 ECS disks in single-node deployment scenarios
Disk	Type	Sharing Mode	Size
OS volume	High I/O	Non-shared disk	N/A
Log volume	Ultra-high I/O	Non-shared disk	For details, see Table 6.
Data volume	Ultra-high I/O	Non-shared disk	Create an EVS disk. Use LVM to create soft partitions and logically divide the disk into data volumes. For details, see Table 6.
Shared volume	High I/O	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	Shared disk (SCSI)	10 GB
/usr/sap volume	High I/O	Non-shared disk	100 GB
Swap volume	High I/O	Non-shared disk	10 GB