Home > Workload Solutions > SAP > Guides > SAP HANA TDI Guides > Dell Validated Design for SAP HANA TDI with Dell PowerMax 2500 and 8500 Storage Arrays > SAP HANA capacity requirements
Every SAP HANA node requires storage devices and capacity for the following purposes:
For the SAP HANA nodes to be able to start up from a volume on a PowerMax array (boot from the SAN), the overall capacity calculation for the SAP HANA installation must include the required operating system capacity. Every SAP HANA node requires approximately 100 GB capacity for the operating system, including the /usr/sap/ directory. For information about best practices when booting from a SAN, see the Dell EMC Host Connectivity Guide for Linux.
To install the SAP HANA binary files, configuration files, traces, and logs, every SAP HANA node requires access to a file system that is mounted under the local /hana/shared/ mount point. An SAP HANA scale-out cluster requires a single shared file system, which must be mounted on every node. Most SAP HANA installations use an NFS for this purpose. PowerMax 2500 and 8500 arrays can provide this file system with the new PowerMax File. Use the formula provided in the SAP HANA Storage Requirements white paper to calculate the size of the /hana/shared/ file system. The white paper is included as an attachment in SAP Note 1900823: SAP HANA Storage Connector API. Version 2.10 of the white paper provides the following formulas:
Single node (scale-up):
Sizeinstallation(single-node) = MIN(1 x RAM; 1 TB)
Multinode (scale-out):
Sizeinstallation(scale-out) = 1 x RAM_of_worker per 4 worker nodes
The SAP HANA in-memory database requires disk storage for the following purposes:
Every SAP HANA scale-up node and scale-out (worker) node requires two disk volumes to save the in-memory database on disk (data) and keep a redo log (log). The size of the data and log devices depends on the database size. Use the formula provided in the SAP HANA Storage Requirements white paper to calculate the size of the data volume. The white paper is included as an attachment in SAP Note 1900823: SAP HANA Storage Connector API. Version 2.10 of the white paper provides the following formulas:
Sizedata = 1.2 x net disk space for data
where “Net disk space” is the anticipated total memory requirement of the database plus 20 percent free space.
If the database is distributed across multiple nodes in a scale-out cluster, divide the net disk space by the number of SAP HANA worker nodes in the cluster. For example, if the net disk space is 2 TB and the scale-out cluster consists of 4 worker nodes, every node must have a 616 GB data volume assigned to it (2 TB / 4 = 512 GB x 1.2 = 616 GB).
If the net disk space is unknown at the time of storage sizing, we recommend using the RAM size of the node plus 20 percent free space to calculate the capacity of the datafile system.
The size of the log volume depends on the RAM size of the node. Use the formula provided in the SAP HANA Storage Requirements white paper to calculate the minimum size of the log volume. The white paper is included as an attachment in SAP Note 1900823: SAP HANA Storage Connector API. Version 2.10 of the white paper provides the following formulas:
[systems ≤ 512 GB] Sizeredolog = 1/2 x RAM
[systems > 512 GB] Sizeredolog(min) = 512 GB
SAP HANA supports backup to a file system or the use of SAP-certified third-party tools. Dell Technologies supports data-protection strategies for SAP HANA backup using Dell Data Domain and Dell NetWorker. Although you can back up an SAP HANA database to an NFS on a PowerMax array, we do not recommend backing up the database to the storage array on which the primary persistence resides. If you plan to back up SAP HANA to an NFS file system on a different Dell storage array, see the SAP HANA Storage Requirements white paper for information about sizing. The white paper is included as an attachment in SAP Note 1900823: SAP HANA Storage Connector API. The capacity depends on not only the data size and the frequency of change operations in the database, but also on the number of backup generations that are kept on disk.
For information about using Data Domain data protection for SAP HANA, see Data Domain Backup and Recovery for SAP HANA.