Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Validation Guide—PowerStore Configuration and Deployment Best Practices for SAP HANA TDI
PowerStore storage configuration
Overview Front-end I/O modules PowerStore disk storage Data reduction Volumes SAP HANA capacity requirements

SAP HANA capacity requirements

  • Every SAP HANA node requires storage devices and capacity for:

    • Operating system boot image
    • SAP HANA installation (/hana/shared)
    • SAP HANA persistence (data and log)
    • Backup

    For more information, see SAP HANA Storage Requirements.

    Note: The formulas for capacity sizing in SAP HANA Storage Requirements are subject to change by SAP. Ensure that you check the latest version of that document before you determine your capacity requirements.

    Operating system boot image

    When the SAP HANA nodes boot from a volume on PowerStore (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, including 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.

    SAP HANA persistence (data and log)

    The SAP HANA in-memory database requires disk storage to:

    • Maintain the persistence of the in-memory data on disk to prevent a data loss that is caused by a power outage. Disk storage must allow a host auto-failover, where a standby SAP HANA host takes over the in-memory data of a failed worker host in scale-out installations.
    • Log information about data changes (redo log).

    Every SAP HANA scale-up or scale-out (worker) node requires two disk volumes or file systems to save the in-memory database on disk (data) and to keep a redo log (log). The size of these volumes or file systems depends on the anticipated total memory requirement of the database and the RAM size of the node. To assist with disk sizing preparation, SAP provides several tools and documents, as described in SAP HANA Storage Requirements. Version 2.10 (February 2017) of the document provides the following formulas to calculate the size of the data volume:

    • Option 1: If an application-specific sizing program can be used:

    Sizedata = 1.2 x anticipated net disk space for data

    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, divide the anticipated net disk space 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, it is recommended to use the RAM size of the node plus 20 percent free space for a capacity calculation of the datafile system.

    • Option 2: If no application-specific sizing program is available, the recommended size of the data volume of an SAP HANA system is equal to the total memory required for the 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:

    [systems ≤ 512 GB] Sizeredolog = 1/2 x RAM
    [systems > 512 GB] Sizeredolog = (min) 512 GB

    SAP HANA installation (/hana/shared/)

    Before you install the SAP HANA binary, configuration, and trace files 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 a Network File System (NFS) for this purpose. PowerStore unified arrays can provide this file system with the NAS option.

    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:

    • Single node (scale-up):

    Sizeinstallation(single-node) = 1 x RAM but max 1 TB

    • Multinode (scale-out):

    Sizeinstallation(scale-out) = 1 x RAM_of_worker per four worker nodes

    Backup

    SAP HANA supports backup to a file system or the use of third-party tools that SAP has certified. Dell EMC supports data protection strategies for SAP HANA backup using Dell EMC Data Domain systems and Dell EMC NetWorker software. While an SAP HANA backup to an NFS file system on a PowerStore all-flash or hybrid array is possible, we do 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 PowerStore array, see SAP HANA Storage Requirements for information about sizing the backup file system. The capacity requirement 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.