Storage Configuration Best Practices for SAP HANA Tailored ... · Unity uses the latest technology...

Solution Guide

STORAGE CONFIGURATION BEST PRACTICES FOR SAP HANA TAILORED DATA CENTER INTEGRATION ON EMC UNITY STORAGE SYSTEMS

Unity All Flash 300F, 400F, 500F, 600F Unity Hybrid 300, 400, 500, 600

EMC Solutions

Abstract

This solution guide describes storage best practices for SAP HANA in Tailored Data Center (TDI) deployments on EMC Unity-certified enterprise storage family systems. The solution enables customers to use EMC Unity™ for SAP HANA TDI deployments in a fully supported environment with their existing data center infrastructures, providing multiple benefits.

July 2016

<Month Year>

Copyright

2 Storage Configuration Best Practices for SAP HANA Tailored Data Center Integration on EMC Unity Storage Systems Solution Guide

Copyright © 2016 EMC Corporation. All rights reserved.

Published July 2016

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, Data Domain, Unity, UltraFlex, Unisphere, Virtual Provisioning and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

Storage Configuration Best Practices for SAP HANA TDI on EMC Unity Storage Systems Solution Guide

Part Number H15220

http://www.emc.com/legal/emc-corporation-trademarks.htm

Contents

3 Storage Configuration Best Practices for SAP HANA Tailored Data Center Integration on EMC Unity Storage Systems

Solution Guide

Contents

Executive summary ............................................................................................................................. 4

Introduction ....................................................................................................................................... 6

Technology overview and considerations ............................................................................................ 7

Storage design recommendations for EMC Unity arrays for SAP HANA ............................................... 15

Configuring Unity storage for HANA using EMC Unisphere for Unity .................................................. 22

Accessing Unity storage from the SAP HANA nodes ........................................................................... 36

Conclusion ....................................................................................................................................... 38

References ....................................................................................................................................... 40

Executive summary


Executive summary

SAP HANA is an in-memory platform that can be deployed locally (on-premises) or in the cloud. It is a revolutionary platform that is best suited for performing realtime analytics and developing and deploying realtime applications. At the core of this realtime data platform is the HANA database.

HANA combines SAP software components that are optimized on proven hardware provided by SAP hardware partners. As shown in Figure 1, HANA can be deployed on-premises in two different models:

Appliance model

Tailored Datacenter Integration (TDI) model

Figure 1. SAP HANA appliance model versus the TDI model (picture © SAP SE)

By default, a HANA appliance includes integrated storage, compute, and network components. The appliance is certified by SAP, built by one of the HANA hardware partners, and shipped to customers with all software components preinstalled, including the operating systems and the HANA software. The TDI approach provides greater flexibility than the appliance deployment model. The HANA servers must still meet the HANA requirements and be certified HANA servers, but the network and storage components can be shared in customer environments. This approach enables customers to use their existing enterprise storage arrays for HANA. They can integrate HANA seamlessly into existing data center operations, such as disaster recovery, data protection, monitoring, and management, reducing the time-to-value, risk, and costs of an overall HANA adoption.

SAP has certified EMC® Unity™ All Flash and Hybrid arrays as enterprise storage arrays for SAP HANA to ensure that they meet the all the SAP performance and functional requirements. This certification enables customers to use EMC Unity for SAP HANA TDI deployments in a fully supported environment using their existing data center infrastructures.

Using the HANA hardware configuration check tool (hwcct), EMC performed extensive testing on the Unity storage family systems in accordance with the SAP HANA-HWC-

Business case

Solution overview

Executive summary


Solution Guide

ES-1.1 certification scenario. Based on the test results, this solution guide describes storage configuration recommendations for the Unity All Flash and Hybrid arrays that meet SAP performance requirements (the SAP HANA TDI key performance indicators for data throughput and latency) and ensure the highest availability for database persistence on disk.

Note: SAP recommends that TDI customers run the hwcct tool in their environment to ensure that their specific HANA TDI implementation meets the SAP performance criteria.

This solution guide describes HANA TDI deployments in physical environments. If you plan to use HANA in VMware virtualized environments on vSphere, refer to the EMC document VMware Virtualized SAP HANA with EMC Storage Solution Guide.

Customers using HANA TDI on Unity arrays can:

Integrate HANA into an existing data center

Use Unity shared enterprise storage to rely on already available, multisite concepts to benefit from established automation and operations processes

Transition easily from an appliance-based model to the Unity-based TDI architecture, while relying on EMC services to minimize risk

Use their existing operational processes, skills, and tools and avoid the significant risks and costs associated with operational change

Use performance and scale benefits of Unity to obtain realtime insights across the business

Expect significant benefits using flash drives for the HANA persistence by reducing HANA startup, host auto-failover, and backup times

EMC and the authors of this document welcome your feedback on the solution and the solution documentation. Contact [email protected] with your comments.

Authors: Donagh Keeshan, Fergal Murphy, Aighne Kearney

Key benefits

We value your feedback!

mailto:[email protected]?subject=Feedback:%20Storage%20Configuration%20Best%20Practices%20for%20SAP%20HANA%20Tailored%20Data%20Center%20Integration%20on%20EMC%20UNITY%20Storage%20Systems,%20Part%20Number%20H15220

Introduction


Introduction

Before the HANA TDI deployment model was available, customers who used the appliance model experienced the following limitations:

Limited choice of servers, networks, and storage

Little knowledge and control of the critical components in the HANA appliance

Inability to use existing data center infrastructure and operational procedures, resulting in higher infrastructure startup costs

Fixed sizes for HANA server and storage capacities, leading to higher costs due to lack of capacity and inability to respond rapidly to unexpected growth demands

This guide describes a solution that uses HANA in a TDI deployment scenario on EMC Unity enterprise storage. This solution reduces hardware and operational costs, lowers risks, and increases server and network vendor flexibility.

The guide provides configuration recommendations that are based on SAP requirements for high availability and on the performance tests and results that are required to meet the SAP key performance indicators (KPIs) for HANA TDI.

This document provides the following information:

Best practices and tips for deploying the HANA database on EMC Unity All Flash and Hybrid storage systems

Descriptions of the configuration requirements and storage design recommendations for Unity with HANA

Steps for configuring EMC Unity storage for HANA using EMC Unisphere® for Unity

Detailed instructions for accessing Unity storage from the SAP HANA nodes

This guide is intended for system integrators, systems or storage administrators, customers, partners, and members of EMC professional services who must configure a Unity All Flash or Hybrid storage array to be used in a TDI environment for HANA.

Purpose

Scope

Audience

Technology overview and considerations


Solution Guide


EMC Unity provides customers with affordable all-flash performance solutions or cost-effective hybrid solutions by using a midrange system that is simple to deploy, manage, and service. The Unity storage system is perfect for midsized deployments, Remote Office/Branch Office (ROBO) locations, and cost-sensitive, mixed-workload environments. It is designed for all-flash systems and is available as a hybrid system, for converged deployment, and as a software-defined virtual edition.

Figure 2 shows the Unity product family.

Figure 2. EMC Unity product family The Unity system is offered in four different models, with two different configurations. The platform includes the Unity 300 and scales up to the Unity 600. It can be configured as an all-flash or a hybrid system. The Unity models are similar in form factor and connectivity, but scale in processing and memory capabilities. Additionally, the system limits change depending on the Unity model. Table 1 provides more details.

Table 1. Comparison of Unity models

Model Unity 300 Unity 400 Unity 500 Unity 600

Processor Intel E5-2603 6c/1.6Ghz

Intel E5-2630 8c/2.4GHz

Intel E5-2660 10c/2.6GHz

Intel E5-2680 12c/2.5Ghz Memory 24 GB/SP 48 GB/SP 64 GB/SP 128 GB/SP

Max. drives 150 250 350 500

Max. capacity (RAW)

1.5 PB 2.5 PB 3.5 PB 5.0 PB

Unity uses the latest technology in multicore processors, providing greater performance capabilities. EMC recommends maximizing the use of flash drives in all Unity systems to realize the performance potential.

Note: Unity Hybrid configurations support a maximum of 50 percent total flash capacity. If you require more than 50 percent flash capacity, consider a Unity All Flash configuration.

EMC Unity system overview



EMC Unity offers both block and file provisioning in the same enclosure. Disks are provisioned into storage pools that can host both block and file data. Connectivity is offered for both block and file protocols. For block connectivity, you can use iSCSI or Fibre Channel to access LUNs, consistency groups, VMware datastores, and VMware virtual volumes. For file connectivity, network attached storage (NAS) Servers can host file systems that are accessed using server message block (SMB) shares or network file system (NFS) shares. NAS Servers also can host VMware NFS datastores.

Storage pools

All storage resources are provisioned from storage pools. A storage pool is a collection of physical disks that are arranged into an aggregate group, with some form of RAID applied to the disks to provide redundancy. On a hybrid system, storage pools can consist of disks of varying types. These disks are sorted into one of three tiers: extreme performance (flash), performance (SAS), and capacity (NL-SAS). For hybrid systems with a Fully Automated Storage Tiering for Virtual Pools (FAST VP) license, a storage pool can be configured to contain multiple tiers of disks. This is known as a heterogeneous storage pool. When combined with FAST VP, heterogeneous storage pools can provide efficient balancing of data between tiers without requiring user intervention. Storage pools can also contain a single tier of disk. This is known as a homogeneous storage pool.

Figure 3 shows the different storage pool configurations.

Figure 3. Storage pool layouts

Each tier in a storage pool can have a different RAID configuration set. Another consideration for storage pools is the “hot spare policy.” The Unity system reserves one spare drive per 30 drives to serve as a spare for the system. A spare drive can replace a faulted drive in a storage pool if it matches the drive type of the faulted disk. Any unbound drive can serve as a spare, but Unity enforces the “1 per 30” rule.

Note: EMC recommends that a storage pool always has at least 10 percent free capacity to maintain proper functioning.

Storage provisioning



Solution Guide

EMC recommends using fewer storage pools within Unity to reduce complexity and increase flexibility. However, it might be appropriate to configure multiple storage pools to:

Separate workloads with different I/O profiles

Separate pools where FAST® cache is and is not active

Dedicate resources to meet specific performance goals

Separate resources for multitenancy

All-flash pools

All-flash pools provide the highest level of performance in Unity. Use an all-flash pool when the application requires the highest storage performance at the lowest response time. SAS Flash 3 drives are preferred for all-flash pools, as they provide higher capacities and lower cost per GB.

Note: Only SAS Flash 2-based all-flash pools can be converted to hybrid pools.

EMC recommends using only a single drive size and a single RAID width within an all-flash pool. For example, you can use only 1.6 TB SAS Flash 3 drives and configure them all with RAID-5 8+1. Hybrid pools

Hybrid pools contain more than one type of drive technology. In addition to flash drives, they can also contain SAS or near-line SAS (NL-SAS) drives. Hybrid pools typically provide greater capacity at a lower cost than all-flash pools, but also typically have lower overall performance and higher response times. Use hybrid pools for applications that do not require consistently low response times, or that have large amounts of mostly inactive data.

Note: EMC recommends provisioning a flash tier in hybrid pools. The minimum recommended flash capacity is approximately five percent of the pool capacity. Refer to EMC Unity: BEST PRACTICES GUIDE – Performance and Availability for details.

FAST VP

FAST VP is an automated feature that optimizes disk utilization. It ensures your data is distributed effectively across the various media types in a multi-tier pool. FAST VP defines three tiers of drive types:

Extreme performance tier–Flash disks

Performance tier–Serial attached SCSI (SAS) disks

Capacity tier–NL-SAS disks

When a storage pool with multiple tiers is created on a hybrid Unity system with licensed FAST VP, block and file resources created on that storage pool are subject to FAST VP policies. FAST VP policies can specify where to place the initial data



populated to a storage resource --highest tier or lowest tier. As the data is manipulated, FAST VP relocates data across the tiers based on usage, as shown in Figure 4.

Figure 4. FAST VP relocation

Data that is accessed frequently is placed on the best-performing tier, while less-frequently accessed data is moved to the high-capacity tiers. Data relocation is at a 256 MB granularity and can be a scheduled recurring event. Combined with FAST cache and the other multicore optimizations, FAST VP ensures that your disks are used efficiently.

Table 2 describes the FAST VP tiering policy settings, which are defined at the data-resource level. This policy defines both the initial tier placement and the ongoing automated tiering of data during data relocation operations. When creating a FAST VP-enabled storage pool, use the highest available tier for the data volumes on flash and auto tier for the log volumes on SAS.

Table 2. Tiering policy information

Tiering policy Corresponding initial tier placement Description

Start High then Auto-Tier (default)

Highest available tier Recommended setting. Sets the initial data placement to the highest-performing disks with available space, and then relocates portions of the storage resource's data based on I/O activity.



Solution Guide

Tiering policy Corresponding initial tier placement Description

Auto-Tier Optimize for pool performance Sets the initial data placement to an optimum, system-determined setting, and then relocates portions of the storage resource's data based on the storage resource's performance statistics such that data is relocated among tiers according to I/O activity.

Highest Available Tier

Highest available tier Sets the initial data placement and subsequent data relocation (if applicable) to the highest-performing disks with available space.

Lowest Available Tier

Lowest available tier Sets the initial data placement and subsequent data relocation (if applicable) to the most cost-effective disks with available space.

Unity offers a range of storage efficiency features that can help you maximize the utilization and performance of your system. Unity’s operating environment was built with the capability of multi-core processors and their increasing scale in mind. With the use of flash media in hybrid array configurations, FAST cache and FAST VP can ensure that data is readily accessible and is being stored in the proper location on the array. Lastly, host I/O limits can be implemented to manage host activity and control “noisy neighbors”.

Multicore optimization

A set of multicore optimizations is offered on the Unity system:

Multicore cache –With multicore cache, read and write cache space is shared and dynamically manipulated based on the read/write activity served by the system. This ensures a proper distribution of cache resources to best serve incoming requests. The arrival rates of incoming requests are tracked, and weighed against the ability of the backend disks to write the data out of cache. Based on this information, multicore cache throttles arrival rates to avoid forced flushing. Multicore cache is fully automated. Noo user interaction is required to enable or manipulate the cache.

Multicore RAID – Multicore RAID manages the RAID-based protection on storage pools. With multicore RAID, any unassigned disks are marked as potential spares for use in the event of a drive fault. If a drive becomes faulted, a potential spare is selected and becomes a permanent part of the RAID group. Multicore RAID also has the ability to move a disk within the physical locations of a system. For example, a disk can be moved from one enclosure to another to better balance activity between enclosures and buses. Both assigned and unassigned disks can be relocated within a five-minute window. Note that moving an

Storage efficiency



assigned disk temporarily results in a degraded RAID group. Lastly, RAID6 groups that suffer double drive failures employ a parallel rebuild to restore full redundancy as quickly as possible. Spares are selected and the rebuild process begins immediately following a drive fault.

NAS Servers

NAS Servers host file systems on the Unity storage system. NAS Servers use virtual interfaces to enable host connectivity to SMB, NFS, and multiprotocol file systems, as well as VMware NFS datastores and VMware Virtual Volumes. Depending on what is enabled on the NAS Server, SMB file systems and NFS file systems can be created either separately or in a multiprotocol configuration. File systems and virtual interfaces are isolated to a single NAS Server, allowing for multitenancy over multiple NAS Servers. NAS Servers are hosted on a storage processor, and automatically fail over if the SP becomes faulted. Any associated file systems also fail over.

File systems

File systems are file-based storage resources that are hosted on NAS Servers. They are accessed through shares, which can be provisioned for SMB or NFS access, providing access for Windows or UNIX hosts. Depending on what protocol is selected for your file system, only shares of that type can be provisioned. For example, if an SMB file system is created, SMB (not NFS) shares can be provisioned. To provision both SMB and NFS shares from a file system, use a multiprotocol file system.

File systems can be extended and shrunk in size, and allocated space is automatically taken and reclaimed based on file system usage patterns. Finally, file systems can be configured with quotas to better regulate file system space usage. Tree quotas and user quotas are supported on file systems, and can be used in combination.

Note: For more information about file systems, refer to the EMC Unity: Unity File System – A Detailed Review.

SAP HANA is an in-memory database. The data is kept in the RAM of one or multiple SAP HANA worker hosts. All database operations (reads, inserts, updates, or deletes) are performed in the main memory of the host. This feature differentiates SAP HANA from traditional databases, where only a part of the data is cached in RAM and the remaining data resides on disk.

To ensure that the SAP HANA database can always be restored to its most recent committed state, persistent storage is used to provide a fallback in case of failure. The log captures all changes by database transactions (redo logs), and data and undo log information is automatically saved to disk at regular savepoints.

Scale-up versus scale-out

As an SAP-certified enterprise storage array for SAP HANA, Unity arrays can be used for both single-host (scale-up) systems and multihost (scale-out) systems in TDI deployments.

Unity file systems

SAP HANA



Solution Guide

In single-host environments, the database must fit into the RAM of a single server. Single-host environments are preferred for online transaction processing (OLTP)-type workloads such as SAP Business Suite on SAP HANA. In multihost environments, the database tables are distributed across the RAM of multiple servers. Multihost environments use worker and standby hosts. A worker host is an active component that accepts and processes database requests. A standby host is a passive component. It has all database services running, but no data in RAM. It waits for a failure of a worker host so that it can take over its role, a process known as host auto-failover. Because the in-memory capacity in these deployments can be quite high, scale-out SAP HANA clusters are perfectly suited for online analytical processing (OLAP)-type workloads with very large datasets, such as SAP Business Warehouse (BW) on SAP HANA. HANA I/O patterns

The HANA persistent devices have different I/O patterns. Refer to the SAP HANA Storage Requirements White Paper for details.

Data volume Access to the data volume is primarily random, with various block sizes from small 4 K blocks up to large 64 M blocks. The data is written asynchronously with parallel I/Os to the data file system. During normal operations, most of the I/Os to the data file system are writes, and data is read from the file system only during database restarts, HANA backups, host auto- failovers, or a column store table load/reload.

Log volume Access to the log volume is primarily sequential, with various block sizes from 4K up to 1M blocks. HANA keeps a 1 M buffer for the redo log in memory. When the buffer is full, it is synchronously written to the log volume. When a database transaction is committed before the log buffer is full, a smaller block is written to the file system. Because data to the log volume is written synchronously, a low latency for the I/O to the storage device is important, especially for the smaller 4 K block and 16 K block sizes.

Similar to the data volume, during normal database operations, most of the I/Os to the log volume are writes, and data is read from the log volume only during database restarts, HA failover, and log backups or database recovery.

HANA I/Os can be optimized for specific storage environments. Refer to Optimizing file I/Os after HANA installation for a description of the specific optimization required for the Unity arrays.

Since SAP introduced the TDI deployment model, two certification scenarios have been used to test the performance of the HANA persistence (data and log) and validate that the storage array meets the SAP KPIs for bandwidth (MB/s) and latency (microseconds): HANA-HWC-ES 1.0 and HANA-HWC-ES 1.1.

HANA-HWC-ES 1.1

With SAP HANA 1.0 SPS 10 and higher, SAP introduced a new scenario for enterprise storage certifications. Version 1.1 now uses the underlying file system performance

SAP HANA certification for Unity



tool (fsperf) for file system performance validation. With fsperf, random I/O operations required additional resources and the KPIs could be achieved only with more disks (HDDs) or with flash disks.

The Unity All Flash and Hybrid arrays have been certified using HANA-HWC-ES 1.1. All configuration and scalability recommendations in this document are based on this scenario. Refer to SAP Note 1943937 when re-validating Unity All Flash and Hybrid arrays at a customer site.

Storage design recommendations for EMC Unity arrays for SAP HANA


Solution Guide


The following configuration recommendations apply to production HANA systems deployed on Unity All Flash and Hybrid storage arrays. Production HANA systems in TDI environments must meet the SAP KPIs. The following configuration requirements apply:

SAN connectivity

Virtual provisioning

Unity scalability

Capacity requirements

Competing workloads

This section addresses general considerations that arise when you connect HANA to Unity arrays.

Host connectivity

The HANA nodes connect to the Unity arrays through a Fibre Channel SAN. SAN components require a minimum 8Gb/s link speed, and the SAN topology must follow best practices for all redundant components and links.

General SAN considerations

The connectivity, which includes host HBAs, SAN ports, switches, and array frontend ports, requires careful planning. Unity provides multiple options for front-end connectivity through on-board ports directly on the DPE and optional I/O modules whose configuration must match between SPs. Fibre Channel I/O module ports use 16 Gb SFPs. 16 Gb FC is recommended for the best performance. All Fibre Channel ports can negotiate to lower speeds.

The SAP HANA KPIs for TDI deployments require a maximum bandwidth of 400 MB/s per HANA node. If, for example, ten nodes are connected in a SAN to a Unity array, a total bandwidth of 4000 MB/s is required. Assuming a 16 Gb/s front-end port provides approximately 1500 MBps bandwidth, four dedicated 16 Gb/s front-end ports are recommended to support 10 HANA nodes (4 x 1500 MB/s = 6000 MB/s), two on each SP, to facilitate high availability, load-balancing, and continued connectivity in the event of SP failure.

While this maximum bandwidth requirement is only seen in the unlikely event that all nodes have this requirement simultaneously, it is one of the SAP HANA certification criteria that the storage arrays must sustain this peak workload.

This requirement does not just affect the storage front-end configuration. In the example with ten nodes, the complete path through the SAN network must be configured to support the maximum bandwidth also.

SAN connectivity



HBA ports

Each HBA port (initiator) creates a path for I/Os between the host and the SAN switch, which then continues to the Unity storage. If a host only uses a single HBA port, it will have a single I/O path that serves all I/Os. Such a design is not advisable, because a single path does not provide high availability and also risks a potential bottleneck during high I/O activity due to the lack of additional ports for load-balancing.

A better design provides each HANA server with at least two HBA ports, preferably on two separate HBAs. The additional ports provide more connectivity and also allow the Linux DM-MPIO to load-balance and failover across HBA paths. Unity storage processor connectivity for HANA persistence

Unity is a unified array providing block and file connectivity. Even though file storage can be used in a HANA environment for different purposes (such as PXE-boot and shared file systems), the SAP TDI certification of the Unity series array applies to block Fibre Channel (FC)-attached HANA persistence (data and log) only.

Special attention is required when you connect HANA nodes to the front-end FC ports of a Unity array. The Unity series provides flexible connectivity options through UltraFlex IO modules for both the file for NFS/SMB connectivity and the block storage for FC and iSCSI host connectivity.

The block connectivity for the SAP HANA persistence requires the EMC UltraFlexTM I/O

FC module (block only) on each storage processor with 4 x 16 GB/s FC ports. Each Unity model supports up to two UltraFlex I/O modules per SP.

Each HANA node must connect to a minimum of two FC ports on each storage processor. Figure 5 shows the recommended FC port connectivity on an UltraFlex I/O module on each storage processor.

Figure 5. Rear view of Unity DPE To achieve full I/O performance for production HANA deployments, implement the following FC port requirements for a Unity array:

Dedicate FC ports to HANA and do not share them with non-HANA applications.

Never connect a single HBA to both ports of the same I/O module.

Balance FC ports used for HANA across all available I/O modules.

Use 16 Gb/s FC ports (recommended). 10 Gb/s iSCSI or Fibre Channel over Ethernet (FCoE) have not been validated for SAP HANA.



Solution Guide

Unity arrays can use EMC Virtual Provisioning™ to provide capacity to an application. The capacity is allocated using Virtual Provisioning data devices and provided through storage pools based on the disk technology and RAID type.

HANA persistence (data and log) for production HANA installations

For production HANA installations, EMC recommends using the flash drives for the HANA persistence (data and log volumes) to meet the SAP HANA KPIs.

Using flash devices provides benefits for production HANA installations:

Sub-millisecond latencies for small block sizes on the log volume

Reduced HANA startup times when data is read from the data volume into memory

Reduced HANA host auto-failover times in scale-out deployments when a standby node takes over the data from a failed worker node

Reduced HANA backup times when the backup process needs to read the data from the data volume

RAID protection

Flash drives successfully meet the SAP HANA performance KPIs for the HANA persistence. EMC recommends the following RAID protection for HANA production systems:

Unity all-flash models with RAID5 8+1 on the extreme performance tier for both data and log devices.

Unity hybrid models use RAID5 8+1 (flash) on the extreme performance tier for both data and log devices.

If there is not enough flash capacity available it is possible to use a FAST VP enabled storage pool RAID5 8+1 (flash) on the Extreme performance tier for data devices and RAID5 4+1 (SAS)on the performance tier for log devices.

A single RAID group RAID5 8+1 (flash), capable of supporting up to three HANA nodes.

Storage pools

EMC recommends creating one storage pool for all HANA data volumes and HANA log volumes in a Unity array when using both an all-flash and a hybrid model.

When you use either the all-flash model or a hybrid model, create one storage pool on the extreme performance tier (Flash).

(Optional): When you use the hybrid model, create one FAST VP-enabled storage pool across the extreme performance tier (flash) and performance tier (SAS).

Virtual provisioning recommendations



HANA persistence for nonproduction HANA installations on Unity hybrid models

Although the SAP performance KPIs do not apply to nonproduction HANA installations, those installations are still critical components in an overall SAP landscape. EMC recommends using the SAS drives for all nonproduction HANA installations on the Unity hybrid models when you provision storage.

HANA installation (/hana/shared/) on Unity hybrid models

When using NAS in Unity arrays to provide the NFS share for the HANA scale-out systems, the NL-SAS or SAS drives are sufficient when you provision additional capacity for the /hana/shared on the Unity hybrid models.

Operating system boot image on Unity hybrid models

Using the NL-SAS or SAS drives for the operating system boot image on the Unity hybrid models is sufficient.

Use Table 3 as a guideline to estimate the initial number of production HANA nodes that can be connected. These guidelines are based on our performance tests on a Unity 400 using the SAP hwcct tool. The tests were executed without competing workloads.

The HANA node numbers listed in Table 3 represent an initial guideline to help you determine the number of HANA worker nodes that can be connected to the Unity array for an existing or planned HANA production environment. The actual number of production HANA nodes that can be connected to a Unity array in a customer environment might be higher or lower than the number listed in Table 3. The number depends on the actual workload. Use the HANA hwcct tool with scenario HANA-HWC-ES 1.1 in customer environments to validate the HANA performance and determine the maximum number of HANA hosts on a specified storage array.

EMC recommends running regular HANA health checks to verify the performance of the underlying storage environment. HANA configuration mini-checks are described in SAP Note 1969700 and SAP Note 1999930.

Table 3. Unity scalability for HANA production systems

Model Number of HANA worker nodes Dedicated 16 GB/s FC-ports per storage processor/array

Unity 300 / Unity 300F

5 2/4


10 2/4


12 3/6


16 3/6

Note: Scalability of other Unity models was determined by extrapolating the Unity 400 test results using the performance characteristics of the other models.

Unity scalability



Solution Guide

Every HANA node requires storage devices and capacity for the following:

Operating system boot image

HANA installation (/hana/shared)

HANA persistence (data and log)

Backup

Note: The formulas for capacity sizing in the SAP HANA Storage Requirements White Paper are subject to change by SAP. Always check these formulas before you determine capacity requirements.

Operating system boot image

When the HANA nodes boot from a volume on Unity (boot from SAN), the required capacity for the operating systems must be included in the overall capacity calculation for the HANA installation. Every 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 in the “Booting from SAN” section of the EMC Host Connectivity Guide for Linux.

HANA installation (/hana/shared/)

To install the HANA binaries, as well as the configuration files, traces, and logs, every HANA node requires access to a file system mounted under the local mount point /hana/shared/. In a HANA scale-out cluster, a single shared file system is required and must be mounted on every node. Most HANA installations use an NFS file system for this file system. Unity all-flash and hybrid arrays can provide this file system with the NAS option. The size of the /hana/shared/ file system can be calculated using the latest formula in the SAP HANA Storage Requirements White Paper. Version 2.7 (February 2016) used the following formulas for calculation:

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

HANA persistence (data and log)

The HANA in-memory database requires disk storage to:

Maintain the persistence of the in-memory data on disk to prevent a data loss due to a power outage and to allow a host auto-failover, where a standby HANA host takes over the in-memory data of a failed worker host in scale-out installations

Log information about data changes (redo log)

Capacity requirements



Every HANA node (scale-up) or worker node (scale-out) requires two disk volumes to save the in-memory database on disk (data) and to keep a redo log (log). The size of these volumes depends on the anticipated total memory requirement of the database and the RAM size of the node. To prepare the disk sizing, SAP provides several tools and documents, as described in the SAP HANA Storage Requirements White Paper. Version 2.7 (February 2016) of this document provides the following formula to calculate the size of the data volume:

Sizedata = 1.2x net disk space for data

where “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 “net disk space” must be divided by the number of HANA worker nodes in the cluster. For example, if the 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 net disk space is unknown at the time of the storage sizing, EMC recommends using the RAM size of the node plus 20 percent free space for a capacity calculation of the data file system.

The size of the log volume depends on the RAM size of the node. The SAP HANA Storage Requirements White Paper provides the following formulas to calculate the minimum size of the log volume:

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

Backup

HANA supports backup to a file system or use of SAP-certified third-party tools. EMC supports data protection strategies for HANA backup using EMC Data Domain® and NetWorker. Although a HANA backup to an NFS file system on a Unity All Flash or Hybrid array is possible, EMC does not recommend backing up the HANA database to the storage array where the primary persistence resides. If you plan to back up HANA to an NFS file system on a different Unity array, refer to the SAP Storage Requirements White Paper for details 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 kept on disk.

When adding workloads to the Unity system, consider the reported CPU utilization rates as well as the capacity and IOP sizing. Brief spikes of high utilization are normal and expected on any Unity system. The EMC Unity: Best Practices Guide provides details on sustained CPU utilization and recommended operating ranges that influence whether the system can accept additional workloads.

In highly consolidated environments, HANA, as well as other databases and applications, competes for storage resources. The “host I/O limits” quality of service (QoS) feature can be used to control noisy neighbors and protect the HANA production system performance.

Competing workloads



Solution Guide

Host I/O limits The ability to limit the number of IOPS serviced by the Unity system is known as host I/O limits. Host I/O limits can be applied on LUNs, VMware vStorage VMFS datastores, and their associated snapshots. Use host I/O limits to limit incoming host activity on the basis of IOPS, bandwidth, or both. You can enforce limits on individual resources, or you can share a limit among a set of resources.

Host I/O limits can be effective in consolidated environments if there is an overload on the storage resources that affects the performance of more critical applications, such as production HANA installations. To protect the performance of HANA production systems, consider configuring host I/O limits on LUNs, datastores of non-HANA applications, or HANA nonproduction systems to limit the total IOPs or bandwidth, which might otherwise consume a large portion of the system’s resources.

Configuring Unity storage for HANA using EMC Unisphere for Unity



The Unity internal architecture eliminates complex configurations and tuning steps. You can use EMC Unisphere for Unity to complete the integral storage configuration tasks required to:

Create the SAP HANA hosts

Create a storage pool

Create a NAS Server

Create a file system and NFS share

Create SAP HANA volumes and map the volumes to the SAP HANA nodes

Configure FAST VP

Figure 6 shows the Unisphere for Unity interface that enables you to perform these tasks.

Figure 6. EMC Unisphere for Unity

Use the step-by-step instructions in the following sections as an example.

Each HANA node must have two host bus adapter (HBA) ports that are zoned to the FC ports of the Unity I/O modules.

After the HANA nodes are started, if the zoning is correct, the host initiators are visible to the Unity module.

To create an SAP HANA host:

1. Select Access > Hosts in the left panel. The Hosts page appears.

2. To add an SAP HANA host, click the plus sign in the upper left corner and select Host. The Add a Host screen appears.

Creating a host



Solution Guide

3. Type a name for the new SAP HANA host and (optionally) a description of the host. Click Next.

4. On the OS and Network Address page, specify a host operating system and network address. Although the operating system information is not required, it allows for more specific configuration and troubleshooting instructions. The network address (name or IP address) is required to customize access to the NFS share. Click Next.

5. On the Select iSCSI Initiators page:

If you are using iSCSI initiators, from the list of auto-discovered initiators select the iSCSI initiators the host will use to access storage resources. If you do not find the initiator you want in the list, click Create Initiator to add it manually and then select that initiator from the list of manually added initiators. Click Next.

If you are not using iSCSI initiators, click Next.

6. On the Select Fibre Channel Initiators page, from the list of auto-discovered initiators (shown in Figure 7), select the FC initiators that the host will use to access storage resources.

If you do not find the initiator you want in the list, click Create Initiator to add an initiator manually, and then select it from the list of manually added initiators. Click Next.

Figure 7. Adding a Host – Select Fibre Channel Initiators screen

7. On the Review Host Configuration page, review all the information you entered for the SAP HANA host and then click Finish to create the host.

A pool is a set of disks that provide specific storage characteristics for the resources that use them. For example, the pool configuration defines the types and capacities

Creating a pool



of the disks in the pool. For physical deployments, the pool configuration also defines the RAID configurations.

EMC recommends creating one storage pool for all HANA data volumes and log volumes in a Unity array when you are using either an all-flash model or a hybrid model. When using the all-flash model, create one storage pool on the extreme performance tier. When you use the hybrid model, create one storage pool across the extreme performance tier and the performance tier.

Note: When you use the hybrid model and create one storage pool across the extreme performance tier and performance tiers, ensure that FAST VP is enabled.

To create an all-flash storage pool with flash for provisioning the HANA persistence on the Unity hybrid model:

1. Select Storage > Pools in the left panel. The Pools page appears.

2. To add a storage pool, click the plus sign in the upper left corner. The Create Pool screen appears.

3. Enter a name and (optionally) a description of the storage pool. Click Next.

4. On the Select Storage Tiers page (shown in Figure 8), select the required tier or tiers for the storage pool:

Extreme performance tierThe extreme performance tier provides fast access times for resources demanding the quickest response time. Databases can achieve their best performance when using this tier.

Performance tierProvides high, all-around performance with consistent response times, high throughput, and good bandwidth. This tier is appropriate for database resources accessed centrally through a network.

Capacity tier Provides high storage capacity with generally lower performance. This tier is appropriate for storing large amounts of primarily static data (such as video, audio, and image files) for users and applications without strict performance requirements.



Solution Guide

Figure 8. Creating a pool – Select Storage Tiers screen

5. Under the Selected Tiers, change the RAID configuration, if required.

6. Click Next. The Select Amount of Storage page appears, as shown in Figure 9.

Note: Flash drives are required to meet the SAP HANA performance KPIs for the HANA persistence successfully. With the Unity All Flash or Hybrid models, EMC recommends using RAID5 8+1 on the extreme performance tier for both data and log devices. With a FAST VP-enabled storage pool on the Unity hybrid model, EMC recommends using RAID 5 8+1(flash) on the extreme performance tier for data devices and RAID 5 4+1(SAS) on the performance tier for log devices.

Figure 9. Creating a pool – Select Amount of Storage screen



7. From the drop-down list, select the usable capacity required for the storage pool. Click Next.

8. Review all the information you entered for the storage pool, as shown in Figure 10, and then click Finish to create the storage pool.

Figure 10. Creating a pool – Review Selection screen

Each SAP HANA node requires two volumes for persistence, one for data and one for log. To create the SAP HANA volumes:

1. Select Storage > Block in the left panel. The LUNs page appears.

2. To create a LUN, click the plus sign in the upper left corner. The Create a LUN screen appears.

3. Enter a name and (optionally) a description of the new LUN. Click Next.

4. On the Configure Storage Characteristics page, select the pool in which to create the LUN.

If there are multiple tiers in the storage pool, select a tiering policy and enter the required size of the LUN, as shown in Figure 11. Click Next.

Note: The default selection is THIN.

Creating a volume and mapping to the SAP HANA node



Solution Guide

Figure 11. Creating a LUN – Configure Storage Characteristics screen

Note: Use the SAP HANA Storage Requirements White Paper to determine the final capacity of the data and log LUNs. In the following examples, we used 256 GB for the log LUN and 614 GB for the data LUN.

5. In the Select Host Access page, check the host that will have access to the newly created LUN, as shown in Figure 12. Click OK.



Figure 12. Creating a LUN – Select Host Access page

6. On the Summary page, review all the information you entered for the new LUN, as shown in Figure 13, and then click Finish to create a LUN that is visible to the SAP HANA host.

Figure 13. Create a LUN - Summary



Solution Guide

FAST VP is an automated feature requiring very little manual intervention.

If sufficient flash capacity is not available, you can use a FAST VP-enabled storage pool RAID 5 8+1 (flash) for data devices and RAID 5 4+1 (SAS) for log devices to meet the SAP HANA performance KPIs. FAST VP enables the system to retain the most frequently accessed or important data on fast, high-performance disks and to move the less frequently accessed and less important data to lower-performance, cost-effective disks. For storage pools, FAST VP:

Monitors the usage of the data in a tiered pool. Tiered pools are heterogeneous pools that are configured with multiple classes of disks (flash plus SAS or NL-SAS).

Depending on the tiering policy, uses the monitoring statistics to relocate data chunks automatically, at a 256 MB granularity, to other tiers within the pool. For example, the Start High then Auto-Tier policy relocates data to the storage tier that is best suited for that data based on relative activity.

Performs load-balancing across the disks in tiered and non-tiered pools.

Note: FAST VP can use all supported disk types except for the SAS Flash 3 disk.

To enable FAST VP:

1. In the Unisphere GUI, click the Update System Setting in the upper right corner. Under Software and Licenses > License Information, check that FAST VP is licensed. If not, you must acquire a license.

2. Select Storage Configuration > FAST VP and review the settings shown in Figure 14. You can change the Data relocation rate if required – the default is Medium.

Enabling FAST VP



Figure 14. FAST VP settings

3. To modify the relocation schedule, click the Modify data relocation schedule link. The Modify data relocation schedule page appears, as shown in Figure 15.

Figure 15. Modify data relocation schedule



Solution Guide

4. Ensure that the Schedule data relocation checkbox is checked, and then select the desired time and days to perform the data relocation. Click OK, and then Apply.

In an SAP HANA scale-out implementation, install the SAP HANA database binaries on a shared file system that is exposed to all hosts of a system under the /hana/shared mount point. A NAS server can provide access to the shared HANA file systems.

To create a NAS server:

1. Select Storage > File on the left side. The File page appears.

2. To create a NAS server, first click the NAS Servers link and then click the plus sign in the upper left corner. The Create a NAS Server screen appears.

3. Enter a server name and select a pool. Click Next. The Configure NAS Server Address page appears, as shown in Figure 16.

Figure 16. Configure NAS Server Address

4. Enter the following information for the NAS server:

Ethernet Port

IP address

Subnet Mask/Prefix Length10

Gateway

VLAN ID

Click Next. The Configure Sharing Protocols screen appears, as shown in Figure 17.

Creating a NAS Server



Figure 17. Configure Sharing Protocols screen

5. Select the Linux/Unix shares (NFS) checkbox and enable NFSv4. Click Next.

6. (Optional) On the Unix Directory Service page, configure NIS as the UDS for the NAS server. Click Next.

7. (Optional) On the DNS page, configure the DNS for the server. Click Next. The Review Your Selections page shown in Figure 18 appears.

Figure 18. Review Your Selections screen



Solution Guide

8. If you are satisfied that the information is correct, click Finish to create the NAS server.

Ensure there is a NAS server configured to support the file system that you want (NFS) and a pool with enough available storage space.

To create a NAS server:

1. Select Storage > File in the left panel. The File page appears.

2. Click the File Systems link and then click the plus sign in the upper left corner. The Configure the Protocols the File System Supports screen appears.

3. Select the NAS Server that was previously configured for HANA. Click Next. The Provide a Name and Description page appears.

4. Enter a name and description for the file system. Click Next. The Configure the File System Storage Characteristics page appears, as shown in Figure 19.

Figure 19. Configure the File System Storage Characteristics screen

5. Select the pool in which to create the file system, and then enter the size of the file system required and the tiering policy requirements. Click Next. The Configure the Initial Share page appears, as shown in Figure 20.

Creating a file system and NFS share



Figure 20. Configure the Initial Share screen

6. Check the NFS Share (Linux/Unix) and enter a name for the share. Click Next. The Configure Access page appears.

7. To allow access to hosts, click the plus symbol in the Customize access for the following hosts screen. The Select Host Access page appears, as shown in Figure 21.

Figure 21. Select Host Access screen



Solution Guide

8. Select the Access Type required from the list box and check the hosts that need access to the NFS share.

Note: For the hosts to be visible, a network address must be assigned to the host.

Click OK and then click Next. The Summary page appears, as shown in Figure 22.

Figure 22. Summary

9. Review the information you have provided. If you are satisfied that it is correct, click Finish. The file system and NFS share are created.

Accessing Unity storage from the SAP HANA nodes



The SAP HANA database requires Linux SUSE SLES11 (or later) or Red Hat RHEL 6.5 (or later) on the SAP HANA nodes. To access the Unity block devices from the SAP HANA nodes, ensure that zoning is correctly configured based on SAN best practices. Refer to the EMC Unity Storage Array Host Configuration Guide for details.

To access the block devices from the SAP HANA nodes, first enable native Linux multipathing. Follow the steps described in the EMC Host Connectivity Guide for Linux to enable DM-MPIO on Red Hat Linux RHEL 6.5 or SUSE SLES11. Figure 23 shows an example of a multipath.conf file.

Figure 23. Sample multipath.conf file

The SAP HANA persistent devices are visible on an SAP HANA worker host after a restart or a rescan (using the rescan-scsi-bus.sh command). To verify that all devices are present and that each device has the number of active paths you configured (as shown in Figure 24), type the following command:

Multipath –ll

Figure 24. Sample Multipath -ll

Enabling native Linux multipathing (DM-MPIO)



Solution Guide

EMC uses the UUID of the LUN to identify the correct storage devices. To view the identifier of a Unity LUN, go to the Volume tab in the configuration workspace in the EMC Unisphere for Unity.

Note: Linux adds a preceding 3 to the storage UUID.

The XFS file system provides the best performance for both SAP HANA data and log block devices.

To format a block device with the XFS file system, run the following command on the SAP HANA node:

$ mkfs.xfs /dev/mapper/3600601600a503e00690f195784759af8

Note: Run this command for all block devices.

If for some reason you must expand a file system, run the xfs_growfs command on the Linux host after you expand the volume on the Unity array.

In an SAP HANA scale-out environment with worker and standby nodes, the SAP HANA storage connector for FC (fcClient) mounts and unmounts the devices to the SAP HANA nodes.

In addition to mounting the devices, the storage connector also writes SCSI-3 persistent reservations (PRs) to the devices using the Linux sg_persist command. This operation, which is called I/O fencing, ensures that at a given time, only one SAP HANA worker host has access to a set of data and log devices.

The storage connector API is controlled in the storage section of the SAP HANA global.ini file, as shown in Figure 25. The storage section of the file contains entries for the block devices with optional mount options. You can run the multipath –ll command on the SAP HANA hosts to determine the worldwide identifiers (WWIDs) of the partition entries.

Figure 25. Sample global.ini file

XFS file system

SAP HANA storage connector

SAP HANA global.ini file

Conclusion


Refer to the SAP HANA Administration Guide and the SAP HANA Server Installation and Update Guide on the SAP Help Portal for information on the SAP HANA storage connector and how to configure the global.ini file.

Note: SAP HANA can only be installed on certified server hardware. The installation must be run by a certified HANA expert.

The base layer of HANA provides two file I/O interfaces:

Simple File: SimpleFile is used for small, simple I/O requests on configuration files, traces, and so on. It uses lightweight, platform-independent wrappers around system calls.

FileFactory & File:The FileFactory & File I/O interface is used for huge, complex streams of I/O requests on the data and log volumes and for backup and recovery. It uses synchronous and asynchronous I/O operations.

The HANA file I/O layer can be configured with configuration parameters to optimize file I/Os for a given file system (the Linux XFS file system is used on all EMC storage LUNs for the HANA persistence) and storage array

When the HANA persistence is installed on Unity LUNs, set the following file I/O layer parameters for optimal I/O processing after the initial HANA installation has been completed:

max_parallel_io_requests=256 async_read_submit=on async_write_submit_blocks=all

Use the HANA hdbparam command as <sid>adm in the Linux shell:

# su - <sid>adm

# hdbparam –p # lists current parameter setting

# hdbparam –-paramset fileio.max_parallel_io_requests=256

# hdbparam –-paramset fileio.async_read_submit=on

# hdbparam –-paramset fileio.async_write_submit_blocks=all

Note: The previous instructions for tuning file I/O parameters are based on SAP HANA 1.0 SPS 11. Future SAP HANA versions might allow these parameters to be set in configuration files. Refer to the latest SAP HANA documentation for details.

Conclusion

Using SAP HANA in TDI deployments with EMC Unity enterprise storage arrays provides many benefits, including reducing hardware and operational costs, lowering risks, and increasing hardware vendor flexibility.

All Unity flash and hybrid arrays are certified by SAP and can be used for production and nonproduction HANA installations and for single-node or scale-out systems.

Optimizing file I/Os after HANA installation

Summary

Conclusion


Solution Guide

Customers can now easily transition to this new architecture using SAP HANA, while relying on EMC services to minimize risk.

During our tests with HANA on Unity, we observed that:

The SAP HANA-HWC-ES 1.1 certification scenario makes higher disk configuration demands than the HANA-HWC-ES 1.0 certification.

Production HANA installations on Unity systems require SSDs for the HANA persistence to meet the SAP HANA KPIs.

Using SSDs for the HANA persistence provides the following significant benefits:

Initial array and disk configuration based on capacity without the need to take spindle count into consideration.

Reduced HANA startup and host auto-failover times

Reduced HANA backup times

Findings

References


References

The following documentation on EMC.com or EMC Online Support provides additional relevant information. Access to these documents depends on your login credentials. If you do not have access to a document, contact your EMC representative.

VMware Virtualized SAP HANA with EMC Storage Solution Guide

EMC Host Connectivity Guide for Linux

Introduction to the Unity Platform - A Detailed Review

EMC Unity: BEST PRACTICES GUIDE - Performance and Availability

EMC Unity: Unisphere Overview

EMC Unity: Unity File System - A Detailed Review

You can find the following SAP HANA documentation at http://help.sap.com/hana/:

SAP HANA Tailored Data Center Integration

SAP HANA Master Guide

SAP HANA Server Installation and Update Guide

SAP HANA Studio Installation and Update Guide

SAP HANA Technical Operations Manual

SAP HANA Administration Guide

Web resources

SAP HANA Storage Requirements

SAP HANA Appliance

SAP HANA One

SAP HANA Enterprise Cloud

Note: The following documentation requires an SAP username and password.

hwcct note

Note 1943937 - Hardware Configuration Check Tool - Central Note

EMC documentation

SAP HANA documentation

http://www.emc.com/

https://support.emc.com/

http://www.emc.com/collateral/technical-documentation/h14721-vmware-virtualized-sap-hana-emc-storage-sg.pdf

http://www.emc.com/collateral/technical-documentation/h14721-vmware-virtualized-sap-hana-emc-storage-sg.pdf

http://www.emc.com/collateral/TechnicalDocument/docu5128.pdf

http://www.emc.com/collateral/white-papers/h15084-emc-unity-introduction-to-the-unity-platform.pdf

http://www.emc.com/collateral/white-papers/h15093-emc-unity-best-practices-guide.pdf

http://www.emc.com/collateral/white-papers/h15085-emc-unity-unisphere-overview.pdf

http://www.emc.com/collateral/white-papers/h15087-emc-unity-unity-file-system.pdf

http://help.sap.com/hana/

http://help.sap.com/saphelp_hanaplatform/helpdata/en/0b/15a92d554c4941a452c9ca127f8c70/content.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/11/6743577e504d3291e9061fd6fe82bf/frameset.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/7e/b0167eb35e4e2885415205b8383584/frameset.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/c1/3cec2b7c2c46bdb0762ce5f1410260/frameset.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/f7/62839ac714478ba443fa093007c6d2/frameset.htm

http://help.sap.com/saphelp_hanaplatform/helpdata/en/33/0e5550b09d4f0f8b6cceb14a64cd22/frameset.htm

http://go.sap.com/documents/2015/03/74cdb554-5a7c-0010-82c7-eda71af511fa.html

http://help.sap.com/hana_appliance

http://help.sap.com/hana_one

http://www.saphana.com/entcloud

https://service.sap.com/sap/support/notes/1943937

Date post:	18-Oct-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Storage Configuration Best Practices for SAP HANA Tailored ... · Unity uses the latest technology...

Documents