• SAP HANA

saphana
  1. Help Center
  2. SAP HANA
  3. Automatic Deployment User Guide
  4. Single-Node Deployment Without HA Required
  5. Data Planning

Data Planning

Scenarios

Figure 1 shows the single-node scenario where HA (High Availability) is not required.

Figure 1 Single-node scenario where HA is not required

The description is as follows:

  • VPC network: All SAP HANA nodes are deployed within a VPC, and all ECSs in the HANA system belong to the same AZ to ensure network security.
  • Public subnet:
    • Network Address Translation (NAT) server ECS: allows you to access HANA ECSs using Secure Shell (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:
    HANA ECS: used for deploying the SAP HANA software. A HANA ECS has the following disks attached:
    • OS disk: provides the directory for installing the OS.
    • Data disk: 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 disk: 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 disk.
    • Shared disk: stores the SAP HANA installation software and SAP HANA database log files.
    • Backup disk: stores backup files of the data and log disks.

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 SAP HANA OSs and Disks

Table 3 lists the requirements on HANA ECS disks.

NOTE:
  • HANA ECS disks include log disks, data disks, shared disks, and backup disks.
  • A shared disk can be attached to multiple ECSs at the same time, while a non-shared disk can only be attached to one ECS.
Table 3 Requirements on HANA ECS disks

Scenario

Specifications

OS

SUSE Linux Enterprise Server (SLES) 11 SP4 for SAP

SUSE Linux Enterprise Server (SLES) 12 SP1 for SAP

NOTE:

On the Heat client, run the nova --insecure image-list command to query the image list. To obtain an image name, contact technical support engineers of the public cloud website.

Disk capacity

Complies with the specifications specified in Table 3.

Single-node scenario where HA is not required

One HANA ECS with the following five disks attached is required:

NOTE:

In SAP HANA scenarios, the SSD disk type is uh-l1) and the SATA disk type is co-p1).

  • OS disk:
    • SSD (production or DR scenario) or SATA disk (other scenarios)
    • Non-shared disk
    • ext3 format
  • Log disk:
    • SSD (production or DR scenario) or SATA disk (other scenarios)
    • Shared disk, which does not support online expansion.
    • XFS format
  • Data disk:
    • SSD (production or DR scenario) or SATA disk (other scenarios)
    • Shared disk, which does not support online expansion.
    • XFS format
  • Shared disk:
    • SATA disk
    • Non-shared disk
    • XFS format
  • Backup disk:
    • SATA disk
    • Non-shared disk
    • ext3 format

SAP HANA Studio and NAT Server

Table 4 lists the requirements on an SAP HANA Studio node and an NAT server node.

NOTE:

On the Heat client, run the nova --insecure image-list command to query the image list. To obtain an image name, contact technical support engineers of the public cloud website.

Table 4 SAP HANA Studio node and NAT server node

Node

Specifications

SAP HANA Studio

  • OS:
    NOTE:

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

    • Windows: Windows Server 2008
    • Linux: SUSE Linux Enterprise Server 11 SP4
  • Flavor: s1.xlarge (4 vCPUs and 16 GB memory capacity)
  • Disk: 80 GB SATA system disk

NAT server

  • OS:

    SUSE Linux Enterprise Server 11 SP4

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

Network Plane

Figure 2 shows the network plane planning in the single-node scenario where HA is not required.

NOTE:

The network segments and IP addresses are for reference only.

Figure 2 Network planning in the single-node scenario where HA is not required

In this scenario, only one NIC is used for network communication.

Table 5 shows the planned network information.

Table 5 Network planning in the single-node scenario where HA is not required

Parameter

Description

Example Value

IP address of the service or client plane

Allows an SAP HANA node to communicate with service software (such as ERP) or SAP HANA Studio client software.

SAP HANA node: 10.0.3.2

SAP HANA Studio: 10.0.3.102

NAT server: 10.0.3.202

Elastic IP address (EIP)

Allows you to access the SAP HANA Studio and NAT server.

Automatically allocated by Open Telekom Cloud.

Security Group Rules

NOTE:

The network segments and IP addresses are for reference only. The following security group rules are recommended practices. You can configure your own security group rule as you need.

Table 6 and Table 7 list security group rules.

NOTE:

In the following table, ## stands for the SAP HANA instance ID, such as 00. Ensure that this ID is the same as that specified when you installed the SAP HANA software.

Table 6 Security group rules (SAP HANA)

Source

Protocol

Port Range

Description

Inbound

10.0.3.0/24

TCP

5##13 to 5##14

Allows the SAP HANA Studio to access SAP HANA.

10.0.3.0/24

TCP

3##15 to 3##17

Provides ports for the service plane.

10.0.3.0/24

TCP

22

Allows SAP HANA to be accessed using SSH.

10.0.3.0/24

UDP

123

Allows other servers to synchronize time with SAP HANA.

Determined by Open Telekom Cloud

ANY

ANY

Security group rule created by the system by default

Allows ECSs in the same security group to communicate with each other.

Outbound

ANY

ANY

ANY

Security group rule created by the system by default

Allows all peers to access SAP HANA.

Table 7 Security group rules (SAP HANA Studio)

Source

Protocol

Port Range

Description

Inbound

0.0.0.0/0

TCP

3389

Allows users to access the SAP HANA Studio using RDP.

This rule is required only when the SAP HANA Studio is deployed on a Windows ECS.

0.0.0.0/0

TCP

22

Allows users to access the SAP HANA Studio using RDP.

This rule is required only when the SAP HANA Studio is deployed on a Linux ECS.

Determined by Open Telekom Cloud

ANY

ANY

Security group rule created by the system by default

Allows ECSs in the same security group to communicate with each other.

Outbound

ANY

ANY

ANY

Security group rule created by the system by default

Allows all peers to access the SAP HANA Studio.

Table 8 Security group rules (NAT server)

Source

Protocol

Port Range

Description

Inbound

0.0.0.0/0

TCP

22

Allows users to access the NAT server using SSH.

Determined by Open Telekom Cloud

ANY

ANY

Security group rule created by the system by default

Allows ECSs in the same security group to communicate with each other.

Outbound

ANY

ANY

ANY

Security group rule created by the system by default

Allows all peers to access the NAT server.