Storage Configuration for SAP HANA
SAP HANA stores and processes all or most of its data in memory, and provides protection
against data loss by saving the data in persistent storage locations. To achieve optimal
performance, the storage solution used for SAP HANA data and log volumes should meet
SAP's
storage KPI. AWS has worked with SAP to certify both Amazon EBS General Purpose SSD
(gp2) and Provisioned IOPS SSD (io1 and io2) storage
solutions for SAP HANA workloads.
gp2 volumes balance price and performance for a wide variety of workloads,
while io1 and io2 volumes provide the highest performance
consistently for mission-critical applications. With these two options, you can choose
the
right storage solution that meets your performance and cost requirements. We highly
recommend
using the io2 configuration for your mission-critical SAP HANA workloads for
production use.
Note that only u-6tb1.metal, u-9tb1.metal, u-12tb1.metal, u-18tb1.metal, u-24tb1.metal, x1e.32xlarge, x1.32xlarge, x1.16xlarge,
r5.24xlarge, r5.12xlarge, r5.metal, r4.16xlarge, r4.8xlarge, and r3.8xlarge instances are
certified for production use. You can use
all the instance types supported by this Quick Start for non-production use.
For multi-node deployments, storage volumes for SAP HANA data and logs are provisioned in the master node and every worker node.
In the following configurations, we intentionally kept the same storage configuration for SAP HANA data and log volumes for all R3, certain R4 and R5, and smaller X1e instance types so you can scale up from smaller instances to larger instances without having to reconfigure your storage.
In addition to the SAP HANA data and log volumes, all instances deployed by this Quick Start will have the following storage configuration for root, SAP binaries, and SAP HANA shared and backup volumes:
| Instance type | Memory (GiB) | vCPUs / logical processors* | Root volume (gp2)
|
SAP binaries (gp2)
|
SAP HANA shared** (gp2)
|
SAP HANA backup*** (st1)
|
|---|---|---|---|---|---|---|
| Certified for production use | ||||||
| u-24tb1.metal | 24,576 | 448 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 2 x 16,384 GiB |
| u-18tb1.metal | 18,432 | 448 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 2 x 16,384 GiB |
| u-12tb1.metal | 12,288 | 448 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 16,384 GiB |
| u-9tb1.metal | 9,216 | 448 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 16,384 GiB |
| u-6tb1.metal | 6,144 | 448 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 12,288 GiB |
| x1e.32xlarge | 3,904 | 128 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 8,192 GiB |
| x1.32xlarge | 1,952 | 128 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 4,096 GiB |
| x1.16xlarge | 976 | 64 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 2,048 GiB |
| r5.metal | 768 | 96 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 2,048 GiB |
| r5.24xlarge | 768 | 96 | 1 x 50 GiB | 1 x 50 GiB | 1 x 1,024 GiB | 1 x 2,048 GiB |
| r5.16xlarge | 512 | 64 | 1 x 50 GiB | 1 x 50 GiB | 1 x 512 GiB | 1 x 1,024 GiB |
| r4.16xlarge | 488 | 64 | 1 x 50 GiB | 1 x 50 GiB | 1 x 512 GiB | 1 x 1,024 GiB |
| r5.12xlarge | 384 | 48 | 1 x 50 GiB | 1 x 50 GiB | 1 x 512 GiB | 1 x 1,024 GiB |
| r5.8xlarge | 256 | 32 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 1,024 GiB |
| r4.8xlarge | 244 | 32 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 1,024 GiB |
| r3.8xlarge | ||||||
| Supported for non-production use only | ||||||
| x1e.4xlarge | 488 | 16 | 1 x 50 GiB | 1 x 50 GiB | 1 x 512 GiB | 1 x 1,024 GiB |
| x1e.2xlarge | 244 | 8 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| x1e.xlarge | 122 | 4 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| r5.4xlarge | 128 | 16 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| r5.2xlarge | 64 | 8 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| r4.4xlarge | 122 | 16 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| r3.4xlarge | ||||||
| r4.2xlarge | 61 | 8 | 1 x 50 GiB | 1 x 50 GiB | 1 x 300 GiB | 1 x 512 GiB |
| r3.2xlarge | ||||||
* Each logical processor offered by Amazon EC2 High Memory Instances is a hyperthread on a physical CPU core.
** In a multi-node architecture, the SAP HANA NFS shared volume is provisioned only once on the master node.
*** In a multi-node architecture, the SAP HANA backup volume can be deployed as NFS
or Amazon EFS. The size of the SAP HANA NFS backup volume is multiplied by the number
of nodes. The SAP HANA backup volume is provisioned only once on the master node,
and NFS is mounted on the worker nodes. There is no provision needed for Amazon EFS
General Purpose SSD (gp2) volumes created or modified after 12/03/2018 have a throughput maximum between 128
MiB/s and 250 MiB/s depending on volume size.
Volumes greater than 170 GiB and below 334 GiB deliver a maximum throughput of 250
MiB/s if burst credits are available.
Volumes with 334 GiB and above deliver 250 MiB/s, irrespective of burst credits.
For details, see Amazon EBS Volume Types in the AWS documentation.
For single-node deployment, storage for SAP HANA backup is configured with Amazon
EBS Throughput Optimized HDD (st1) volumes.
This volume type provides low-cost magnetic storage designed for large sequential
workloads.
SAP HANA uses sequential I/O with large blocks to back up the database, so st1 volumes provide a low-cost, high-performance option for this scenario.
To learn more about st1 volumes, see Amazon EBS Volume Types in the AWS documentation.
The SAP HANA backup volume size is designed to provide optimal baseline and burst throughput as well as the ability to hold several backup sets. Holding multiple backup sets in the backup volume makes it easier to recover your database if necessary. You may resize your SAP HANA backup volume after initial setup if needed. To learn more about resizing your Amazon EBS volumes, see Expanding the Storage Size of an EBS Volume on Linux in the AWS documentation.
For multi-node deployment, SAP HANA backup deployed with Amazon EFS
