h12342 storage config best practices sap hana tdi on emc symmetrix vmax wp

8/11/2019 H12342 Storage Config Best Practices Sap Hana Tdi on Emc Symmetrix Vmax Wp

http://slidepdf.com/reader/full/h12342-storage-config-best-practices-sap-hana-tdi-on-emc-symmetrix-vmax-wp 1/28

White Paper

EMC Solutions

Abstract

This white paper provides information on a new concept that revokeslimitations of the current SAP HANA Appliance Model. Using Tailored DataCenter Integration (TDI) on EMC Symmetrix® VMAX®, customers can move SAPHANA into the private cloud and integrate into an existing, well-establisheddata center infrastructure, providing multiple benefits.

January 2014

STORAGE CONFIGURATIONRECOMMENDATIONS FOR SAP HANATAILORED DATA CENTER INTEGRATION (TDI)ON EMC SYMMETRIX VMAX STORAGESYSTEMS

Integrating SAP HANA into an EMC Symmetrix VMAX privatecloud



Storage Configuration Recommendations for SAP HANA Tailored Data

Center Integration (TDI) on EMC Symmetrix VMAX Storage Systems;integrating SAP HANA into an EMC Symmetrix VMAX private cloud

2

Disclaimer

This document outlines a general product direction and should not be relied onin making a purchase decision. This document is not subject to your licenseagreement or any other agreement with EMC or SAP. EMC or SAP has no

obligation to pursue any course of business outlined in this document or todevelop or release any functionality mentioned in this document. Thisdocument and the strategy and possible future developments of EMC or SAPare subject to change and may be changed by EMC or SAP at any time for anyreason without notice. This document is provided without a warranty of anykind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement. EMC and SAP assumes no responsibility for errors or omissions inthis document, except if such damages were caused by EMC or SAPintentionally or grossly negligent.

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 © 2014 SAP. All Rights Reserved.

SAP and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germanyand in other countries.

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

Copyright © 2014 EMC Corporation. All Rights Reserved.

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

The information in this publication is provided as is. EMC Corporation makes norepresentations or warranties of any kind with respect to the information in thispublication, and specifically disclaims implied warranties of merchantability orfitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this

publication requires an applicable software license.

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

All trademarks used herein are the property of their respective owners.

Part Number H12342.1

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






3Storage Configuration Recommendations for SAP HANA Tailored Data


Table of contents

Executive summary ............................................................................................................................... 5

Business case .................................................................................................................................. 5

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

Purpose ........................................................................................................................................... 6

Scope .............................................................................................................................................. 6

Audience ......................................................................................................................................... 6

VMAX storage configuration overview .................................................................................................. 7

Scalability of a VMAX engine ............................................................................................................ 7

Dedicated disks ............................................................................................................................... 7

Dedicated Fibre Adaptor (FA) processors .......................................................................................... 8

SAP HANA OS images on VMAX ........................................................................................................ 8

SAP HANA shared file system on VMAX ............................................................................................ 9

Configuring VMAX storage with EMC Unisphere for VMAX .................................................................. 10

Creating disk groups ...................................................................................................................... 10

Creating disk groups for logs ..................................................................................................... 10

Creating disk groups for data..................................................................................................... 10

Creating initiator groups ................................................................................................................ 11

Creating thin pools ......................................................................................................................... 12

Creating meta volumes .................................................................................................................. 14

Creating a meta volumes for logs ............................................................................................... 14

Creating meta volumes for data ................................................................................................. 16

Binding meta volumes to thin pools .......................................................................................... 17

Creating storage groups ................................................................................................................. 18

Creating port groups ...................................................................................................................... 20

Creating masking views ................................................................................................................. 21

Accessing VMAX storage from the SAP HANA nodes ........................................................................... 23

Enable native Linux multipathing (DM-MPIO) ................................................................................. 23

Using XFS file system to format a block device ............................................................................... 24

Mounting block devices ................................................................................................................. 25

SAP HANA global.ini file ............................................................................................................ 25

Conclusion ......................................................................................................................................... 26

References.......................................................................................................................................... 27

EMC documentation ....................................................................................................................... 27

SAP documentation ....................................................................................................................... 27





4

Web resources .......................................................................................................................... 27

Notes: Deployment options ....................................................................................................... 27

Notes: Virtualization .................................................................................................................. 27

Best practice documents / white papers.................................................................................... 27





Executive summary

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

Data centers that need to run traditional SAP applications, including non-SAPapplications or SAP HANA, must offer the following fundamental characteristics:

• Service catalogs, productized service-level agreements, and multitenantresource pools

• Chargeback based on fully automated cost measurement, cost analysis, andcost reporting

• Efficiently managed availability, capacity, performance, and health in the SAPlandscape

• High availability and application mobility

•

Disaster recovery• Data protection

• Automation and operations

• Enhanced security

By default, an SAP HANA appliance includes integrated storage, compute, andnetwork components. SAP has defined key performance indicators for storagesubsystems, such as I/O throughput and latency, ensuring that the overallinfrastructure forms a HANA-ready environment.

You can also deploy SAP HANA appliances using a Tailored Data Center Integration

(TDI) approach, which EMC engineering recommends. With this approach, you canconnect certified servers to existing enterprise storage systems. This reduces time-to-value, risk, and costs for an overall HANA adoption.

EMC engineering has performed many performance tests with SAP HANA on a VMAXenterprise storage system. Based on these tests, this white paper describes a VMAXstorage configuration that meets SAP performance requirements and ensures thehighest availability for database persistence on disk.

This white paper also includes step-by-step instructions to configure SAP HANAstorage devices on a VMAX array.

Business case





6

Introduction

Until now, customers who used the SAP HANA Appliance Model had the followinglimitations:

• Limited flexibility for servers and storage

• Inability to use existing data center infrastructure and operationalprocesses

• Fixed sizes for storage capacities

This white paper describes a solution that uses EMC enterprise storage, SAP HANA,and Tailored Data Center Integration (TDI), and runs SAP HANA in a private cloud. Thissolution reduces hardware and operational costs, lowers risks, and increaseshardware vendor flexibility for both SAP and non-SAP applications.

This white paper serves the following purposes:

•

Introduces the key solution technologies• Describes the key business benefits of using EMC Symmetrix VMAX storage

systems with SAP HANA

• Describes configuring VMAX storage with EMC Unisphere for VMAX

• Describes accessing VMAX storage from the SAP HANA nodes

This white paper is intended for system integrators, systems or storageadministrators, customers, partners and members of the EMC professional serviceswho need to configure a VMAX storage array to be used in a TDI environment for SAPHANA.

Purpose

Scope

Audience





VMAX storage configuration overview

The specific SAP HANA I/O workload requires special considerations for theconfiguration of persistence for data and log volumes on a shared EMC VMAX storagearray.

The EMC VMAX system delivers the high performance requirements for the persistent

storage of a SAP HANA database, without impacting other applications concurrentlyusing the same array.

The I/O workload on SAP HANA has two major components:

• Random I/Os on the data volume

• Sequential I/Os on the log volume

SAP HANA uses different block sizes for log volumes and data volumes. I/O for logvolumes uses 4 K, 16K, and 1M block sizes. I/O for data volumes uses 4 K, 16 K, 64K, 1 M, 16 M, and 64 M block sizes.

SAP HANA TDI uses VMAX engines as building blocks. The VMAX engine can scale upto 6 TB in-memory capacity for a SAP HANA database. If, for example, a SAP HANAnode has 512 GB RAM capacity, a single VMAX engine can scale to support up to 12HANA nodes.

Providing storage for a larger SAP HANA database requires additional engines. VMAXsystems can support the following number of engines, each with a minimum cache of128 GB:

• VMAX 10 K: 1-4 engines



Note: EMC recommends that an EMC engineer evaluate your workload distribution to ensurethat you have the correct reserved capacity for expected SAP HANA workloads.

To separate the SAP HANA workload from the other applications on the VMAX, youmust use dedicated disks in dedicated disk groups for SAP HANA. For every 2 TB in-memory database capacity, 48 of the 600 GB 15 k 3.5” disks are required, split intotwo disk groups:

• 16 disks in a dedicated disk group for log volumes

• 32 disks in a dedicated disk group for data volumes

Scalability of aMAX engine

Dedicated disks





8

Table 1 shows the in-memory database capacity for various numbers of 600 GB 15k3.5” disks.

Note: The recommendations in Table 1 are based on increments of 48 disks for each 2 TBincrease in database size. The recommended number of disks is not proportional for smallerdatabase sizes. (For example, a 1 TB database may require more than 24 disks.

Table 1. Database capacity for disks and disk groups

In-memory database size Total number of disks Disk groups

2 TB 48 1x 16 disks, 1x 32 disks



EMC engineers must create disk groups for VMAX systems and cannot create diskgroups using Unisphere for VMAX or command lines.

Note: Add the required hot spare disks on top of the total disk count for HANA.

Table 2 shows the number of FA processors and the allocation of FA ports for a VMAX10K single engine configuration, with three different examples for increases in-memory database size. Databases must have a minimum of four FA processors.

Table 2. Database capacity for FA disks and FA ports

In-memory database sizeNumber of FA

processors

FA ports in a VMAX 10 K single engine

example

2 TB 4 FA-1E:0, FA-1F:0, FA2E-0, FA2F-0

4 TB 6 FA-1E:0, FA-1F:0, FA2E-0, FA2F-0FA-1G:0, FA-2G:0

6 TB 8 FA-1E:0, FA-1F:0, FA2E-0, FA2F-0FA-1G:0, FA-2G:0,FA1H-0, FA2H-0

Port 1 of each FA cannot be used for HANA or other applications. Ensure that the portsare correctly zoned to the SAP HANA nodes.

You can boot HANA nodes from SANs and install the operating systems on blockdevices on VMAX systems.

You can also use existing free space on a VMAX storage array to create the devices forthe operating systems images.

Note: Refer to the SAP HANA Server Installation Guide and requirements for specific servesfor more information.

Dedicated Fibre Adaptor (FA)processors

SAP HANA OSimages on VMAX





SAP HANA database binaries are installed on a shared file system, but a file-basedstorage system is not required. Guided by the specific customer infrastructure andrequirements, you can select from these choices:

• You can use VMAX block storage to create a shared file system, in thesame way as /usr/sap/mnt is created as an NFS or similar shared mount

point. Because SAP HANA runs only on SUSE Linux, to create such a sharedmount point on the VMAX requires the use of a cluster file system such asan Oracle Cluster File System 2 (OCFS2) on top of it. SUSE provides OCFS2capabilities with the high availability package, and a SUSE license isrequired. The high availability package is also part of the SUSE LinuxEnterprise Server (SLES) for SAP Applications distribution from SAP that isused by most of the HANA appliance vendors.

• You can instead use existing NAS systems, such as EMC VNX, to provide anNFS share for this purpose.

SAP HANA sharedfile system on

MAX





1

Configuring VMAX storage with EMC Unisphere for VMAX

Before a storage administrator can configure the volumes to support data persistencefor SAP HANA on a VMAX, an EMC engineer must configure the disk groups on thearray.

VMAX disk groups are used to dedicate a range of disks within the array for specialpurposes. To separate the sequential workload of the HANA logs from the randomworkload of data persistence for HANA, dedicated disk groups for data and log mustbe created.

Creating disk groups for logs

Figure 1 shows how disk groups are created for a disk group with a log capacity of 16xFIB-600GB-15K disks.

Creating disk groups for logsFigure 1.

Choose a meaningful name for the disk groups, such as the following:

● HANA1_Log for the log persistence of the first 2 TB in-memory database capacity

● HANA2_Log for the second 2 TB capacity (4 TB total)

● HANA3_Log for the remaining 2 TB (up to 6 TB in-memory capacity)

Creating disk groups for data

Figure 2 shows how disk groups are created for 32x FIB-600 GB-15 K disks.

Creating disk groups for dataFigure 2.

Creating diskgroups





You can view the disk groups in the EMC Unisphere for VMAX GUI, as shown in Figure3:

Disk groups in the Unisphere GUIFigure 3.

Initiators are represented by the worldwide names (WWNs) of the host bus adapters(HBAs) of the HANA nodes. A HANA node can have multiple HBAs. The initiator group

combines the HBAs of a HANA node into a single group.

Follow these steps to create an initiator group:

1. In Unisphere, navigate toHosts

>Initiator Groups

, and then clickCreate

.

2. Select the initiators of the corresponding HANA node and create one initiatorgroup per HANA node, as shown in Figure 4.

Create initiator groupsFigure 4.

Repeat this step for all the HANA nodes, as shown in Figure 5.

Creating initiatorgroups





1

Initiator groupsFigure 5.

After you create initiator groups, create the thin pools to provide data persistence forHANA.

A thin pool in a VMAX system represents a number of data devices (TDATs) that are

created on the corresponding disk group. TDATs are not visible to a host. A thindevice (TDEV) must be created on a thin pool. The data written by the host to a TDEVis then striped across all TDATs in the thin pool.

The process for creating thin pools is described in the following steps, and shown inFigure 6:

1. In Unisphere, navigate to Storage > Thin Pools, and then click Create.

2. Specify the following details:

• Name: Specify a meaningful name

• Disk Technology: FC (Fibre Channel)

• Protection: 2-Way Mir

• Emulation: FBA

• Capacity:

Number of Volumes: 64 for a log thin pool or 128 for a data thin pool

Volume Capacity: 32 GB for log or 64 GB for data

Disk Group: Select an appropriate disk group

Creating thin pools





Create thin poolsFigure 6.

3. Click OK to complete the configuration and then click Run Now.4. Repeat these steps for all thin pools. Ensure that you create one thin pool for

each log and provide for data persistence of up to 2 TB in-memory databasecapacity.

Table 3 shows how many thin pools are required on a single VMAX engine based onthe database capacity.

Table 3. Database capacity for FA disks and FA ports

In-memory database size Thin pools Disk groups

2 TB HANA1_log 64 TDAT volumes each 32 GB

HANA1_data 128 TDAT volumes each 64 GB


HANA2_log 64 TDAT volumes each 32 GB







1

In-memory database size Thin pools Disk groups







The thin pools are displayed in the Unisphere GUI, as shown in Figure 7.

Thin poolsFigure 7.

After you create thin pools, the next step is to create the meta volumes to supportdata persistence for HANA.

Each HANA node requires a set of two volumes, a data and a log volume. The in-memory database is saved to the data volume in regular intervals (save points).Database updates are stored in the redo log on the log volume.

The size of the volume depends on the RAM capacity of the HANA node.

• Log: 1x RAM

• Data: 3x RAM

Note: Capacity of the data and log devices may change in the future based on SAPrequirements. Review the SAP HANA Server Installation Guide for details.

Creating a meta volumes for logs

Follow these steps to create meta volumes for logs:

1. In the Unisphere GUI, select Storage > Create Meta Volume.

2. Create striped volumes and selectUsing New Virtual Volumes

as the volumetype to use, as shown in Figure 8.

Creating meta volumes





Create a meta volume for a logFigure 8.

3. Type 64 GB for the the meta volume member (TDEV) capacity log volume, asshown in Figure 9.

Note: The member count depends on the required size of the meta volume. Forexample, if the HANA node has 512 GB RAM, the member count would be 8 (8 x 64GB = 512GB = 1x RAM). Adjust the member count based on the actual RAM size of aHANA node.

Create a meta volume memberFigure 9.

4. In the Create Meta Volume dialog box, click Next and Run Now to complete

the configuration change.5. Create one meta volume for each HANA worker node (the number of meta

volumes). HANA standby nodes do not have a persistence layer and do notneed data and log volumes.

6. After you create the log meta volumes for all HANA nodes, also create themeta volumes for the data devices, which must be created using a slightlydifferent configuration.





1

Creating meta volumes for data

The meta volume member capacity (TDEV size) of a data volume must be 96 GB, andthe meta member count again depends on the RAM size of the HANA node. Forexample, if the HANA node has 512 GB RAM, the member count is 16 (16 x 96 GB =1536 GB = 3x RAM).

Create meta volume for data Step 1Figure 10.

1. In the Create Meta Volume Summary dialog box, click Run Now as shown inFigure 11.

Create meta volume for data summary screenFigure 11.

2. Meta volumes are displayed in the EMC Unisphere for VMAX page as shown inFigure 12.





1

Ensure that you select the log meta volumes to be bound to a log thin pooland bind the data meta volumes to a data thin pool.

4. Clear thePreallocated Capacity for each Volume

checkbox, as shown in Figure14.

Bind volumes to a thin poolFigure 14.

5. Click OK and repeat this step for the data meta volumes.

After all meta volumes are bound to their corresponding thin pools, the next step is to

create storage groups.

A storage group contains all devices visible to a HANA node. Even though a HANAworker node has exclusive access to only one data and one log device at any time,the HANA HA (highly available) feature can move the persistence to a standby node incase of a failure on a node. If a node recovers from a failure, it will automaticallybecome a standby node. This means that all HANA nodes can potentially become astandby node and therefore requires access to all available persistence devices.

Follow these steps to create storage groups:

1. In the Unisphere GUI, navigate to Storage > Storage Groups, and then click

Create. Specify a meaningful storage group name and ensure that you selectEmpty Storage Group

as the Storage Group Type, as shown in Figure 15.

Creating storagegroups





Create a storage groupFigure 15.

2. ClickFinish

to create the storage group.

3. From the Storage Groups Overview page, select the storage group.

4. Click View Details and click the Volumes – empty link in the upper rightcorner, as shown in Figure 16.

Create storage group volumesFigure 16.





2

5. Click Add and select all log and data volumes for the HANA database, asshown in Figure 17.

Add volumes to a storage groupFigure 17.

6. ClickOK

to add the volumes to the storage group.

Note: You need only one storage group per HANA database. This storage groupincludes all data and log volumes.

After you create storage groups, the next step is to create port groups.

Three FA ports are used per VMAX engine for the SAP HANA nodes. Up to 12 HANAnodes (or 6 TB RAM capacity) can use one VMAX engine.

Follow these steps to create port groups:

1. In the Unisphere GUI, navigate toHost

>Port Groups

, and then clickCreate

.Select the ports which have been zoned to the HANA nodes, as shown inFigure 18.

Creating portgroups





Create port groupFigure 18.

Important: Use only port 0 of each front end processor.

2. If more than one VMAX engine is dedicated for the SAP HANA database,ensure that the port group contains the front end ports from all engines.

After you create port groups, the last step is to create masking views.

A VMAX masking view assigns the volumes to the front end ports and makes themaccessible to the initiators (HANA nodes).

1. In the Unisphere GUI, select Hosts > Masking Views, and then click Create, asshown in Figure 19.

Creating masking views





Accessing VMAX storage from the SAP HANA nodes

The SAP HANA database requires a Linux SUSE SLES-11 operating system on theHANA nodes. To access the VMAX block devices from the HANA nodes, ensure thatproper zoning was done in the SAN so that all HBAs (or vHBAs) of the HANA nodeshave access to all FA ports on the VMAX system.

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

Follow these steps to enable native Linux multipathing:

1. DM-MPIO requires a /etc/multipath.conf file with proper parameters set forthe VMAX system:

def aul t s {user_f r i endl y_names no}devi ces {

devi ce {vendor "EMC"product "SYMMETRI X"get ui d_cal l out

"/ l i b/ udev/ scsi _i d - - whi t el i st ed - - page=pr e- spc3- 83 - -devi ce=/ dev/ %n"

f eat ur es " 0"hardware_handl er "0"pat h_sel ect or "r ound- r obi n 0"path_groupi ng_pol i cy mul t i busr r _wei ght uni f or m

no_pat h_r et r y f ai lr r _mi n_i o 100

pat h_checker di r ect i opr i o constpr i o_ar gs ""

}}

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

$ ser vi ce mul t i pat hd r est art$ rescan- scsi - bus. sh

3. The HANA persistent device should be visible. Run the following command toverify that all devices are present and each device has three active paths:

$ mul t i pat h –l l360000970000298700460533030303238 dm- 10 EMC, SYMMETRI Xsi ze=512G f eatures=' 0' hwhandl er=' 0' wp=r w`- +- pol i cy=' r ound- r obi n 0' pr i o=1 st at us=act i ve

| - 2: 0: 5: 1 sdai 66: 32 act i ve r eady r unni ng| - 1: 0: 5: 1 sdby 68: 192 act i ve r eady r unni ng`- 2: 0: 4: 1 sdcg 69: 64 act i ve r eady r unni ng

360000970000298700460533030303338 dm- 11 EMC, SYMMETRI Xsi ze=512G f eatures=' 0' hwhandl er=' 0' wp=r w

Enable nativeLinux multipathing(DM-MPIO)





2

`- +- pol i cy=' r ound- r obi n 0' pr i o=1 st at us=act i ve| - 2: 0: 5: 3 sdak 66: 64 act i ve r eady r unni ng| - 1: 0: 5: 3 sdca 68: 224 act i ve r eady r unni ng`- 2: 0: 4: 3 sdci 69: 96 act i ve r eady r unni ng

360000970000298700460533030303438 dm- 12 EMC, SYMMETRI Xsi ze=1. 5T f eat ures=' 0' hwhandl er=' 0' wp=r w`- +- pol i cy=' r ound- r obi n 0' pr i o=1 st at us=act i ve

| - 2: 0: 5: 5 sdam 66: 96 act i ve r eady r unni ng

| - 1: 0: 5: 5 sdcc 69: 0 act i ve r eady r unni ng`- 2: 0: 4: 5 sdck 69: 128 act i ve r eady r unni ng


| - 2: 0: 5: 6 sdan 66: 112 act i ve r eady r unni ng| - 1: 0: 5: 6 sdcd 69: 16 act i ve r eady r unni ng`- 2: 0: 4: 6 sdcl 69: 144 act i ve r eady r unni ng


| - 2: 0: 5: 7 sdao 66: 128 act i ve r eady r unni ng| - 1: 0: 5: 7 sdce 69: 32 act i ve r eady r unni ng`- 2: 0: 4: 7 sdcm 69: 160 act i ve r eady r unni ng


| - 2: 0: 5: 8 sdap 66: 144 act i ve r eady r unni ng| - 1: 0: 5: 8 sdcf 69: 48 act i ve r eady r unni ng`- 2: 0: 4: 8 sdcn 69: 176 act i ve r eady r unni ng

360000970000298700460533030303330 dm- 9 EMC, SYMMETRI Xsi ze=512G f eatures=' 0' hwhandl er=' 0' wp=r w`- +- pol i cy=' r ound- r obi n 0' pr i o=1 st at us=act i ve

| - 2: 0: 5: 2 sdaj 66: 48 act i ve r eady r unni ng| - 1: 0: 5: 2 sdbz 68: 208 act i ve r eady r unni ng`- 2: 0: 4: 2 sdch 69: 80 act i ve r eady r unni ng

360000970000298700460533030303430 dm- 13 EMC, SYMMETRI X

si ze=512G f eatures=' 0' hwhandl er=' 0' wp=r w`- +- pol i cy=' r ound- r obi n 0' pr i o=1 st at us=act i ve

| - 2: 0: 5: 4 sdal 66: 80 act i ve r eady r unni ng| - 1: 0: 5: 4 sdcb 68: 240 act i ve r eady r unni ng`- 2: 0: 4: 4 sdcj 69: 112 act i ve r eady r unni ng

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

Although you can format block devices with a traditional Linux EXT3 file system, EMCstrongly recommends using XFS as the file system for the HANA block devices.

The SAP HANA storage connector API, which moves the devices from a failed workernode to a standby node, does not support partitioned devices or volume managerdevices. This may change in upcoming SAP HANA revisions.

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

$ mkf s. xf s / dev/ mapper / 3600009700002987004605330303238

Note: Run this command for all block devices.

Using XFS filesystem to format ablock device





In a SAP HANA scale-out environment with worker and standby nodes, the SAP HANAstorage connector API for Fibre Channel (FC Client) mounts and unmounts the devicesto the HANA nodes.

In addition to mounting the devices, the storage connector API also writes SCSI-3 PGRreservations to the devices using the Linux sg_persist command. This is called I/Ofencing and 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 HANAglobal.ini file. This section contains entries for the block devices with optional mountoptions.

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

• r el at i me

• nobar r i er ( appr oved f r omSAP) onl y f or Log devi ces

•

i node64 This is an example of a global.ini file:

[ per si st ence]basepath_dat avol umes=/ hana/ dat a/ ANAbasepat h_l ogvol umes=/ hana/ l og/ ANAuse_mount poi nt s = yes

[storage]ha_provi der = f cCl i entpar t i t i on_*_*__ pr Type = 5part i t i on_*_dat a__mount Opt i ons = - o r el at i me, i node66par t i t i on_*_ l og__mount Opt i ons = - o rel ati me, i node66, nobarr i er

par t i t i on_1_dat a__wwi d = 360000970000298700460533030303438par t i t i on_1_l og__wwi d = 360000970000298700460533030303238par t i t i on_2_dat a__wwi d = 360000970000298700460533030303538par t i t i on_2_l og__wwi d = 360000970000298700460533030303330par t i t i on_3_dat a__wwi d = 360000970000298700460533030303638par t i t i on_3_l og__wwi d = 360000970000298700460533030303338

Mounting blockdevices





2

Conclusion

Using EMC enterprise storage, SAP HANA, and Tailored Data Center Integration (TDI),EMC developed the new concept of running SAP HANA in a private cloud. This conceptprovides many benefits, including reducing hardware and operational costs, loweringrisks, and increasing hardware vendor flexibility, for both SAP and non-SAPapplications.

Customers can now integrate HANA into their existing data center infrastructure. Anessential characteristic of this solution is the use of shared enterprise storage. Thisallows customers the ability to rely on already-available multisite concepts to benefitfrom established automation and operations processes.

Customers can now easily transition to this new architecture, (SAP HANA in a privatecloud), relying on EMC services to minimize risk.





References

You can find further information on EMC Online Support:

• EMC Symmetrix VMAX Family Documentation Set—Contains the hardwareplatform product guide and TimeFinder product guide for the Symmetrix VMAX

10K, VMAX 20K, and VMAX 40K.• EMC Symmetrix System Viewer for Desktop and iPad—Illustrates VMAX 10K,

VMAX 2Ok, and VMAX 40K system hardware, incrementally scalable systemconfigurations, and available host connectivity offered for Symmetrixsystems.

• EMC SRDF Connectivity Guide

• EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide

• EMC Cloud Enabled Infrastructure for SAP – Business White Paper

• EMC Transforms IT On-Premise Private Cloud for SAP – Reference architecturefor EMC Cloud-Enabled Infrastructure for SAP on VMAX

• EMC Cloud Enabled Infrastructure for SAP – Foundation bundle white paper

The following SAP documentation contains SAP information.

• SAP HANA Server Installation Guide

• Best Practice Document – Technical Deployment Options for SAP Systemswith SAP HANA

Web resources

• SAP HANA Appliance

• SAP HANA One

• SAP HANA Enterprise Cloud

• SAP HANA tailored data center integration (integration of enterprise storagesystems with SAP HANA)

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

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

Notes: Virtualization

• Note 1788665 – SAP HANA running on VMware vSphere VMs

Best practice documents / white papers

• Sizing Approaches for SAP HANA – Lessons Learned

EMCdocumentation

SAPdocumentation

https://support.emc.com/


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


http://www.emc.com/collateral/technical-documentation/h11229-sap-virtual-stack-ra.pdf





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


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


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





http://help.sap.com/hana_appliance

http://help.sap.com/hana_one

http://www.saphana.com/entcloud

http://www.saphana.com/community/implement/hana-solutions/content?filterID=contentstatus%5Bpublished%5D~category%5Bsap-hana-tailored-data-center-integration%5D

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





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






http://www.saphana.com/community/implement/hana-solutions/content?filterID=contentstatus%5Bpublished%5D~category%5Bsap-hana-tailored-data-center-integration%5D

http://www.saphana.com/entcloud

http://help.sap.com/hana_one

http://help.sap.com/hana_appliance











• Enterprise Storage Architecture – Planning Guide

• Elements of a Software Change Management Strategy

• Technical Deployment Options for SAP Systems with SAP HANA


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



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


h12342 storage config best practices sap hana tdi on emc symmetrix vmax wp

Documents