Storage Configuration Best Practices for SAP HANA TDI on ...

Solution Guide

STORAGE CONFIGURATION BEST PRACTICES FOR SAP HANA TAILORED DATA CENTER INTEGRATION ON EMC VNX SERIES UNIFIED STORAGE SYSTEMS Integrating SAP HANA into an EMC VNX storage system

EMC Solutions

Abstract

This solution guide provides information on a new concept that overcomes limitations of the current SAP HANA Appliance Model. Using Tailored Data Center Integration (TDI) on EMC VNX storage systems, customers can integrate SAP HANA into an existing, well-established data center infrastructure, providing multiple benefits.

April 2017

Copyright

2 Storage Configuration Best Practices for SAP HANA TDI on EMC VNX Solution Guide

Disclaimer

This document outlines a general product direction and should not be relied on in making a purchase decision. This document is not subject to your license agreement or any other agreement with EMC or SAP. Neither EMC nor SAP has an obligation to pursue any course of business outlined in this document or to develop or release any functionality mentioned in this document. This document and the strategy and possible future developments of EMC or SAP are subject to change and may be changed by EMC or SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. EMC and SAP assume no responsibility for errors or omissions in this document, except if such damages were caused by EMC or SAP intentionally or through gross negligence.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of EMC and SAP AG.

Copyright © 2017 SAP. All Rights Reserved.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in other countries.

See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Copyright © 2017 EMC Corporation. All rights reserved. Published April 2017 in the USA.

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, EMC VNX, EMC Unisphere, 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 VNX Solution Guide

Part Number H13047.4

http://www.sap.com/corporate-en/legal/copyright/index.epx

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

Contents


Contents

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

Introduction ....................................................................................................................................... 5

VNX storage configuration overview ................................................................................................... 5

Configuring VNX storage with EMC Unisphere for VNX ....................................................................... 12

Accessing VNX storage from the SAP HANA nodes............................................................................. 19

Conclusion ....................................................................................................................................... 22

References ....................................................................................................................................... 23

Executive summary


Executive summary

Many customers seek solutions to fulfill the requirements of an industrialized data center. The SAP High performance Analytics Appliance (HANA) in-memory computing platform, along with EMC® enterprise storage, extends the possibilities for enterprises.

These data centers, whether they run traditional SAP applications, including SAP HANA, or non-SAP applications, must provide the following:

Efficiently managed availability, capacity, performance, and health in the SAP landscape

High availability and application mobility

Disaster recovery

Data protection

By default, an SAP HANA appliance includes integrated storage, compute, and network components. SAP has defined key performance indicators (KPIs) for storage subsystems, such as I/O throughput and latency, to ensure that the overall infrastructure forms an environment ready for HANA.

You also can deploy SAP HANA appliances using a Tailored Data Center Integration (TDI) approach. With this approach, you can connect certified servers to existing enterprise storage systems. This reduces the time-to-value, risk, and costs of an overall HANA adoption.

Using the SAP HANA hardware configuration and check tool (hwcct), EMC did extensive testing on the VNX series unified storage system in accordance with the SAP certification scenario HANA-HWC-ES-1.0. Based on these tests, this solution guide describes a VNX storage configuration that meets SAP performance requirements (the SAP HANA TDI KPIs for data throughput and latency) and ensures the highest availability for database persistence on disk.

Note: The VNX configuration requirements described in this paper apply only to production HANA appliances. Non-production HANA appliances, which do not have to meet the KPIs, can be deployed in TDI environments when the storage meets the HANA capacity requirements.

SAP recommends that TDI customers run the hwcct tool in their production environment to ensure that the customer-specific HANA TDI implementation also meets the SAP performance criteria. Only hwcct tests based on the HANA-HWC-ES-1.0 certification scenario will meet the SAP performance KPIs. For more information about the certification scenarios, refer to SAP Note 943937.

This solution guide also includes step-by-step instructions for configuring SAP HANA storage devices on a VNX array.

Business case

Introduction


Introduction

Until now, customers who used the SAP HANA appliance model experienced the following limitations:

Limited flexibility for servers and storage

Inability to use existing data center infrastructure and operational processes

Fixed sizes for storage capacities

This solution guide describes a solution that uses SAP HANA in a TDI deployment scenario for EMC VNX enterprise storage. This solution reduces hardware and operational costs, lowers risks, and increases hardware vendor flexibility.

All configuration recommendations in this document are based on the performance tests and results used to meet the SAP KPIs for SAP HANA TDI.

This document provides best practices and tips for deploying the SAP HANA database on VNX series unified storage systems and describes the following:

Key solution technologies

Key business benefits of using VNX storage systems with SAP HANA

How to configure VNX storage with EMC Unisphere® for VNX

How to access VNX storage from the SAP HANA nodes

This solution guide is intended for system integrators, systems or storage administrators, customers, partners, and members of EMC Global Services who need to configure a VNX storage array to be used in a TDI environment for SAP HANA.

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

Authors: Werner Katzenberger, Aighne Kearney.

VNX storage configuration overview

The specific SAP HANA I/O workload, which can be simulated using the SAP HANA hardware configuration and check tool (hwcct) with the HANA-HWC-ES 1.0 scenario, requires special considerations for the configuration of persistence for data and log volumes on VNX storage arrays.

The VNX system delivers the high performance required for the persistent storage of an SAP HANA database. The I/O workload on SAP HANA has two major components:

Random I/O on the data volume

Sequential I/O on the log volume

Purpose

Scope

Audience

We value your feedback!

mailto:[email protected]?subject=Feedback:Storage%20Configuration%20Best%20Practices%20for%20SAP%20HANA%20TDI%20on%20EMC%20VNX%20Solution%20Guide%20H13047.4



SAP HANA uses different block sizes for log volumes and data volumes:

I/O for log volumes uses 4 KB, 16 KB, and 1 MB block sizes.

I/O for data volumes uses 4 KB, 16 KB, 64 KB, 1 MB, 16 MB, and 64 MB block sizes.

Figure 1 shows the VNX models certified by SAP to be used in an SAP HANA TDI environment. They are:

EMC VNX5400™

EMC VNX5600™

EMC VNX5800™

EMC VNX7600™

EMC VNX8000™

Figure 1. EMC VNX series unified storage systems certified for SAP HANA TDI

Note: EMC VNX5200™ has not been tested for the SAP HANA TDI certification of the VNX series unified storage systems.

Depending on the number of HANA nodes used on a certified VNX array and the specific performance requirements of HANA, certain configurations require the array to be dedicated to the SAP HANA appliance and not used for other purposes.

VNX series scalability with HANA on page 10 provides further details on scalability and limitations.

VNX 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, shared file systems, and so on), the SAP TDI certification of the VNX series array applies only to block Fibre Channel (FC)-attached HANA persistence (data and log).

The block connectivity for the SAP HANA persistence requires block EMC UltraFlexTM I/O modules on the storage processors with 4 x 8 GB/s FC ports.

VNX models certified for HANA TDI

VNX storage processor connectivity for the HANA persistence



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

Figure 2. Recommended FC port connectivity

VNX series scalability with HANA provides details about the number of I/O modules and ports required per VNX array.

In an SAP HANA scale-out deployment, a shared file system must be mounted on all nodes of the scale-out installation. This file system is used for the SAP HANA installation. The VNX unified array is perfectly suited to deliver file services in addition to the FC block connectivity on the storage processors.

Although SAP HANA has no specific performance requirements for the shared file system, EMC recommends using 10 GbE interfaces with one active and one standby Data Mover.

EMC recommends the following disk configuration in a VNX for SAP HANA:

10,000 rpm or 15,000 rpm SAS disks

Two RAID groups in a RAID5 8+1 configuration (9 disks) for 1 or 2 HANA worker nodes with striped meta devices across the two RAID groups, as shown in Figure 3.

VNX Data Mover connectivity for the HANA shared file system

Disk configuration for HANA



Figure 3. Recommended meta volume configuration

Disk size depends on capacity requirements, as shown in Table 1.

Note: Only meta devices on RAID groups meet the SAP performance requirements for SAP HANA TDI deployments in the HANA-HWC-ES-1.0 certification scenario.

SAP HANA capacity requirements for persistence

Table 1 shows the usable capacity of a single RAID group in a RAID 5 (8+1) configuration based on the per-disk size.

Table 1. Disk pool capacity for different disk sizes

Disk size Usable capacity per RAID group RAID5 (8+1)

300 GB 2,145 GB

600 GB 4,288 GB

900 GB 6,560 GB



Note: Even though the usable capacity of a RAID group may exceed the required capacity for the HANA persistence, EMC strongly recommends not using fewer disks or a different RAID configuration. Otherwise, the SAP HANA performance requirements will not be met.

In general, the capacity required for the SAP HANA persistence on disk depends on the in-memory database size and the RAM size of the HANA servers. Every SAP HANA customer must perform memory and CPU sizing as the first step in sizing an SAP HANA deployment.

For new SAP HANA implementations, you can determine the memory and CPU requirements for an SAP HANA system using the HANA version of the SAP Quick Sizer tool, which is available on the SAP Service Marketplace website.

For systems that are migrating to SAP HANA, SAP provides tools and reports for proper HANA memory sizing.

After memory requirements have been determined, you can calculate the disk capacity requirements by using the sizing rules provided by SAP in their SAP HANA Storage Requirements white paper.

Each SAP HANA worker node requires two LUNs for the database persistence, a data LUN and a log LUN. Both LUNs must be created as meta-LUNs with one member from two RAID groups, as shown in Figure 3. A best practice is to ensure that data and log LUNs are assigned to different storage processors—for example, the data LUN is owned by storage processor A (SP-A) and the log LUN is owned by SP-B.

The following formulas were used for the persistence in the certification tests and in the configuration examples in Configuring VNX storage with EMC Unisphere for VNX:

Data size = RAM size * 3

Log size = RAM size * 1

For the current sizing requirements, refer to the latest version of the SAP HANA Storage Requirements white paper.

In an SAP HANA scale-out implementation, the SAP HANA database binaries must be installed on a shared file system. The VNX unified array can provide and export an NFS share for this purpose. A specific performance requirement for this share does not exist. You can create the underlying block LUNs from a separate disk pool by using the Unisphere wizards for file.

In the certification tests, we used the following formula to determine the size of the shared file system:

# of HANA nodes * RAM size of a single node

For the current sizing requirements, refer to the latest version of the SAP HANA Storage Requirements white paper.

Capacity considerations

HANA persistence LUNs

HANA shared file system

https://websmp102.sap-ag.de/



The following tables summarize the connectivity and capacity requirements for SAP HANA for each VNX model:

Table 2—Scalability of VNX5400





These tables can be used as a reference for planning SAP HANA TDI with VNX deployments.

Depending on the number of HANA nodes deployed on a specified VNX model, you can share the array with other applications. Usually, if you use more than half of the maximum supported nodes per array, the array must be dedicated to SAP HANA and cannot be shared with other applications. For example, on a VNX5800, which supports a maximum of six HANA nodes, you can run up to three HANA nodes and share the array with other applications. If you are running more than three HANA nodes, the array must be dedicated to the HANA application to ensure that the array meets the HANA performance requirements.

The Total number of disks for the HANA persistence table column does not include the additional disks required for the HANA shared file system. Neither does it include any other capacity that must be provided by the VNX system, such as boot devices, operation systems, and so on. Use the SUSE Write performance file patch for increasing I/O operations on XFS to achieve the best performance and full scalability of the VNX arrays. Use the following or greater kernel from SUSE: 3.0.101-0.15.1.

The HANA nodes numbers listed in the following tables represent an initial guideline to help you determine the VNX array for an existing or planned HANA environment. The actual number of production HANA nodes that can be connected to a VNX might be different. EMC recommends running regular HANA health checks, such as the HANA configuration mini checks described in SAP Note 1969700 and SAP Note 1999930, to verify the performance of the underlying storage environment.

Note: A careful performance analysis of a VNX storage system with existing applications is required before a production SAP HANA can be deployed.

Table 2. Scalability of VNX5400

Number of nodes

Required UltraFlex

IO modules per SP/array

Required FC ports per SP/array

Number of RAID groups required

Total number of disks for the HANA persistence

Is array sharing possible?

1-2 1/ 2 2/4 2 18 Yes

3-4 1/2 4/8 4 36 Yes

5 2/4 6/12 6 54 Yes

VNX series scalability with HANA



Number of nodes

Required UltraFlex






6 2/4 6/12 6 54 No

7-8 2/4 8/16 8 72 No

9-10 3/6 10/20 10 90 No

Note: VNX5400 supports a maximum of 10 HANA nodes.


Number of nodes

Required UltraFlex






1-2 1/ 2 2/4 2 18 Yes

3-4 1/2 4/8 4 36 Yes

5 2/4 6/12 6 54 Yes

6 2/4 6/12 6 54 No

7-8 2/4 8/16 8 72 No

9-10 3/6 10/20 10 90 No



Number of nodes

Required UltraFlex





Array sharing possible?

1-2 1/ 2 2/4 2 18 Yes

3-4 1/2 4/8 4 36 Yes

5 2/4 6/12 6 54 Yes

6 2/4 6/12 6 54 No

7-8 2/4 8/16 8 72 No

9-10 3/6 10/20 10 90 No


Configuring VNX storage with EMC Unisphere for VNX



Number of nodes

Required UltraFlex



Number of pools or RAID groups required



1-2 1/ 2 2/4 2 18 Yes

3-4 1/2 4/8 4 36 Yes

5-6 2/4 6/12 6 54 Yes

7-8 2/4 8/16 8 72 No

9-10 3/6 10/20 10 90 No

11-12 3/6 12/24 12 108 No



Number of nodes

Required UltraFlex





Array sharing possible?

1-2 1/ 2 2/4 2 18 Yes

3-4 1/2 4/8 4 36 Yes

5-6 2/4 6/12 6 54 Yes

7-8 2/4 8/16 8 72 Yes

9-10 3/6 10/20 10 90 No

11-12 3/6 12/24 12 108 No

13-14 4/8 14/28 14 126 No

15-16 4/8 16/32 16 144 No



You can use Unisphere for VNX for all the storage configuration tasks required to create the HANA storage devices. Use the step-by-step instructions in the following sections as an example.

For every SAP HANA worker node, use two RAID groups in a RAID5 (8+1) configuration with nine disks.

Create RAID groups



To create a RAID group:

1. Select Storage > Storage Pools > RAID Groups and click Create.

2. Select RAID5 in RAID Configuration and let the array automatically select 9 (Recommended) disks, as shown in Figure 4.

Figure 4. Create a RAID Group

3. Click OK to create the RAID group.

Each HANA persistent data or log LUN must be created as a striped meta-LUN with two LUNs in two RAID Groups, as shown in Figure 3. To create HANA persistence for data and log of two HANA worker nodes, use the following steps:

1. After the RAID group is ready, right-click the disk RAID group and select Create LUN from the context menu.

2. Under General, as shown in Figure 5, select the User Capacity for the LUN, which must be half of the final DATA or LOG size, create two LUNs of this size, and type the Name of the LUNs and a Starting ID of 1.

Create HANA persistence for data and log



Note: You must determine the final capacity of the data and log metaLUNs using the SAP HANA Storage Requirements white paper. In the following examples, we used 512 GB for the log LUN and 1.5 TB for the data LUN.

Figure 5. Select General properties for the LUN

In this example, the system will create two LUNs with names LOG_RG8_1 and LOG_R8_2. Repeat this step on the same RAID group and create two LUNs for DATA. Then select the second RAID group and create two LUNs for LOG and two LUNs for DATA.

You should have the following single LUNs:

o RAID group 1—LOG_RG8_1, LOG_RG8_2, DATA_RG8_1, DATA_RG8_2

o RAID group 2—LOG RG9_1, LOG_RG9_2, DATA_RG9_1, DATA_RG9_2

3. Select Storage > LUNs. The new LUNs appear, as shown in Figure 6.



Figure 6. Single LUNs

4. To create a metaLUN, right-click on the first LUN (DATA_RG8_1, in this example) and click Expand. The Expand Storage Wizard appears, as shown in Figure 7.

Figure 7. Expand Storage Wizard

5. Select an Expansion Type of Striping, and then click Next, as shown in Figure 8.



Figure 8. Select an expansion type

6. Select the LUN from the other RAID group that you want to use to expand the base LUN, and then click Next, as shown in Figure 9.

Figure 9. Select Unused LUNs

To specify a new LUN capacity, select the Maximum capacity, and then click Next, as shown in Figure 10.



Figure 10. Specify a new LUN capacity

7. To specify new LUN settings, select a Default Owner, accept the default values for Element Size and Alignment Offset, and then click Next, as shown in Figure 11.

Figure 11. Specify new LUN settings

8. Review the Summary settings and click Finish to create the metaLUN, as shown in Figure 12:



Figure 12. Summary

Repeat the steps for the LOG and the DATA metaLUNs and ensure that both LUNs are bound to different storage processors for the default owner. If you create LUNs for multiple HANA nodes, distribute data and log LUNs across the storage processors. For example, if you create six data LUNs and six log LUNs, ensure that each storage processor owns three data LUNs and three log LUNs.

Base the size of the LUNs on the requirements in the SAP HANA Storage Requirements white paper.

Each HANA node must have two host bus adapters (HBAs) that are properly zoned to the FC ports of the VNX I/O modules.

After the HANA nodes are started, the initiators are visible to the VNX and must be registered. Assign the World Wide Name (WWN) initiator to the corresponding HANA node.

To register initiators:

1. Select Hosts > Initiators.

2. Click an initiator that is not yet registered and select Register.

3. Select an Initiator Type of CLARiiON/VNX and a Failover Mode 1 of Active-Passive (PNR), as shown in Figure 13.

If this is the first initiator for the server, select a new host and specify a hostname and IP address. Otherwise, select the corresponding server from the list of existing hosts.

Register initiators

Accessing VNX storage from the SAP HANA nodes


Figure 13. Select initiator and host agent information

4. Click OK to save your changes.

Repeat these steps for all unregistered initiators.

To create storage groups:

1. Select Hosts > Storage Groups, and click Create, as shown in Figure 14.

Figure 14. Create a storage group

2. Select a storage group name, for example, sghana01, and click Apply.

3. Click Connect LUNs and add all persistence LUNs to the storage group.

Note: Do not use 0 as the host LUN ID.

4. After all LUNs are connected, connect the host that has previously been registered to this storage group.


The SAP HANA database requires a Linux SUSE SLES-11 operating system on the HANA nodes. To access the VNX block devices from the HANA nodes, ensure that proper zoning was done in the SAN so that all HBAs (or vHBAs) of the HANA nodes have access to the FC ports on the I/O module, as described in the previous sections.

Create storage groups



Note: The SAP HANA database also supports the Red Hat Enterprise Linux (RHEL) 6.5 operating system.

To access the block devices from the HANA nodes, first enable native Linux multipathing. The Linux Storage Administration Guide provides information on how to enable DM-MPIO on a HANA node.

Note: The commands below are based on the SUSE SLES-11 operating system.

To enable native Linux multipathing:

1. Create an /etc/multipath.conf file with the correct parameters to be set for the VNX system.

You can use the following code sample for RAID group LUNs:

defaults {

user_friendly_names no

}

devices {

device {

vendor "DGC"

product ".*"

product_blacklist "LUNZ"

features "0"

hardware_handler "1 emc"

path_selector "round-robin 0"

path_grouping_policy group_by_prio

failback immediate

rr_weight uniform

no_path_retry 5

rr_min_io 1

path_checker emc_clariion

prio emc

flush_on_last_del yes

fast_io_fail_tmo off

dev_loss_tmo 120

}

}

2. After creating the configuration file, restart the multipath daemon to activate the settings and rescan the new devices:

$ rescan-scsi-bus.sh

$ service multipathd force-reload

The HANA persistence device should be visible.

3. Type the following command to verify that all devices are present and each device has four active paths:

server01:~ # multipath -ll

36006016056303800773847fee517e411 dm-0 DGC ,VRAID

size=512G features='1 queue_if_no_path' hwhandler='1 emc'

wp=rw

|-+- policy='service-time 0' prio=4 status=active

Enable native Linux multipathing (DM-MPIO)



| |- 1:0:1:1 sde 8:64 active ready running

| `- 2:0:7:1 sdw 65:96 active ready running

`-+- policy='service-time 0' prio=1 status=enabled

|- 1:0:0:1 sdb 8:16 active ready running

`- 2:0:6:1 sdt 65:48 active ready running

36006016056303800378ef712e617e411 dm-1 DGC ,VRAID

size=1.5T features='1 queue_if_no_path' hwhandler='1 emc'

wp=rw

|-+- policy='service-time 0' prio=4 status=active

| |- 1:0:0:2 sdc 8:32 active ready running

| `- 2:0:6:2 sdu 65:64 active ready running

`-+- policy='service-time 0' prio=1 status=enabled

|- 1:0:1:2 sdf 8:80 active ready running

`- 2:0:7:2 sdx 65:112 active ready running

If all devices are visible, create file systems on the block devices.

EMC recommends using XFS as the file system for the HANA block devices.

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

$ mkfs.xfs /dev/mapper/3600009700002987004605330303238

Note: Run this command for all block devices.

In a SAP HANA scale-out environment with worker and standby nodes, the SAP HANA Storage Connector API for Fibre Channel (fcClient.py) mounts and unmounts the devices to the HANA nodes.

In addition to mounting the devices, the Storage Connector API also writes SCSI-3 PGR reservations to the devices using the Linux sg_persist command. This is called I/O fencing. It ensures that only one HANA node at a time has access to a set of data and log devices.

SAP HANA global.ini file

The Storage Connector API is controlled in the storage section of the SAP HANA global.ini file. This section of the file contains entries for the block devices with optional mount options.

For the XFS devices, use the following XFS mount options:

relatime

nobarrier (approved from SAP) only for Log devices

inode64

This is an example of a global.ini file:

[persistence]

basepath_datavolumes=/hana/data/ANA

basepath_logvolumes=/hana/log/ANA

use_mountpoints = yes

Format block devices using the XFS file system

Mount block devices

Conclusion


[storage]

ha_provider = hdb_ha.fcClient

partition_*_*__prType = 5

partition_*_data__mountOptions = -o relatime,inode64

partition_*_log__mountOptions = -o relatime,inode64,nobarrier

partition_1_data__wwid = 360000970000298700460533030303438

partition_1_log__wwid = 360000970000298700460533030303238





Conclusion

Using EMC enterprise storage, SAP HANA, and TDI, EMC developed the concept of running SAP HANA in a VNX storage system. This concept provides many benefits, including reducing hardware and operational costs, lowering risks, and increasing hardware vendor flexibility, for SAP as well as nonSAP applications.

Customers can now integrate HANA into their existing data center infrastructure. An essential characteristic of this solution is the use of shared enterprise storage. This allows customers to rely on already available multisite concepts to benefit from established automation and operations processes.

Customers can now transition easily from the appliance model to the new TDI architecture with SAP HANA while relying on EMC solutions and services to minimize risk.

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.

• The EMC VNX series unified storage systems documentation set contains the hardware platform guides for the VNX5400, VNX5600, VNX5800, VNX7600, and VNX8000 storage arrays

• EMC Cloud Enabled Infrastructure for SAP: Business White Paper

EMC Cloud Enabled Infrastructure for SAP: Foundation Bundle

The following documentation on the SAP website provides additional relevant information about SAP HANA:

• SAP HANA Server Installation and Update Guide

• SAP HANA TDI - Storage Requirements

• Certified SAP HANA Hardware Directory - EMC Enterprise Storage

Web resources

• SAP HANA Platform

• SAP HANA One

• SAP HANA Enterprise Cloud

• Overview - SAP HANA tailored data center integration

The following documents require an SAP username and password.

Best practice documents/white papers

• Sizing Approaches for SAP HANA—Lessons Learned

• Enterprise Storage Architecture—Planning Guide

• Elements of a Software Change Management Strategy

• Technical Deployment Options for SAP Systems with SAP HANA

Notes: Deployment options

• Note 1681092—Multiple SAP HANA databases on one appliance

• Note 1661202—Support for multiple applications on SAP HANA

• Note 1666670—BW on SAP HANA; Landscape deployment planning

• Note 1944799 - SAP HANA Guidelines for SLES Operating System

• Note 2009879 - SAP HANA Guidelines for RedHat Enterprise Linux (RHEL)

• Note 19669700 - SQL statement collection for SAP HANA

EMC documentation

SAP documentation

http://www.emc.com/

https://support.emc.com/

https://community.emc.com/docs/DOC-26684

https://community.emc.com/docs/DOC-25623?et=watches.email.document

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

http://scn.sap.com/docs/DOC-62595

http://scn.sap.com/docs/DOC-62595

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html#categories=EMC%20Corporation

http://help.sap.com/hana_appliance

http://help.sap.com/hana_one

http://www.saphana.com/entcloud

https://scn.sap.com/docs/DOC-63140

https://scn.sap.com/docs/DOC-63140

https://service.sap.com/~sapidb/011000358700000050632013E

https://service.sap.com/~sapidb/011000358700000050612013E

http://service.sap.com/~sapidb/011000358700000669992013E/171_Elements_of_a_SW_CMS.pdf

http://service.sap.com/~sapidb/011000358700000884902013E/D70229650_173a_SAP_HA_Opt.pdf

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



https://websmp130.sap-ag.de/sap/support/notes/1944799

http://service.sap.com/sap/support/notes/2009879


References


• Note 1999930 – FAQ: SAP HANA I/O Analysis

Notes: Virtualization

• Note 1788665—SAP HANA running on VMware vSphere VMs



Storage Configuration Best Practices for SAP HANA TDI on ...

Documents

Transcript of Storage Configuration Best Practices for SAP HANA TDI on ...