SAP HANA with Lenovo System x and NetApp …through SAP HANA technology; for example, using SAP BW...

White Paper

SAP HANA with Lenovo System x and NetApp FAS/AFF Systems with NFS Architecture Overview

SAP Competence Center, NetApp

June 2016 | WP-7232

Abstract

This document outlines the architecture of SAP HANA solution built with tailored data center

integration (TDI)–certified Lenovo servers and NetApp® Data ONTAP® storage systems. This

solution excels in flexibility, scalability, and differentiating data protection capabilities in

business-critical environments. It outlines practical architectures to implement production,

disaster recovery, development, and testing for a Business Warehouse (BW) and Suite-on-

HANA (SoH) scenario.

Tags: SAP HANA, TDI, Lenovo, System X, NetApp Data ONTAP, Data Protection, Snapshot

based storage Backup, Snapshot Backup (Tags font color changed to white prior to export to

PDF.

2 SAP HANA with Lenovo System x and NetApp FAS/AFF Systems with NFS © 2016 NetApp, Inc. All rights reserved.

TABLE OF CONTENTS

1 Executive Summary.............................................................................................................................. 4

2 Introduction ........................................................................................................................................... 4

3 Architecture ........................................................................................................................................... 5

3.1 SAP HANA Backup .........................................................................................................................................6

4 SAP HANA Disaster Recovery ............................................................................................................ 7

4.1 Asynchronous Storage Replication .................................................................................................................8

5 System Replication and SAP HANA High Availability ...................................................................... 8

6 Solution Sizing ...................................................................................................................................... 9

6.1 Solid-State Drives ...........................................................................................................................................9

7 Scenario-Specific Sizing .................................................................................................................... 10

7.1 SAP HANA BW Architecture ......................................................................................................................... 10

7.2 SAP SoH Architecture ................................................................................................................................... 11

8 Summary ............................................................................................................................................. 12

Appendix .................................................................................................................................................... 12

Lenovo Compute Building Blocks for SAP HANA TDI .......................................................................................... 12

HWCCT ................................................................................................................................................................ 13

Resources .................................................................................................................................................. 14

Lenovo Documentation ......................................................................................................................................... 14

NetApp Documentation ........................................................................................................................................ 14

SAP Documentation ............................................................................................................................................. 14

LIST OF TABLES

Table 1) Lenovo server configurations for SAP HANA in BW/data mart scenarios. .......................................................5

Table 2) Lenovo server configurations for SAP HANA in SoH scenarios. ......................................................................5

Table 3) Capacity sizing examples with 900GB and 10 drives per SAP HANA node. ....................................................9

Table 4) Capacity sizing examples with 800GB SSDs and four disks per SAP HANA node. ....................................... 10

Table 5) Lenovo servers and components certified for SAP HANA TDI. ...................................................................... 13

LIST OF FIGURES

Figure 1) Example configuration with four SAP HANA Lenovo x3850 X6 nodes. ...........................................................6

Figure 2) Database log backup to secondary storage using NFS mount. ......................................................................7

Figure 3) Asynchronous storage replication. ..................................................................................................................8


Figure 4) 3+1 scale-out configuration with three worker nodes. ................................................................................... 11

Figure 5) Business continuity solution using SAP HANA system replication. ............................................................... 12


1 Executive Summary

In today's fast-paced world, you need to know what's going on with your business, your marketplace, and

your customers so you can respond quickly. Many enterprises are looking to obtain real business insights

through SAP HANA technology; for example, using SAP BW on HANA, SAP Suite on HANA (SoH), and

S/4HANA. However, the move to SAP HANA can be complex, so choosing your business and technology

partners wisely is an important first step in this journey.

Lenovo and NetApp are working closely with SAP to provide you with seamless, secure, context-aware

experiences for your SAP environment. For SAP HANA, Lenovo and NetApp offer customers a complete

set of fully integrated solutions and services with Lenovo System x servers and NetApp enterprise

storage.

In this document, we focus on deploying SAP HANA using the tailored data center integration (TDI)

approach. With this approach, you can connect SAP HANA–certified servers to SAP HANA–certified

enterprise storage systems. This allows homogeneous integration into existing infrastructure,

management, and operational models and a faster overall HANA adoption. With this approach, you can

leverage existing data center processes and reuse existing IT infrastructure.

The SAP HANA configuration outlined in this white paper is based on Lenovo System x servers and

NetApp FAS and AFF enterprise storage systems. This solution white paper combines the technologies

of NetApp and Lenovo to create a best-in-class, economical, feature-rich, and simple-to-operate SAP

HANA TDI implementation.

2 Introduction

This document describes an SAP HANA architecture using SAP HANA TDI-certified Lenovo server

components and NetApp FAS and AFF storage controllers. It is applicable to all SAP HANA–based

solutions, such as SAP BW on HANA, SoH, and S/4HANA.

The components used in these scenarios include:

Lenovo System x Servers:

x3850 X6

x3950 X6

Both are SAP HANA–certified server models listed in the SAP HANA HW directory. For the storage

connectivity in this TDI deployment scenario, Emulex One Connect 10 Gigabit Ethernet (10GbE) dual-port

network adapters are used. Table 1 and Table 2 provide an overview of the usage scenarios of the

servers.

The following NetApp FAS and AFF storage controllers are compatible with the solution described in this

document. The storage controllers are not limited to any particular usage scenario.

FAS6210, FAS6220, FAS6240, FAS6250, FAS6280, FAS6290

FAS8020, FAS8040, FAS8060, FAS8080 EX

AFF8040, AFF8060, AFF8080 EX

Servers and storage system are interconnected using Ethernet and NFS protocol:

Any combination of Lenovo System x servers and NetApp storage listed in the SAP HANA HW directory is allowed.

Both physical and virtual deployment types are allowed.

Any certified or validated SAP software on top of SAP HANA can be used.


Table 1) Lenovo server configurations for SAP HANA in BW/data mart scenarios.

Lenovo Solution for SAP HANA: Hardware Configurations for BW/Data Mart

Scale-Up Sizes

128 GB

256 GB

384 GB

512 GB

768 GB

1TB 1.5 TB

2TB 2.5 TB

3TB 4TB 6TB 12 TB

2 CPUs X X X X X Non prod

Non prod

Non prod

Non prod

Non prod

--- --- ---

4 CPUs X X X X X X X X Non prod

Non prod

Non prod

Non prod

---

8 CPUs X X X X X X X X X X X Non prod

Non prod

Scale-Out Sizes

2 CPUs --- --- ---- ---- ---- --- --- --- --- --- --- --- ---

4 CPUs X X X X X X X X Non prod

Non prod

Non prod

Non prod

Non prod

8 CPUs X X X X X X X X X X X Non prod

Non prod

Table 2) Lenovo server configurations for SAP HANA in SoH scenarios.

Lenovo Solution for SAP HANA: Hardware Configurations for SoH and S/4HANA

Scale-Up Sizes

128GB

256GB

384GB

512 GB

768GB

1TB 1.5 TB

2TB 2.5 TB

3TB 4TB 6TB 12TB

2 CPUs X X X X X X X Non prod

Non prod

Non prod

--- --- ---

4 CPUs X X X X X X X X X X Non prod

Non prod

---

8 CPUs X X X X X X X X X X X X Non prod

3 Architecture

SAP HANA nodes are connected to storage controllers by using a redundant 10GbE infrastructure. Data

communication between SAP HANA nodes and storage controllers is based on the NFS protocol. A

redundant switching infrastructure is required to provide fault-tolerant SAP HANA node-to-storage

connectivity in case of a switch or network interface card (NIC) failure.

Different Lenovo server models and different models of the NetApp FAS and AFF system product family

can be used at the storage layer. The maximum number of SAP HANA nodes attached to the storage is

defined by the SAP HANA performance requirements. The number of required disk shelves is determined

by the capacity and performance requirements of the SAP HANA systems. The capacity requirements

depend on the number of SAP HANA nodes and the RAM size of each node. The storage partitions of the

SAP HANA nodes are distributed to the storage controllers.


Note: The storage and SAP HANA node-to-node communication is separated. Only the storage communication is shown in Figure 1.

Figure 1 shows an example configuration with four SAP HANA Lenovo nodes attached to a two-node

storage cluster.

Figure 1) Example configuration with four SAP HANA Lenovo x3850 X6 nodes.

The architecture can be scaled in two dimensions:

Scale up the storage system and attach additional SAP HANA nodes and storage capacity to the storage, as long as the storage controllers provide enough performance to meet the KPIs.

Scale out the storage system and add more storage controllers and capacity for the additional SAP HANA nodes.

Scaling up and scaling out the environment can be performed without any interruption to the running SAP

HANA environment, making use of the nondisruptive operations (NDO) built into NetApp clustered Data

ONTAP.

3.1 SAP HANA Backup

NetApp Data ONTAP is the storage operating system for NetApp FAS and AFF storage controllers. It

provides a built-in mechanism to support backup of SAP HANA databases, out of the box. This so-called

storage-based Snapshot® backup is a fully supported and integrated backup. It excels by performing

SAP HANA backups extremely quickly. This gives customers the freedom to perform data protection

according to their business needs and achieve full control over their SAP HANA RTO again. It is a major

component in most of our customers’ backup strategies and can be extended with the following backup

strategies:

File-based backup (also for integrity check purposes)

Backint-based backup

Storage-based Snapshot backups are implemented using the NetApp Snap Creator® plug-in for SAP

HANA, which allows consistent storage-based Snapshot backups by using the interfaces provided by the

SAP HANA database. Snap Creator registers the Snapshot backups in the SAP HANA backup catalog so

that they are visible within the SAP HANA studio and can be selected for restore and recovery operations.

By using NetApp SnapVault® software, the Snapshot copies that were created on the primary storage can


be replicated to the secondary backup storage controlled by Snap Creator to create a second copy of the

backups. Different backup retention policies can be defined for backups on the primary storage and

backups on the secondary storage.

The database logs can be backed up directly to the secondary storage by using an NFS mount, as shown

in Figure 2.

Figure 2) Database log backup to secondary storage using NFS mount.

Storage-based Snapshot backups provide significant advantages compared to backup to disk and backup

to a backup server (backint). The advantages include:

Fast backup (less than a minute)

Fast restore on storage layer (less than a minute)

No performance impact on the SAP HANA database node or storage during backup

Space-efficient and bandwidth-efficient replication to secondary storage based on incremental block changes

Thus, storage-based Snapshot backups implement fine-grained incremental backup. For detailed

information about the SAP HANA backup and recovery solution using Snap Creator, refer to TR-4313:

SAP HANA Backup and Recovery Using Snap Creator.

4 SAP HANA Disaster Recovery

There are several ways to achieve disaster recovery with SAP HANA. The most economic ways are

asynchronous storage replication and asynchronous/synchronous SAP HANA system replication.

Technically, there is an option to perform synchronous storage replication using NetApp MetroCluster™.

We mention it for completeness and refer the reader to the appendix.

http://www.netapp.com/us/media/tr-4313.pdf



4.1 Asynchronous Storage Replication

Asynchronous replication of consistent SAP HANA database images on the storage level is supported

using Snap Creator. A consistent Snapshot image of the database at the primary site is asynchronously

replicated to the disaster recovery site by using NetApp SnapMirror® technology. The servers at the

disaster recovery site can be used for development and testing during normal operation, as shown in

Figure 3. In contrast to a synchronous replication using SAP HANA system replication, there’s no

overhead on the compute resources of the DR site, because sending and receiving data are handled at

the storage layer.

Figure 3) Asynchronous storage replication.

Space-efficient, instantaneous NetApp FlexClone® copies can be used at the disaster recovery site to run

disaster failover tests without interrupting the replication process. FlexClone copies can also be used to

create an SAP system copy and refresh the test systems with current production data.

For detailed information about the SAP HANA disaster recovery solution using Snap Creator, refer to TR-

4279: SAP HANA Disaster Recovery with Asynchronous Storage Replication Using Snap Creator and

SnapMirror.

5 System Replication and SAP HANA High Availability

SUSE Linux supports high availability with SAP HANA. SAP HANA is deployed with system replication,

and its software handles a reconfiguration in case of system failure. System replication keeps the data in

sync, but the two systems have their own dedicated persistency and their own backups.

In the event of an incident at the production system, the failover system continues and writes ahead its

data protection history. For the time being, an SAP HANA system in the role of a system replication target

can perform data protection based on Snapshot in a crash-consistent manner until its role changes to be

the primary. After becoming the primary, database-consistent data protection based on Snapshot can be

performed to enable an overall protection history.





6 Solution Sizing

The following performance and capacity considerations should be observed to obtain an accurate storage

sizing.

Table 3 shows that when using SAP HANA nodes with 2TB or more RAM, disk sizing is based on the

capacity requirements with 900GB drives. All sizings that are based on performance requirements include

capacity headroom for Snapshot copies on the storage layer.

Table 3) Capacity sizing examples with 900GB and 10 drives per SAP HANA node.

SAP HANA Node RAM Size

Minimum Number of Data Disks per SAP HANA Node Performance Requirement

Capacity Requirement:

~2.5 x RAM; Min Number of Data Disks per SAP HANA Node (See SAP HANA Storage Requirements)

Sizing Based On

Space Available for Snapshot Copies

128GB 10 data disks 320GB

1 data disk

Performance requirements

Approximately 6TB headroom. Sufficient space for Snapshot copies.


2 data disks


Approximately 5.9TB headroom. Sufficient space for Snapshot copies.


3 data disks



1TB 10 data disks 2.5TB

6 data disks



2TB 10 data disks 5TB

12 data disks

Capacity requirements

Approximately 1.5TB headroom.


24 data disks


Add capacity for Snapshot copies.


36 data disks



6.1 Solid-State Drives

Table 4 shows examples of the performance and capacity requirements of a single SAP HANA node with

different RAM sizes, using 800GB SSDs. SSDs of a different size, such as 1.6TB, can also be used as

long as the minimum number of required drives or performance is considered.

Note: The capacity sizing of the overall SAP landscape with multiple SAP HANA systems must be determined by using capacity sizing tools such as the NetApp SPM and not just by multiplying the number of data drives in the table.


Table 4) Capacity sizing examples with 800GB SSDs and four disks per SAP HANA node.

SAP HANA Node RAM Size

Minimum Number of Data Disks per SAP HANA Node Performance Requirement

Capacity Requirement: ~2.5 x RAM; Minimum Number of Data Disks per SAP HANA Node (See SAP HANA Storage Requirements)

Sizing Based On

Space Available for Snapshot Copies

128GB Up to 4 HANA nodes per SSD shelf; approx. 4 SSDs per SAP HANA node

640GB

2 data drives



256GB 1280GB

3 data drives


Approximately 1.7TB headroom. Sufficient space for Snapshot copies.

512GB 2.5TB

5 data drives



1TB 5TB

10 data drives



2TB 10TB

20 data drives



4TB 15TB

30 data drives



6TB



Table 4 shows that by using SAP HANA nodes with 1TB or more RAM, disk sizing is based on capacity

requirements. In that case, 1.6/3.8TB SSDs can also be used, but at least four data disks per SAP HANA

system must be available to fulfill the performance requirements. All sizings that are based on

performance requirements include capacity headroom for Snapshot copies on the storage layer.

7 Scenario-Specific Sizing

In this section, we would like to bring the two perspectives of server and storage together and give insight

into two typical types of SAP HANA projects.

We’ll consider an SAP HANA BW project with development and test chain and an SAP SoH or S/4HANA

with development and test chain with system replication to implement high availability.

7.1 SAP HANA BW Architecture

The following example architecture is for a 3TB BW on Hana system based on SAP HANA scale-out (3

workers + 1 standby). There is one production BW system (PRD) with a development instance (DEV) on

the left and an asynchronous mirrored system (PRD failover) on the right.

Asynchronous mirroring is performed with NetApp Snap Creator and asynchronous storage mirroring of

consistent database images, with a quality assurance (QAS) and test (TST) system on the right side as

well. Those systems are refreshed from the PRD-failover system using NetApp cloning. The development

and test systems can be provided as either virtual or physical.


Either way, the data for those systems is provided by an NFS-attached clone. Virtual machines attach

their data/log by mounting directly from the storage controller.

Figure 4 illustrates a 3+1 scale-out configuration with three worker nodes. We assume 1TB RAM size at

each node, resulting in an overall 3TB scale-out SAP HANA BW system.

Figure 4) 3+1 scale-out configuration with three worker nodes.

On both sides, all qualified FAS/AFF controllers could be used. In the following, we use FAS8060 storage

controllers with 900GB SAS drives. Within this architecture we implement:

Snapshot copy–based storage backup for system PRD

Asynchronous storage replication from PRD to PRD failover

Development on the left

Quality assurance and test on the right

The capacity and performance on the left side are delivered using a storage system using ~52 drives in

three shelves. This configuration gives headroom for sufficient local backup copies (7) on the left side for

rapid recovery.

The capacity and performance on the right side are delivered using ~64 drives in three shelves. Because

there are more active copies for QAS and TST system, a few more drives are necessary.

7.2 SAP SoH Architecture

As a second architecture example, we outline a 2TB S/4HANA or, respectively, 2TB SoH system. This

system is replicated synchronously using SAP HANA system replication from the production system

(PRD) to the failover system (PRD-failover). On the left side, the development system (DEV) is located

with 0.5TB RAM. The PRD-failover system (2TB), quality assurance (QAS, 2TB), and test system (TST,

2TB) are on the right side. Those systems are refreshed using crash-consistent clones of the PRD-

failover system. In this setup we make use of AFF8060 storage controllers with SSD drives with 3.8TB

raw capacity.

Figure 5 illustrates a business continuity solution for SoH deployment.


Figure 5) Business continuity solution using SAP HANA system replication.

On the left side, one shelf with ~16 drives is necessary. On the right side, one shelf containing 17 drives

is needed. Within this architecture, we implement:

Snapshot copy–based storage backup for system PRD

Development on the left

Quality assurance and test on the right

There is sufficient headroom available to provide Snapshot copies on both sites.

8 Summary

This document highlights Lenovo enterprise-class servers and NetApp enterprise storage components for

TDI-based SAP HANA deployments. This approach allows customers to operate SAP HANA with their

operational best practice as an existing sourcing strategy.

We outlined the scalability on the server as well as the storage side to address growing demands. It is a

simple architecture for virtual and physical SAP HANA deployments covering important development,

availability, and data protection needs, right out of the box. With many SAP software stacks turning to

HANA, the ability to scale up and scale with the correct number of SAP HANA systems is critical.

Appendix

Lenovo Compute Building Blocks for SAP HANA TDI

Table 5 shows which System x servers are supported in an SAP HANA TDI environment.


Table 5) Lenovo servers and components certified for SAP HANA TDI.

Machine Type CPU Type Memory FC HBAs Ethernet Cards

System x3850 X6 (type 6241)

Intel Ivy Bridge EX E7-8880v2, 2S and 4S

Maximum 6TBF

1 Click here. Click here.

System x3950 X6 (type 6241)

Intel Ivy Bridge EX E7-8880v2, 4S and 8S

Maximum 12TBF

2 Click here. Click here.

System x3500 M5 (5464)

Intel Xeon E5-26xx v3, 2S

Maximum 1.5TB Click here. Click here.

System x3550 M5 (5463)



System x3650 M5 (5462)



HWCCT The SAP HANA HW Configuration Check Tool (HWCCT) allows you to check the interoperability of SAP HANA with your existing enterprise storage in production environments.

The HWCCT is a framework that provides tests and reports for new single-host and scale-out systems to determine whether the hardware you intend to use meets the minimum performance criteria required to run SAP HANA in production use. Click here for more details about the HWCCT.

1 6TB for single-node SoH implementations only. 8S 4TB is the maximum BW on HANA scale-out supported

configuration in TDI. For more information, check SCN. 2 12TB support only for nonproduction environments.

https://lenovopress.com/tips1250-system-x3850-x6-6241#sap-hana-workload-optimized-solution-models




https://lenovopress.com/tips1242-system-x3500-m5

https://lenovopress.com/tips1242-system-x3500-m5

https://lenovopress.com/tips1194-lenovo-system-x3550-m5




http://help.sap.com/saphelp_hanaplatform/helpdata/en/44/226b888ae64f40a6e7906eeaa0a44c/content.htm?frameset=/en/65/af0e2d971b430fb58b29323e2e1592/frameset.htm&current_toc=/en/00/0ca1e3486640ef8b884cdf1a050fbb/plain.htm&node_id=136

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html#categories=Lenovo


Resources

Lenovo Documentation

System x Solution for SAP HANA

HFlex System X6 Solution for SAP HANA

System x Solutions for SAP Environments

In-Memory Computing on Lenovo eX5 and X6

Lenovo System x Solution for SAP HANA and VMware vSphere on X6

NetApp Documentation

Best Practices and Recommendations for Scale-Up Deployments of SAP HANA on VMware vSphere

Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere

SAP HANA Tailored Data Center Integration Frequently Asked Questions

SAP HANA Tailored Data Center Integration Overview Presentation

TR-4279: SAP HANA Disaster Recovery with Asynchronous Storage Replication Using Snap Creator and SnapMirror

TR-4313: SAP HANA Backup and Recovery Using Snap Creator

TR-4338: SAP HANA on VMware vSphere and NetApp FAS Systems Reference Architecture

TR-4439: Optimizing SAP Lifecycle Management with NetApp Solutions for SAP HANA

SAP Documentation

SAP HANA Server Installation Guide

Best Practice Document – Technical Deployment Options for SAP Systems with SAP HANA

White Paper - SAP HANA System Landscape Guide

SAP HANA Appliance

SAP HANA One

SAP HANA Enterprise Cloud

SAP HANA Tailored Data Center Integration (Of enterprise storage systems with SAP HANA)

SAP HANA High Availability Paper

SAP SCN Page for TDI-certified Servers and Storage

SAP SCN SAP HANA Storage Requirements

http://www-03.ibm.com/systems/x/solutions/sap/hana/

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=SP&infotype=PM&appname=LNVE_LZ_WZ_USEN&htmlfid=LZS12346usen&attachment=LZS12346USEN.PDF#loaded

http://www-03.ibm.com/systems/x/solutions/sap/

http://www.redbooks.ibm.com/abstracts/sg248086.html?Open

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=SP&infotype=PM&appname=STGE_XS_XG_USEN&htmlfid=XSS03127USEN#loaded

http://www.vmware.com/files/pdf/SAP_HANA_on_vmware_vSphere_best_practices_guide.pdf

http://www.vmware.com/files/pdf/sap-hana-scale-out-deployments-on-vsphere.pdf

http://www.vmware.com/files/pdf/sap-hana-scale-out-deployments-on-vsphere.pdf

http://www.saphana.com/docs/DOC-3634







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

https://proddps.hana.ondemand.com/dps/d/preview/6932132d32b54f58a961a755e043e21e/1.0/en-US/index.html#url=dfeb8da5f24749d089917673fe4ed629.html

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

http://help.sap.com/hana_appliance

http://help.sap.com/hana_one

http://hana.sap.com/platform/sap-hana-enterprise-cloud.html

http://hana.sap.com/abouthana/hana-technology/data-center.html


http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html#categories=Lenovo

https://hcp.sap.com/content/dam/website/saphana/en_us/Technology%20Documents/Storage%20Whitepaper%202%204.pdf


Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact

product and feature versions described in this document are supported for your specific environment.

The NetApp IMT defines the product components and versions that can be used to construct

configurations that are supported by NetApp. Specific results depend on each customer's installation in

accordance with published specifications.

Trademark Information

NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud

ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel,

Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare,

FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp

Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity, SecureShare, Simplicity,

Simulate ONTAP, SnapCenter, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock,

SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator,

SnapVault, SolidFire, StorageGRID, Tech OnTap, Unbound Cloud, WAFL, and other names are

trademarks or registered trademarks of NetApp Inc., in the United States and/or other countries. All other

brands or products are trademarks or registered trademarks of their respective holders and should be

treated as such. A current list of NetApp trademarks is available on the web at

http://www.netapp.com/us/legal/netapptmlist.aspx. WP-7232-0516

Copyright Information

Copyright © 1994–2016 NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document

covered by copyright may be reproduced in any form or by any means—graphic, electronic, or

mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—

without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY

DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.

NetApp assumes no responsibility or liability arising from the use of products described herein, except as

expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license

under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents, or

pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to

restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software

clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

http://mysupport.netapp.com/matrix

http://www.netapp.com/us/legal/netapptmlist.aspx

SAP HANA with Lenovo System x and NetApp …through SAP HANA technology; for example, using SAP BW...

Documents

Transcript of SAP HANA with Lenovo System x and NetApp …through SAP HANA technology; for example, using SAP BW...