Every SAP HANA node requires storage devices and capacity for:
For more information, see SAP HANA Storage Requirements.
When the SAP HANA nodes boot from a volume on Unity XT (boot from SAN), the required capacity for the operating system must be included in the overall capacity calculation for the SAP HANA installation. Every SAP HANA node requires approximately 100 GB capacity for the operating system. This capacity includes space for the /usr/sap/ directory.
When booting from a SAN, follow the best practices that are described in the Dell EMC Host Connectivity Guide for Linux.
Before you can install the SAP HANA binaries and the configuration files, traces, and logs, every SAP HANA node must have access to a file system that is mounted under the local /hana/shared/ mount point. In an SAP HANA scale-out cluster, a single shared file system is required and must be mounted on every node. Most SAP HANA installations use an NFS file system for this purpose. Unity XT all-flash and hybrid arrays can provide this file system with the NAS option.
You can calculate the size of the /hana/shared/ file system by using the latest formula in SAP HANA Storage Requirements. Version 2.10 (February 2017) of the requirements document uses the following formulas for calculation:
Sizeinstallation(scale-out) = 1 x RAM_of_worker per 4 worker nodes
The SAP HANA in-memory database requires disk storage to:
Every SAP HANA node (scale-up) or worker node (scale-out) requires two disk volumes/file systems to save the in-memory database on disk (data) and to keep a redo log (log). The size of these volumes/file systems depends on the anticipated total memory requirement of the database and the RAM size of the node. To assist with preparing the disk sizing, SAP provides several tools and documents, as described in SAP HANA Storage Requirements. Version 2.10 (February 2017) of the requirements document provides the following formulas to calculate the size of the data volume:
where “anticipated net disk space” is the anticipated total memory requirement of the database plus an additional 20 percent free space. If the database is distributed across multiple nodes in a scale-out cluster, the “anticipated net disk space” must be divided by the number of SAP HANA worker nodes in the cluster. For example, if the anticipated net disk space is 2 TB and the scale-out cluster consists of four worker nodes, then every node must be assigned a 616 GB data volume (2 TB / 4 = 512 GB x 1.2 = 616 GB).
If the anticipated net disk space is unknown at the time of the storage sizing, Dell EMC recommends using the RAM size of the node plus 20 percent free space for a capacity calculation of the data file system.
Sizedata = 1 x RAM
The size of the log volume depends on the RAM size of the node. SAP HANA Storage Requirements provides the following formulas to calculate the minimum size of the log volume:
Figure 9. Calculating the log volume
SAP HANA supports backup to a file system or the use of SAP-certified third-party tools. Dell EMC supports data protection strategies for SAP HANA backup using Dell EMC Data Domain systems and Dell EMC NetWorker software. An SAP HANA backup to an NFS file system on a Unity XT all-flash or hybrid array is possible. However, Dell EMC does not recommend backing up the SAP HANA database to the storage array where the primary persistence resides. If you plan to back up SAP HANA to an NFS file system on a different Unity XT array, see SAP HANA Storage Requirements for information about sizing the backup file system. The capacity depends not only on the data size and the frequency of change operations in the database but also on the backup generations that are kept on disk.