Guide To Integrate IBM System Storage With SAP HANA TDI V2.9

IBM System Storage Architecture
and Configuration Guide

for
SAP HANA
Tailored Datacenter Integration
location of this document:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102347
[email protected]
Version 2.9 October 2016
IBM System Storage Reference Architecture for SAP HANA TDI
Table of Contents
1
Preface .................................................................................................................... 3
IBM storage architecture for SAP HANA TDI ....................................................... 3
The central theme.................................................................................................. 4
Requirements .......................................................................................................... 4
Installation of SUSE SLES or Red Hat ..................................................................... 5
Setup of shared access for the /hana/shared/ directory ............................... 5
IBM System Storage sizing & configuration ........................................................ 6
Setup of multipath ............................................................................................... 10
SAN zoning and volume mapping .................................................................... 11
10
Setup of file systems for DATA and LOG ........................................................... 11
11
VMware VVols ...................................................................................................... 12
12
Setup of LINUX IO scheduler (elevator) ............................................................ 12
13
Setup of /hana/shared/global.ini...................................................................... 13
14
hdbparam fileio parameter ............................................................................... 13
15
SAP HANA TDI High Availability setup with IBM System Storage ................... 13
16
SAP HANA TDI Disaster Recovery setup with IBM System Storage ................ 14
17
SAP HANA TDI backup with IBM Spectrum Protect ........................................ 14
18
Change History ..................................................................................................... 14
19
Resources .............................................................................................................. 15
20
Trademarks ............................................................................................................ 16
21
Disclaimers............................................................................................................. 17
Page - 2
Copyright IBM Corporation 2016
1 Preface
This paper is intended as an architecture and configuration guide to setup the
IBM System Storage for the SAP HANA tailored datacenter integration (SAP
HANA TDI) within a SAN environment.
This document has been written for IT technical specialists and architects, with
advanced skill levels on SUSE Linux Enterprise Server or RedHat LINUX and IBM
System Storage, with a focus on architecting and setting up an IBM System Storage environment for SAP HANA TDI. The SAP HANA TDI allows the SAP customer to
use external storage to attach to the SAP HANA server.
This document provides the necessary information to select, verify and connect
IBM System Storage to the SAP HANA server through a SAN (fiber channel) attached storage network. The recommendations in this guideline apply to both
single node and scale out configurations, as well as Intel or IBM POWER based
SAP HANA systems.
For a list of all storage systems certified for SAP HANA production please visit:
http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html
2 IBM storage architecture for SAP HANA TDI

The IBM System Storage needs to be connected through a SAN network with the
SAP HANA server. IBM recommends but not requires the use of the IBM Spectrum Virtualize (SAN Volume Controller, SVC) as virtualization layer, enabling to
centralize the management of the storage systems, as well as to provide easily
high availability and disaster recovery functionality, as well as IBM FlashCopy
backup and tiered storage pooling. For smaller HANA TDI deployments you can
also use the IBM Storwize, which is based on the same functions like the SVC, and
inherits its advantages described above.
IBM Storage Systems are certified for SAP HANA TDI production:
IBM Storwize family, model V7000, V5030, V5020, V5010, V5000, V3700,
and IBM Spectrum Virtualize (SVC)
IBM FlashSystem family, model 820, 840, 900, V840, V9000
A9000, A9000R
IBM XIV Gen 3 Storage System
IBM DS8800, DS8870, DS8880
IBM Spectrum Scale ESS GS2,4 & GL2,4,6
Page - 3

The setup of IBM Spectrum Scale (IBM GPFS) storage system ESS (Elastic Storage Server) is documented in:
For non-prod SAP HANA systems any storage system can be used.
3 The central theme

Below the generic workflow describes how to setup SAP HANA TDI with IBM storage:
I.
II.
III.
IV.
V.
VI.
VII.
VIII.
IX.
X.
XI.
Verify all server & storage components and firmware requirements given
by SAP are met
Install SLES or Red Hat operating system on all SAP HANA nodes
If required: setup NFS services for the SAP HANA shared directory
Setup SAN storage systems
Create SAN zone for SAP HANA environment
On the storage systems map the storage volumes (LUNs)
to all target SAP HANA nodes
Setup of multipath
On each LINUX host create the file systems for SAP HANA data, log,
shared
Setup of /hana/shared/global.ini
Install and configure the SAP HANA software
Optional: HA, DR, and Backup considerations
4 Requirements
Before starting to deploy a SAP HANA TDI, ensure that the following key items have
are in place:
A SAN environment is required to attach IBM System Storage through fiber

channel with the SAP HANA TDI nodes.
SAP requires a storage validation for SAP HANA TDI according to their KPI
(key Performance Indicators) please contact SAP for further details.
The SAP HANA nodes must be sized and configured according to SAPs
specification (Bill of Material for SAP HANA node), in addition each SAP
HANA TDI system needs to have min 2 FC ports, recommended are 4 FC
ports.
Page - 4

Naming: The term node is use for a single HANA instance: if for instance 4 HANA
instances are deployed on a single IBM POWER server, or 4 HANA instances are
deployed into one single LPAR, then this reflects 4 nodes.
5 Installation of SUSE SLES or Red Hat

Install the Linux operating System accordingly to the SAP PAM for the chosen SAP
HANA version.
6 Setup of shared access for the /hana/shared/ directory

SAP HANA scale-out and HANA HA node fail-over require that the directory
/hana/shared/ must be accessible from all nodes (else this directory can be
setup as local file system from type xfs).
The shared access can be achieved most easily through NFS. If such setup does
not already exist, one of the following options can be used to implement it:
IBM Storwize V7000 Unified

High Availability NFS service with DRBD and IBM Tivoli System Automation for
Multiplatform (SA MP) with SUSE Linux Enterprise High Availability Extension
11.
Highly Available NFS service with DRBD and Pacemaker with SUSE Linux Enterprise High Availability Extension 11.
Setup these systems according to the appropriate implementation guides, and

make the NFS file system available on all HANA nodes, including the spare nodes.
Basic setup of NFS Server, add this line to /etc/exports
/hana/shared node1(fsid=0,crossmnt,rw,no_root_squash, sync,no_subtree_check)
node2(fsid=0,crossmnt,rw, ...) node3( ...
Basic setup of the HANA nodes (NFS clients), add this line to /etc/fstab
nfs-server:/hana/shared
Page - 5
/hana/shared
nfs
rw,soft,intr,rsize=8192,wsize=8192 0 0
7 IBM System Storage sizing & configuration

This section covers the evaluated storage options.
7.1
Recommended IBM System Storage combinations
To achieve the required storage performance according to SAP KPIs (key performance indicators) for SAP HANA TDI, one of the following configurations listed
should be chosen nevertheless all IBM systems listed can be used as stand-alone
system as well, used for DATA and LOG.
IBM Spectrum Virtualized is referred as SVC.
Storage virtualization
SAP HANA data
SAP HANA log
SVC
IBM XIV Gen 3
IBM FlashSystem
SVC
IBM Storwize
IBM Storwize/ IBM FlashSystem
SVC
IBM FlashSystem
IBM FlashSystem
SVC
IBM DS8000
IBM Storwize / IBM FlashSystem
Because IBM SVC, and for smaller configurations IBM Storwize, provisions volumes
(LUNs) as a single volume type and single storage system, it will ease the administration of storage pool tiers with Flash, SSD, and HDD types; and optional tasks
like setup of storage high availability, FlashCopy base backup, storage based mirroring, or storage maintenance. If the IBM storage system will be direct attached
the SAP HANA TDI nodes, then the following table specifies the recommended
disk types.
IBM Storwize
IBM DS8000
SAP HANA data

HDD / SSD
HDD / SSD
SAP HANA log

SSD
SSD
IBM XIV
Module
Module
IBM FlashSystem
Flash Card
Flash Card
7.1 Storage sizing through SAPmagic tool

The IBM storage systems should be configured (sized) through the IBM tool
HANAmagic and SAPmagic; this tool is available to IBM (technical) Sales and IBM
Business Partner on IBM TechDocs, w3 or ibm.com/partnerworld
Note: The performance sizing described in this chapter is only required for productive HANA nodes (HANA databases for the SAP production systems) and not for
the non-production HANA Nodes (e.g. QA, Test, Dev, Sandbox Systems). For the
non-production systems only a capacity sizing is required.
Page - 6
7.2
Required IBM System Storage sizing
This chapter provides some general sizing guidelines.

All components of the SAN infrastructure must be configured to use a minimum
8GB link speed. All listed storage configurations apply to active SAP HANA TDI
nodes only; no additional storage configuration is required for any stand-by system. If SVC stretched cluster needs to be configured, all listed storage configuration must be doubled.
Maximal number of HANA production systems support per IBM System Storage:
IBM System Storage
# HANA
Storwize V3700
Storwize V5000 (00/10/20/30)

Storwize V7000 (Models 524 / 624)
10/8/10/12
10 / 14
FlashSystem V9000
40
FlashSystem A9000R
40
FlashSystem 820 / 840 / V840 / 900
12
DS8870
16
DS8880 (4/6/8)
16 / 32 / 40
XIV Gen 3
15
SVC 2145, one / four node pair
10 / 40
The minimum number of HDD for DATA is 24: three RAID 5 as 7+1, spares not included. The HDD or SDD disk capacity can be chosen arbitrary to match HANA
capacity requirements.
IBM Storwize Use distributed RAID 5, this provides higher performance.
HANA DATA, one of:

o 16 HDD, plus: For every 1 system 8 HDD, 10 krpm
o For every 4 node 8 SSD
HANA LOG: For every 8 node 8 SSD
For a small number of nodes, and small RAM size the LOG RAID can be built as RAID 10,
with 2, 4, or 6 SSD depending on actual sizing.
Page - 7

IBM FlashSystem A9000R
One building block supports up to 10 HANA nodes

One building block is one Flash enclose and two Grid controllers
The maximum number of SAP HANA nodes is 40 by using 6 building blocks
IBM FlashSystem V9000
One building block supports up to 10 HANA systems

One building block is one IBM FlashSystem V9000 Control Enclosure (AC2) and one to four
FlashSystem 900 (AE2) with 12 Flash Cards
The maximum number of SAP HANA nodes is 40 by using 4 building blocks
IBM FlashSystem (820, 840, 900, V840)
Supports up to 10 HANA production nodes

One Flash Module supports one HANA node, min 6 Flash modules required
IBM XIV Storage System
Supports up to 15 HANA production nodes

One Module supports one HANA node, min 9 modules required
IBM DS8000 family up to 16 HANA systems
7.3
HANA DATA one of:

o 16 HDD plus: For every 2 HANA nodes 16 HDD, 10 krpm, RAID 5
o For every 8 HANA nodes 16 SSD RAID 5
HANA LOG one of:
o For every 12 HANA nodes 16 HDD, 10 krpm, RAID 5
o For every 4 HANA nodes 16 SSD, RAID 5
Definitions of storage pools and volumes
The SAP HANA Data and Log have different I/O characteristics reflected by the
different storage systems configurations as described earlier. This has to be applied by pooling the appropriate storage systems accordingly.
For all storage systems:
Create 4 volumes for HANA DATA and 1 volume for HANA LOG,
for each node
These volumes would also server as MDISKs if SVC will be used
Page - 8

IBM SVC storage pool and VDISK definitions
7.4
Create separate pools for DATA and LOG

Create 4 VDISKs for HANA DATA and 1 VDISKs for HANA LOG, for each node
Switch off VDISK caching for pools with FlashSystem MDISK
Layout of storage pools and storage volumes
The following diagrams show the relationship between Linux file system, LINUX LV,
VG, and PV, and the Virtual Volumes (VD, VDISK) and Managed Disks (MD, MDISK,
RAIDs/Arrays) of a Storage Systems.
We recommend to create just one DATA and just one LOG pool, if feasible, and
just one non-Prod (HDD / shared) pool, if needed. This ensures best resource utilization (max striping) if more than one HANA system needs to be deployed.
Page - 9
7.5
Competing storage utilization
Every IBM storage system can be shared between SAP HANA (production) and
any other SAP or non-SAP (production) workload.
To do so proper sizing of the entire storage infrastructure is required, including configuration of RAID controller, number of HDD, SSD, storage of Flash Modules, number and type of HBA and FC ports/links.
IBM and IBM Business Partner are pleased to provide support for this sizing task,
including the usage of the IBM tools HANAmagic.
7.6
The use of IBM storage compression (RtC)
The IBM storage systems provide the option to compression data on VDISK / Volume level.
Because the data of the HANA database are just integers, these data cannot
be compressed further. SAP calls this Data Compression in the Column Store.
We strongly urge you to not use IBM storage compression (RtC) for SAP HANA, else
this would lead to performance degradation.
8 Setup of multipath
Setup multipath according SLES or Red Hat documentation, in addition:
/etc/multipath.conf:
defaults {
polling_interval
failback
no_path_retry
user_friendly_names
30
immediate
5
no
devices {
device {
vendor
product
failback
no_path_retry
rr_min_io
dev_loss_tmo
path_checker
path_grouping_policy
path_selector
prio
rr_weight
}
}
Page - 10
"IBM"
"2145"
immediate
5
10
120
tur
group_by_prio
"round-robin 0"
const
uniform
9 SAN zoning and volume mapping

Apply standard, best practices zoning within the SAN.
If HANA High Availability node-fail over or HANA scale-out is use, then, and only
then, it is required to map all Data and Log volumes to all SAP Hana Nodes.
10 Setup of file systems for DATA and LOG

Create the DATA, LOG, and SHARED file system needed by SAP HANA according
to the SAP HANA Storage Requirements documentation from SAP.
Use the xfs file system type with a 4KB block size for the DATA and LOG file
systems
To use LVM 2 use this schema:
vgcreate lvreate mkfs.xfs
Use useful names for volume groups and logical volumes do not use
the hyphen (minus) sign - as part of the name, because the LINUX mapper uses this sign as separator between VG and LV name.
Create Volume Groups and Logical Volumes for DATA and LOG, for each
HANA mount point (as listed in global.ini) create one Volume Group with
exactly one Logical Volume.
It has turned out that these settings are most beneficial for SAP HANA workload
in combination with SVC:
1. Use 4 PV for Volume Group DATA
2. Create a volume group with an extent size of 1MB and an alignment size
of 1MB
vgcreate vgcreate -s 1M --dataalignment 1M VG_ANA_DATA_1 /dev/mapper/WWID_1 /dev/mapper/WWID_2 ...
3. Create a logical volume with a stripe size of 256KB

lvcreate -i 4 -I 256K -l 100%VG -n LV_ANA_DATA_1 VG_ANA_DATA_1
4. Create the file system

mkfs.xfs -b size=4096 -s size=4096 /dev/mapper/VG_ANA_DATA_1LV_ANA_DATA_1
5. Mount the file system

mount /dev/mapper/VG_ANA_DATA_1-LV_ANA_DATA_1 /hana/data/ANA/mnt00001
Page - 11

1. Use 1 PV for Volume Group LOG
2. Create a volume group with an alignment size of 1MB
vgcreate vgcreate -s 1M --dataalignment 1M VG_ANA_LOG_1 /dev/mapper/WWID_1
3. Create a logical volume (without striping)

lvcreate -l 100%VG -n LV_ANA_LOG_1 VG_ANA_LOG_1

mkfs.xfs -b size=4096 -s size=4096 /dev/mapper/VG_ANA_LOG_1-LV_LOG_1

mount /dev/mapper/VG_ANA_LOG_1-LV_ANA_LOG_1 /hana/log/ANA/mnt00001
1. If scale up, use 1 PV for Volume Group SHARED

2. Create a volume group:
vgcreate vgcreate -s 1M --dataalignment 1M VG_SHARED /dev/mapper/WWID_1
3. Create a logical volume (without striping)

lvcreate -l 100%VG -n LV_SHARED VG_SHARED

mkfs.xfs -b /dev/mapper/VG_SHARED-LV_SHARED

mount /dev/mapper/VG_SHARED-LV_SHARED /hana/shared
If HANA scale-out or HA node fail-over is used, it is not necessary to add the file
system to /etc/fstab, mounting will be done by SAP HANA.
11 VMware VVols
The same setup applies like for LINUX native installation as described in chapter
10; the only deviation is that VMware (ESX server) controls the SAN multipath,
not the LINUX OS. The volumes are typically accessible under the path:
/dev/sd... instead of /dev/mapper/...
Please have a look in the IBM Redbook how to setup VMware VVols with IBM storage: http://www.redbooks.ibm.com/abstracts/sg248328.html?Open
12 Setup of LINUX IO scheduler (elevator)

The default scheduler cfq delivers low IO performance for multiple (parallel)
streaming read processes. It seems that deadline delivers slightly better performance than noop, special during multiple (parallel) IO operations.
We recommend to use the deadline scheduler.
Page - 12

More information on IO tuning can be found in this whitepaper:
LINUX IO performance tuning for IBM System Storage
13 Setup of /hana/shared/global.ini
Enter the Logical Volume names as shown in directory /dev/mapper into
/hana/shared/global.ini :
[communication]
listeninterface = .global
[persistence]
basepath_datavolumes = /hana/data/ANA
basepath_logvolumes = /hana/log/ANA
[storage]
ha_provider
partition_*_*__prtype
partition_1_data__lvmname
partition_1_log__lvmname
partition_2_data__lvmname
partition_2_log__lvmname
=
=
=
=
=
=
hdb_ha.fcClientLVM
5
VG_ANA_DATA_1-LV_ANA_DATA_1
VG_ANA_LOG_1-LV_ANA_LOG_1
VG_ANA_DATA_2-LV_ANA_DATA_2
VG_ANA_LOG_2-LV_ANA_LOG_2
The [storage] section is only needed, if you want to use the node fail-over functionality provided by SAP HANA software and for HANA scale-out. If you use the
system replicating capability leave this section empty.
14 hdbparam fileio parameter

The following parameters were set for the SAP HWCCT tool hwval/fsperf, and
needs to be used for all IBM storage:
async_write_submit_active : on
async_write_submit_blocks : all
async_read_submit
: on
Plase read the SAP note: 1930979 - Alert: Sync/Async read ratio how to set these
parameters via the hdbparm tool.
15 SAP HANA TDI High Availability setup with IBM System Storage
The SAP HANA system gains high availability through an N+1 concept one or
more server act as standby SAP HANA node with dedicated storage for each
active node. If one active SAP HANA node fails, the SAP HANA cluster software
Page - 13

initiates a failover to the standby node, and the standby node will mount the data
and log from the failed node.
For more details, please read the SAP document SAP HANA High Availability.
To improve storage availability, the ISICC recommends to setup the storage environment as a SVC stretched cluster with symmetric VDISK mirroring, as shown in
Figure 1.
Figure 1: SAP HANA TDI HA setup with SVC stretched cluster for data redundancy
16 SAP HANA TDI Disaster Recovery setup with IBM System Storage
The disaster recovery capabilities of SAP HANA are documented on
www.saphana.com:
SAP HANA Scale-Out, High Availability & Disaster Tolerance

SAP HANA High Availability
If IBM Metro Mirror (synchronous) is used for storage replication for SAP HANA TDI,
all DATA and all LOG volumes of all nodes from one HANA system must be included in one storage Consistency Group.
That implies (when using native attached storage) that both Data and Log
must come from the same storage unit.
17 SAP HANA TDI backup with IBM Spectrum Protect

IBM Spectrum Protect, also known as Tivoli Storage Manager for Enterprise Resource Planning (TSM for ERP) includes the package Data Protection for SAP
HANA.
Please see current product documentation how to install, configure, and run this
integrated solution.
18 Change History
V1
V1.2
V1.3
V1.4
V1.5
V1.6
V1.7
Page - 14
Initial version
Update of chapter 7.6 to clarify files system setup
Included new Storwize V5000
Specified NFS section to be used only for /hana/shared/
Minor updates add some clarifications
Add setup of multipath and global.ini
Rework of document

V1.8
V2.1
V2.2
V2.3
V2.5
V2.6
V2.7
V2.8
V2.9
Added LINUX LVM2 & list of certified IBM storage systems

Added IBM DS8000 system as certified for SAP HANA TDI
Added IBM FlashSystem 900 & V9000
Changes sizing rules, added recommendation for multipath and VG/LV settings.
Changed /etc/multipath setting
Added fileio parameter for hdbparam
Added A9000R & DS8880; info on LINUX LVM settings for HANA LOG
Added chapter on Storage RtC, changes in storage sizing
Added paragraph about VMware VVols
19 Resources
For any product or documentation provided by SAP please contact SAP.
For any product or documentation provided by SUSE please contact SUSE.
For any product or documentation provided by IBM regarding SAP send an email
to [email protected].
IBM documentations:
This document is ID WP102347 on www.ibm.com
SAP HANA on IBM Power Systems and IBM System Storage Guides
IBM Storwize product manuals:
http://www-01.ibm.com/support/docview.wss?uid=ssg1S7003318
Installation, configuration and usage of Tivoli Storage Manager for Enterprise Resource Planning V6.4 Data Protection for SAP HANA
http://www-01.ibm.com/support/docview.wss?uid=swg21608240
IBM Tivoli SA for MP Installation and Configuration Guide

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.samp.doc_3.2.1/HALICG21.pdf
SAP documentation:
Overview - SAP HANA tailored data center integration
http://www.saphana.com/docs/DOC-3633
FAQ - SAP HANA tailored data center integration

Page - 15

Introduction to High Availability for SAP HANA
Access to sapjam and documentation will be provided by SAP the listed links
only work after login: login first, then access the links.
SAP HANA Fiber Channel Storage Connector Admin Guide
SAP HANA Storage Requirements (Storage Whiltepaper.pdf)
https://jam4.sapjam.com/wiki/show/60549
SAP HANA reference architecture

SAP HANA Bill of Material

Novell / SUSE documentation:

List of all SLES 11 documentations
https://www.suse.com/documentation/sles11/
Highly Available NFS Storage with DRBD and Pacemaker with SUSE Linux Enterprise High Availability Extension 11
https://www.suse.com/documentation/sle_ha/singlehtml/book_sleha_techguides/book_sleha_techguides.html
20 Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or
both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was
published. Such trademarks may also be registered or common law trademarks
in other countries. A current list of IBM trademarks is available on the Web at
http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
AIX, BladeCenter, DB2, Global Business Services, Global Technology Services, GPFS, IBM SmartCloud, IBM, Intelligent Cluster, Passport Advantage, POWER, PureFlex, RackSwitch, Redbooks, Redpaper,
Redbooks (logo) , System Storage, System x, System z, Tivoli, z/OS.
Page - 16

The following terms are trademarks of other companies:
SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany
or an SAP affiliate company.
Intel Xeon, Intel, Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
SUSE is a registered trademark of SUSE Germany and Novell USA, other countries,
or both. SLES is a trademark of SUSE Germany and Novell USA, other countries, or
both.
Other company, product, or service names may be trademarks or service marks
of others.
21 Disclaimers
This information was developed for products and services offered in Germany.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be
used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT
Page - 17

WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may
not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites.
The materials at those websites are not part of the materials for this IBM product
and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on developmentlevel systems and there is no guarantee that these measurements will be the same
on generally available systems. Furthermore, some measurements may have
been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
Page - 18

Guide To Integrate IBM System Storage With SAP HANA TDI V2.9

Uploaded by

Copyright:

Available Formats

Guide To Integrate IBM System Storage With SAP HANA TDI V2.9

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guide To Integrate IBM System Storage With SAP HANA TDI V2.9

Uploaded by

Copyright:

Available Formats

What are the main requirements for setting up IBM storage for SAP HANA TDI?

What are the main requirements for setting up IBM storage for SAP HANA TDI?

What are the steps to configure multipath?

What are the steps to configure multipath?

IBM System Storage Architecture

and Configuration Guide

Version 2.9 October 2016

IBM System Storage Reference Architecture for SAP HANA TDI

IBM storage architecture for SAP HANA TDI ....................................................... 3

The central theme.................................................................................................. 4

Installation of SUSE SLES or Red Hat ..................................................................... 5

Setup of shared access for the /hana/shared/ directory ............................... 5

IBM System Storage sizing & configuration ........................................................ 6

Setup of multipath ............................................................................................... 10

SAN zoning and volume mapping .................................................................... 11

Setup of file systems for DATA and LOG ........................................................... 11

VMware VVols ...................................................................................................... 12

Setup of LINUX IO scheduler (elevator) ............................................................ 12

hdbparam fileio parameter ............................................................................... 13

SAP HANA TDI backup with IBM Spectrum Protect ........................................ 14

Change History ..................................................................................................... 14

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

2 IBM storage architecture for SAP HANA TDI

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

3 The central theme

A SAN environment is required to attach IBM System Storage through fiber

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

5 Installation of SUSE SLES or Red Hat

6 Setup of shared access for the /hana/shared/ directory

IBM Storwize V7000 Unified

Setup these systems according to the appropriate implementation guides, and

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

7 IBM System Storage sizing & configuration

Recommended IBM System Storage combinations

SAP HANA data

SAP HANA log

IBM XIV Gen 3

IBM Storwize/ IBM FlashSystem

IBM Storwize / IBM FlashSystem

SAP HANA data

SAP HANA log

7.1 Storage sizing through SAPmagic tool

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

Required IBM System Storage sizing

This chapter provides some general sizing guidelines.

Storwize V5000 (00/10/20/30)

FlashSystem 820 / 840 / V840 / 900

SVC 2145, one / four node pair

HANA DATA, one of:

Copyright IBM Corporation 2016

IBM System Storage Reference Architecture for SAP HANA TDI

One building block supports up to 10 HANA nodes

IBM FlashSystem V9000

One building block supports up to 10 HANA systems