Technical Report

SAP HANA on NetApp FAS Systems with NFS

Configuration Guide
Nils Bauer and Marco Schön, NetApp
June 2020 | TR-4290

Abstract
The NetApp® FAS product family has been certified for use with SAP HANA in tailored data
center integration (TDI) projects. This document describes best practices for a NAS (NFS)
storage setup using NetApp ONTAP® with the FAS product family.
TABLE OF CONTENTS

1 Introduction ........................................................................................................................................... 4
1.1 SAP HANA Tailored Data Center Integration ..................................................................................................5

2 Architecture........................................................................................................................................... 5
2.1 SAP HANA Backup .........................................................................................................................................7

2.2 SAP HANA Disaster Recovery........................................................................................................................8

3 Storage Sizing ..................................................................................................................................... 10

3.1 Performance Considerations.........................................................................................................................10

3.2 Mixed Workloads ..........................................................................................................................................11

3.3 Capacity Considerations ...............................................................................................................................12

3.4 Configuration of Performance Test Tool .......................................................................................................12

3.5 Storage Sizing Process Overview .................................................................................................................14

4 Infrastructure Setup and Configuration ........................................................................................... 14

4.1 Network Setup ..............................................................................................................................................14

4.2 Time Synchronization ...................................................................................................................................15

4.3 Storage Controller Setup ..............................................................................................................................15

4.4 Host Setup ....................................................................................................................................................25

4.5 SAP HANA Installation Preparations for NFSv4 ...........................................................................................29

4.6 I/O Stack Configuration for SAP HANA .........................................................................................................30

4.7 SAP HANA Data Volume Size ......................................................................................................................30

4.8 SAP HANA Software Installation...................................................................................................................30

4.9 Adding Additional Data Volume Partitions for SAP HANA Single-Host Systems ..........................................32

Where to Find Additional Information .................................................................................................... 35

Version History ......................................................................................................................................... 36

LIST OF TABLES
Table 1) Supported NFS versions. .................................................................................................................................4
Table 2) Number of SAP HANA hosts per disk shelf. ...................................................................................................11
Table 3) Performance test tool configuration file parameter values. .............................................................................12
Table 4) Maximum number of mounts per physical interface. ......................................................................................19
Table 5) Volume configuration for SAP HANA single-host systems. ............................................................................20
Table 6) Mount points for single-host systems. ............................................................................................................21
Table 7) Volume configuration for SAP HANA multiple-host systems. .........................................................................22
Table 8) Mount points for multiple-host systems. .........................................................................................................22
Table 9) Volume options...............................................................................................................................................23

2 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Table 10) NFSv3 options. .............................................................................................................................................23
Table 11) NFSv4 options. .............................................................................................................................................23
Table 12) Additional NFSv4 options for SAP HANA multiple host systems ..................................................................24
Table 13) Setting SAP HANA Failover Parameters ......................................................................................................25
Table 14) NFS versions to be used. .............................................................................................................................28
Table 15) Mount options. ..............................................................................................................................................28
Table 16) Volume configuration for SAP HANA single-host system with two data partitions........................................32
Table 17) Mount points for single-host system with two data partitions. .......................................................................32
Table 18) Volume configuration for SAP HANA multiple-host system with two data partitions.....................................33
Table 19) Mount points for multiple-host system with two data partitions. ....................................................................34

LIST OF FIGURES
Figure 1) SAP HANA TDI. ..............................................................................................................................................5
Figure 2) Example configuration with eight SAP HANA hosts. .......................................................................................6
Figure 3) Scaling by adding more storage capacity. .......................................................................................................6
Figure 4) Scaling with additional storage systems. .........................................................................................................7
Figure 5) Backup architecture. .......................................................................................................................................8
Figure 6) Disaster Recovery with Synchronous and Asynchronous SnapMirror Replication. .........................................9
Figure 7) Synchronous storage replication. ..................................................................................................................10
Figure 8) Storage sizing overview. ...............................................................................................................................14
Figure 9) Network configuration example. ....................................................................................................................15
Figure 10) Disk shelf connection with HDDs. ...............................................................................................................17
Figure 11) Disk shelf connection with SSDs. ................................................................................................................17
Figure 12) Aggregate layout with HDDs. ......................................................................................................................18
Figure 13) Aggregate layout with ADPv2......................................................................................................................19
Figure 14) Volume layout for SAP HANA multiple single-host systems. ......................................................................20
Figure 15) Volume layout for SAP HANA multiple-host systems. .................................................................................21
Figure 16) Add additional data volume partition. ..........................................................................................................35

3 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
1 Introduction
The NetApp FAS product family has been certified for use with SAP HANA in tailored data center
integration (TDI) projects. The certified enterprise storage system is characterized by the NetApp ONTAP
software.
This certification is currently only valid for the following models:
• FAS2620, FAS2650, FAS2720, FAS2750, FAS8200, FAS8300, FAS8700, and FAS9000
A complete list of NetApp certified storage solutions for SAP HANA can be found at the Certified and
Supported SAP HANA Hardware Directory.
This document describes the ONTAP configuration requirements for the NFS version 3 (NFSv3) protocol
or the NFS version 4 (NFSv4.0 and NFSv4.1) protocol. For the remainder of this document, NFSv4 refers
to both NFSv4.0 and NFSv4.1.
Note: The configuration described in this paper is necessary to achieve the required SAP HANA KPIs
and the best performance for SAP HANA. Changing any settings or using features not listed
herein might cause performance degradation or unexpected behavior and should only be
performed if advised by NetApp support.
The configuration guides for NetApp FAS systems using FCP and for AFF systems using NFS or FC can
be found at the following links:
• SAP HANA on NetApp FAS Systems with Fibre Channel Protocol
• SAP HANA on NetApp AFF Systems with NFS
• SAP HANA on NetApp AFF Systems with Fibre Channel Protocol
Table 1 shows the supported combinations for NFS versions, NFS locking, and the required isolation
implementations, depending on the SAP HANA database configuration. For SAP HANA single-host
systems, NFSv3 and NFSv4 are supported.
For SAP HANA multiple host systems, NetApp only supports NFSv4, while using NFSv4 locking as an
alternative to a server-specific STONITH (SAP HANA HA/DR provider) implementation.

Table 1) Supported NFS versions.

SAP HANA NFS Version NFS Locking SAP HANA HA/DR Provider
SAP HANA single host NFSv3 Off N/A

NFSv4 On N/A

SAP HANA multiple hosts NFSv4 On Not required

This document covers configuration recommendations for SAP HANA running on physical servers and on
virtual servers that use VMware vSphere.
For more information about using vSphere with SAP HANA, see the following links:
• 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
• TR-4338: SAP HANA on VMware vSphere and NetApp FAS Systems
Note: Always refer to the relevant SAP notes for operating system configuration guidelines and HANA-
specific Linux kernel dependencies. For more information, you see SAP note 2235581: SAP
HANA Supported Operating Systems.

4 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
1.1 SAP HANA Tailored Data Center Integration
NetApp FAS storage controllers are certified in the SAP HANA TDI program using both NFS (NAS) and
FC (SAN) protocols. They can be deployed in any of the current SAP HANA scenarios such as SAP
Business Suite on HANA, S/4HANA, BW/4HANA, or SAP Business Warehouse on HANA in either single-
host or multiple-host configurations. Any server that is certified for use with SAP HANA can be combined
with NetApp certified storage solutions. See Figure 1 for an architecture overview.

Figure 1) SAP HANA TDI.

For more information regarding the prerequisites and recommendations for production SAP HANA
systems, see the following SAP resources:
• SAP HANA Tailored Data Center Integration Frequently Asked Questions
• SAP HANA Storage Requirements

2 Architecture
SAP HANA hosts are connected to storage controllers by using a redundant 10GbE or faster network
infrastructure. Data communication between SAP HANA hosts and storage controllers is based on the
NFS protocol. A redundant switching infrastructure is recommended to provide fault-tolerant SAP HANA
host-to-storage connectivity in case of switch or network interface card (NIC) failure. The switches might
aggregate individual port performance with port channels in order to appear as a single logical entity at
the host level.
Different models of the FAS system product family can be mixed and matched at the storage layer to
allow for growth and differing performance and capacity needs. The maximum number of SAP HANA
hosts that can be attached to the storage system is defined by the SAP HANA performance requirements
and the model of NetApp controller used. The number of required disk shelves is only determined by the
capacity and performance requirements of the SAP HANA systems. Figure 2 shows an example
configuration with eight SAP HANA hosts attached to a storage high availability (HA) pair.

5 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 2) Example configuration with eight SAP HANA hosts.

The architecture can be scaled in two dimensions:

• By attaching additional SAP HANA hosts and/or storage capacity to the existing storage, if the
storage controllers provide enough performance to meet the current SAP key performance indicators
(KPIs)
• By adding more storage systems with additional storage capacity for the additional SAP HANA hosts
Figure 3 shows an example configuration in which more SAP HANA hosts are attached to the storage
controllers. In this example, more disk shelves are necessary to fulfill both the capacity and performance
requirements of 16 SAP HANA hosts. Depending on the total throughput requirements, additional 10GbE
(or faster) connections to the storage controllers must be added.

Figure 3) Scaling by adding more storage capacity.

Independent of the deployed FAS system, the SAP HANA landscape can also be scaled by adding any of
the certified storage controllers to meet the desired node density (Figure 4).

6 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 4) Scaling with additional storage systems.

2.1 SAP HANA Backup

The ONTAP software present on all NetApp storage controllers provides a built-in mechanism to back up
SAP HANA databases while in operation with no effect on performance. Storage-based NetApp
Snapshot™ backups are a fully supported and integrated backup solution available for SAP HANA single
containers and for SAP HANA Multitenant Database Container (MDC) systems with a single tenant or
multiple tenants.
Storage-based Snapshot backups are implemented by using the NetApp SnapCenter® plug-in for SAP
HANA. This allows users to create consistent storage-based Snapshot backups by using the interfaces
provided natively by SAP HANA databases. SnapCenter registers each of the Snapshot backups into the
SAP HANA backup catalog. Therefore, the backups taken by SnapCenter are visible within SAP HANA
Studio where they can be selected directly for restore and recovery operations.
NetApp SnapMirror® technology allows Snapshot copies that were created on one storage system to be
replicated to a secondary backup storage system that is controlled by SnapCenter. Different backup
retention policies can then be defined for each of the backup sets on the primary storage and for the
backup sets on the secondary storage systems. The SnapCenter Plug-in for SAP HANA automatically
manages the retention of Snapshot copy-based data backups and log backups, including the
housekeeping of the backup catalog. The SnapCenter Plug-in for SAP HANA also allows the execution of
a block integrity check of the SAP HANA database by executing a file-based backup.
The database logs can be backed up directly to the secondary storage by using an NFS mount, as shown
in Figure 5) Backup architecture.

7 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 5) Backup architecture.

Storage-based Snapshot backups provide significant advantages when compared to conventional file-
based backups. These advantages include, but are not limited to, the following:
• Faster backup (a few minutes)
• Reduced recovery time objective (RTO) due to a much faster restore time on the storage layer (a few
minutes) as well as more frequent backups
• No performance degradation of the SAP HANA database host, network, or storage during backup
and recovery operations
• Space-efficient and bandwidth-efficient replication to secondary storage based on block changes
For detailed information about the SAP HANA backup and recovery solution using SnapCenter, see TR-
4614: SAP HANA Backup and Recovery with SnapCenter.

2.2 SAP HANA Disaster Recovery

SAP HANA disaster recovery (DR) can be performed either on the database layer by using SAP HANA
system replication or on the storage layer by using storage replication technologies. The following section
provides an overview of disaster recovery solutions based on storage replication.
For detailed information about the SAP HANA disaster recovery solutions, see TR-4646: SAP HANA
Disaster Recovery with Asynchronous Storage Replication.

Storage Replication Based on SnapMirror

Figure 6 shows a three-site disaster recovery solution that uses synchronous SnapMirror replication to
the local DR datacenter and asynchronous SnapMirror to replicate data to the remote DR datacenter.
Data replication using synchronous SnapMirror provides an RPO of zero. The distance between the
primary and the local DR datacenter is limited to around 100km.

8 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Protection against failures of both the primary and the local DR site is performed by replicating the data to
a third remote DR datacenter using asynchronous SnapMirror. The RPO depends on the frequency of
replication updates and how fast they can be transferred. In theory, the distance is unlimited, but the limit
depends on the amount of data that must be transferred and the connection that is available between the
data centers. Typical RPO values are in the range of 30 minutes to multiple hours.
The RTO for both replication methods primarily depends on the time needed to start the HANA database
at the DR site and load the data into memory. With the assumption that the data is read with a throughput
of 1000MBps, loading 1TB of data would take approximately 18 minutes.
The servers at the DR sites can be used as dev/test systems during normal operation. In the case of a
disaster, the dev/test systems would need to be shut down and started as DR production servers.
Both replication methods allow to you execute DR workflow testing without influencing the RPO and RTO.
FlexClone volumes are created on the storage and are attached to the DR testing servers.

Figure 6) Disaster recovery with synchronous and asynchronous SnapMirror replication.

Synchronous replication offers StrictSync mode. If the write to secondary storage is not completed for any
reason, the application I/O fails, thereby ensuring that the primary and secondary storage systems are
identical. Application I/O to the primary resumes only after the SnapMirror relationship returns to InSync
status. If the primary storage fails, application I/O can be resumed on the secondary storage after failover,
with no loss of data. In StrictSync mode, the RPO is always zero.

Storage Replication Based on MetroCluster

Figure 7 shows a high-level overview of the solution. The storage cluster at each site provides local high
availability and is used for the production workload. The data of each site is synchronously replicated to
the other location and is available if there is disaster failover.

9 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 7) Synchronous storage replication.

3 Storage Sizing
The following section provides an overview of the required performance and capacity considerations
needed for sizing a storage system for SAP HANA.
Note: Contact NetApp or your NetApp partner sales representative to assist you in creating a properly
sized storage environment.

3.1 Performance Considerations

SAP has defined a static set of storage KPIs that are valid for all production SAP HANA environments
independent of the memory size of the database hosts and the applications that use the SAP HANA
database. These KPIs are valid for single-host, multiple-host, Business Suite on HANA, Business
Warehouse on HANA, S/4HANA, and BW/4HANA environments. Therefore, the current performance
sizing approach only depends on the number of active SAP HANA hosts that are attached to the storage
system.
Note: Storage performance KPIs are only mandated for production SAP HANA systems, but you can
implement them in all HANA systems.
SAP delivers a performance test tool used to validate the performance of the storage system for active
SAP HANA hosts attached to the storage.
NetApp tested and predefined the maximum number of SAP HANA hosts that can be attached to a
specific storage model, while still fulfilling the required storage KPIs from SAP for production-based SAP
HANA systems.
Note: The storage controllers of the certified FAS product family can also be used for SAP HANA with
other disk types or disk back-end solutions. However, they must be supported by NetApp and

10 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 fulfill SAP HANA TDI performance KPIs. Examples include NetApp Storage Encryption (NSE)
and NetApp FlexArray® technology.
This document describes disk sizing for SAS HDDs and solid-state drives (SSDs).

HDDs
A minimum of 10 data disks (10k RPM SAS) per SAP HANA node is required to fulfill the storage
performance KPIs from SAP.
Note: This calculation is independent of the storage controller and disk shelf used as well as the
capacity requirements of the database.

Solid-State Drives
With SSDs, the number of data disks is determined by the SAS connection throughput from the storage
controllers to the SSD shelf.
The maximum number of SAP HANA hosts that can be run on a single disk shelf and the minimum
number of SSDs required per SAP HANA host were determined by running the SAP performance test
tool. This test does not consider the actual storage capacity requirements of the hosts. In addition, you
must also calculate the capacity requirements to determine the actual storage configuration needed.
• The 12Gb SAS disk shelf (DS224C) with 24 SSDs supports up to 14 SAP HANA hosts when the disk
shelf is connected with 12Gb.
• The 6Gb SAS disk shelf (DS2246) with 24 SSDs supports up to 4 SAP HANA hosts.
The SSDs and the SAP HANA hosts must be equally distributed between both storage controllers.
Table 2 summarizes the supported number of SAP HANA hosts per disk shelf.

Table 2) Number of SAP HANA hosts per disk shelf.

6Gb SAS Shelves (DS2246) 12Gb SAS Shelves
Fully Loaded with 24 SSDs (DS224C)
Fully Loaded with 24 SSDs
Maximum number of SAP HANA
4 14
hosts per disk shelf

Note: This calculation is independent of the storage controller used.

3.2 Mixed Workloads

SAP HANA and other application workloads running on the same storage controller or in the same
storage aggregate are supported. However, it is a NetApp best practice to separate SAP HANA
workloads from all other application workloads.
You might decide to deploy SAP HANA workloads and other application workloads on either the same
storage controller or the same aggregate. If so, you must make sure that adequate performance is
available for SAP HANA within the mixed workload environment. NetApp also recommends that you use
quality of service (QoS) parameters to regulate the effect these other applications could have and to
guarantee throughput for SAP HANA applications.
The SAP performance test tool must be used to check if additional SAP HANA hosts can be run on an
existing storage controller that is already in use for other workloads. SAP application servers can be
safely placed on the same storage controller and/or aggregate as the SAP HANA databases.

11 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
3.3 Capacity Considerations
A detailed description of the capacity requirements for SAP HANA is in the SAP HANA Storage
Requirements white paper.
Note: The capacity sizing of the overall SAP landscape with multiple SAP HANA systems must be
determined by using SAP HANA storage sizing tools from NetApp. Contact NetApp or your
NetApp partner sales representative to validate the storage sizing process for a properly sized
storage environment.

3.4 Configuration of Performance Test Tool

Starting with SAP HANA 1.0 SPS10, SAP introduced parameters to adjust the I/O behavior and optimize
the database for the file and storage system used. These parameters must also be set when storage
performance is being tested with the SAP performance test tool.
NetApp conducted performance tests to define the optimal values. Table 3 lists the parameters that must
be set within the configuration file of the SAP performance test tool.

Table 3) Performance test tool configuration file parameter values.

Parameter Value
max_parallel_io_requests 128
async_read_submit on
async_write_submit_active on
async_write_submit_blocks all

For more information about the configuration of the SAP test tool, see SAP note 1943937 for HWCCT
(SAP HANA 1.0) and SAP note 2493172 for HCMT/HCOT (SAP HANA 2.0).
The following example shows how variables can be set for the HCMT/HCOT execution plan.
…
{
"Comment": "Log Volume: Controls whether read requests are submitted asynchronously,
default is 'on'",
"Name": "LogAsyncReadSubmit",
"Value": "on",
"Request": "false"
},
{
"Comment": "Data Volume: Controls whether read requests are submitted asynchronously,
default is 'on'",
"Name": "DataAsyncReadSubmit",
"Value": "on",
"Request": "false"
},
{
"Comment": "Log Volume: Controls whether write requests can be submitted
asynchronously",
"Name": "LogAsyncWriteSubmitActive",
"Value": "on",
"Request": "false"
},
{
"Comment": "Data Volume: Controls whether write requests can be submitted
asynchronously",
"Name": "DataAsyncWriteSubmitActive",
"Value": "on",
"Request": "false"
},
{

12 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 "Comment": "Log Volume: Controls which blocks are written asynchronously. Only relevant
if AsyncWriteSubmitActive is 'on' or 'auto' and file system is flagged as requiring asynchronous
write submits",
"Name": "LogAsyncWriteSubmitBlocks",
"Value": "all",
"Request": "false"
},
{
"Comment": "Data Volume: Controls which blocks are written asynchronously. Only relevant
if AsyncWriteSubmitActive is 'on' or 'auto' and file system is flagged as requiring asynchronous
write submits",
"Name": "DataAsyncWriteSubmitBlocks",
"Value": "all",
"Request": "false"
},
{
"Comment": "Log Volume: Maximum number of parallel I/O requests per completion queue",
"Name": "LogExtMaxParallelIoRequests",
"Value": "128",
"Request": "false"
},
{
"Comment": "Data Volume: Maximum number of parallel I/O requests per completion queue",
"Name": "DataExtMaxParallelIoRequests",
"Value": "128",
"Request": "false"
},
…

These variables must be used for the test configuration. This is usually the case with the predefined
execution plans SAP delivers with the HCMT/HCOT tool. The following example for a 4k log write test is
from an execution plan.
…
{
"ID": "D664D001-933D-41DE-A904F304AEB67906",
"Note": "File System Write Test",
"ExecutionVariants": [
{
"ScaleOut": {
"Port": "${RemotePort}",
"Hosts": "${Hosts}",
"ConcurrentExecution": "${FSConcurrentExecution}"
},
"RepeatCount": "${TestRepeatCount}",
"Description": "4K Block, Log Volume 5GB, Overwrite",
"Hint": "Log",
"InputVector": {
"BlockSize": 4096,
"DirectoryName": "${LogVolume}",
"FileOverwrite": true,
"FileSize": 5368709120,
"RandomAccess": false,
"RandomData": true,

"AsyncReadSubmit": "${LogAsyncReadSubmit}",
"AsyncWriteSubmitActive": "${LogAsyncWriteSubmitActive}",
"AsyncWriteSubmitBlocks": "${LogAsyncWriteSubmitBlocks}",
"ExtMaxParallelIoRequests": "${LogExtMaxParallelIoRequests}",
"ExtMaxSubmitBatchSize": "${LogExtMaxSubmitBatchSize}",
"ExtMinSubmitBatchSize": "${LogExtMinSubmitBatchSize}",
"ExtNumCompletionQueues": "${LogExtNumCompletionQueues}",
"ExtNumSubmitQueues": "${LogExtNumSubmitQueues}",
"ExtSizeKernelIoQueue": "${ExtSizeKernelIoQueue}"
}
},
…

13 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
3.5 Storage Sizing Process Overview
The number of disks per HANA host and the SAP HANA host density for each storage model were
determined with the SAP performance test tool.
The sizing process requires details such as the number of production and nonproduction SAP HANA
hosts, the RAM size of each host, and the backup retention of the storage-based Snapshot copies. The
number of SAP HANA hosts determines the storage controller and the number of disks required.
The size of the RAM, net data size on the disk of each SAP HANA host, and the Snapshot copy backup
retention period are used as inputs during capacity sizing.
Figure 8 summarizes the sizing process.

Figure 8) Storage sizing overview.

4 Infrastructure Setup and Configuration

The following sections provide SAP HANA infrastructure setup and configuration guidelines.

4.1 Network Setup

Use the following guidelines when configuring the network:
• A dedicated storage network must be used to connect the SAP HANA hosts to the storage controllers
with a 10GbE or faster network.
• Use the same connection speed for storage controllers and SAP HANA hosts. If this is not possible,
ensure that the network components between the storage controllers and the SAP HANA hosts are
able to handle different speeds. For example, you must provide enough buffer space to allow speed
negotiation at the NFS level between storage and hosts. Network components are usually switches,
but other components within blade chassis, such as the back plane, must be considered as well.
• Disable flow control on all physical ports used for storage traffic on the storage network switch and
host layer.
• Each SAP HANA host must have a redundant network connection with a minimum of 10Gb of
bandwidth.
• Jumbo frames with a maximum transmission unit (MTU) size of 9,000 must be enabled on all network
components between the SAP HANA hosts and the storage controllers.
• In a VMware setup, dedicated VMXNET3 network adapters must be assigned to each running virtual
machine. Check the relevant papers mentioned in chapter 1 for further requirements.

14 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 9 shows an example with four SAP HANA hosts attached to a storage controller HA pair using a
10GbE network. Each SAP HANA host has an active-passive connection to the redundant fabric.
At the storage layer, four active connections are configured to provide 10Gb throughput for each SAP
HANA host. In addition, one spare interface is configured on each storage controller.
At the storage layer, a broadcast domain with an MTU size of 9000 is configured, and all required
physical interfaces are added to this broadcast domain. This approach automatically assigns these
physical interfaces to the same failover group. All logical interfaces (LIFs) that are assigned to these
physical interfaces are added to this failover group.

Figure 9) Network configuration example.

In general, it is also possible to use HA interface groups on the servers (bonds) and the storage systems
(for example, Link Aggregation Control Protocol [LACP] and ifgroups). With HA interface groups, verify
that the load is equally distributed between all interfaces within the group. The load distribution depends
on the functionality of the network switch infrastructure.
Note: Depending on the number of SAP HANA hosts and the connection speed used, different numbers
of active physical ports are needed. For details, see Table 4.

4.2 Time Synchronization

You must synchronize the time between the storage controllers and the SAP HANA database hosts. To
do so, set the same time server for all storage controllers and all SAP HANA hosts.

4.3 Storage Controller Setup

This section describes the configuration of the NetApp storage system. You must complete the primary
installation and setup according to the corresponding ONTAP setup and configuration guides.

Storage Efficiency
Inline deduplication, cross-volume inline deduplication, inline compression, and inline compaction are
supported with SAP HANA in an SSD configuration.

15 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Enabling storage efficiency features in an HDD-based configuration is not supported.

NetApp Volume Encryption

The use of NetApp Volume Encryption (NVE) is supported with SAP HANA.

Quality of Service
QoS can be used to limit the storage throughput for specific SAP HANA systems or other applications on
a shared-use controller. One use case would be to limit the throughput of development and test systems
so that they cannot influence production systems in a mixed setup.
During the sizing process, you should determine the performance requirements of a nonproduction
system. Development and test systems can be sized with lower performance values, typically in the range
of 20% to 50% of a production-system KPI as defined by SAP.
Starting with ONTAP 9, QoS is configured on the storage volume level and uses maximum values for
throughput (MBps) and the amount of I/O (IOPS).
Large write I/O has the biggest performance effect on the storage system. Therefore, the QoS throughput
limit should be set to a percentage of the corresponding write SAP HANA storage performance KPI
values in the data and log volumes.

NetApp FabricPool
NetApp FabricPool technology must not be used for active primary file systems in SAP HANA systems.
This includes the file systems for the data and log area as well as the /hana/shared file system. Doing
so results in unpredictable performance, especially during the startup of an SAP HANA system.
Using the “snapshot-only” tearing policy is possible as well as using FabricPool in general at a backup
target such as a SnapVault or SnapMirror destination.
Note: Using FabricPool for tiering Snapshot copies at primary storage or using FabricPool at a backup
target changes the required time for the restore and recovery of a database or other tasks such
as creating system clones or repair systems. Take this into consideration for planning your overall
lifecycle-management strategy, and check to make sure that your SLAs are still being met while
using this function.
FabricPool is a good option for moving log backups to another storage tier. Moving backups affects the
time needed to recover an SAP HANA database. Therefore, the option “tiering-minimum-cooling-days”
should be set to a value that places log backups, which are routinely needed for recovery, on the local
fast storage tier.

Storage Configuration
The following overview summarizes the required storage configuration steps. Each step is covered in
detail in the subsequent sections. In this section, we assume that the storage hardware is set up and that
the ONTAP software is already installed. Also, the connections between the storage ports (10GbE or
faster) and the network must already be in place.
1. Check the correct SAS stack configuration as described in “Disk Shelf Connection.”
2. Create and configure the required aggregates as described in “Aggregate Configuration.”
3. Create a storage virtual machine (SVM) as described in “Storage Virtual Machine Configuration.”
4. Create LIFs as described in “Logical Interface Configuration.”
5. Create volumes within the aggregates as described in “Volume Configuration for SAP HANA Single-
Host Systems” and “Volume Configuration for SAP HANA Multiple-Host Systems.”
6. Set the required volume options as described in “Volume Options.”

16 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
7. Set the required options for NFSv3 as described in “NFS Configuration for NFSv3” or for NFSv4 as
described in “NFS Configuration for NFSv4.”
8. Mount the volumes to namespace and set export policies as described in “Mount Volumes to
Namespace and Set Export Policies.”

Disk Shelf Connection

With HDDs, a maximum of two DS2246 disk shelves or four DS224C disk shelves can be connected to
one SAS stack to provide the required performance for the SAP HANA hosts, as shown in Figure 10. The
disks within each shelf must be distributed equally to both controllers of the HA pair.

Figure 10) Disk shelf connection with HDDs.

With SSDs, a maximum of one disk shelf can be connected to one SAS stack to provide the required
performance for the SAP HANA hosts, as shown in Figure 11. The disks within each shelf must be
distributed equally to both controllers of the HA pair. With the DS224C disk shelf, quad-path SAS cabling
can also be used, but is not required.

Figure 11) Disk shelf connection with SSDs.

Aggregate Configuration
In general, you must configure two aggregates per controller, independent of the disk shelf or drive
technology (SSD or HDD) that is used. For FAS2000 series systems, one data aggregate is enough.

17 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Aggregate Configuration with HDDs
Figure 12 shows a configuration for eight SAP HANA hosts. Four SAP HANA hosts are attached to each
storage controller. Two separate aggregates, one at each storage controller, are configured. Each
aggregate is configured with 4 × 10 = 40 data disks (HDDs).

Figure 12) Aggregate layout with HDDs.

Aggregate Configuration with SDD-Only Systems

In general, you must configure two aggregates per controller, independent of which disk shelf or disk
technology (SSDs or HDDs) is used. For FAS2000 series systems, one data aggregate is enough.
Figure 13 shows a configuration of 12 SAP HANA hosts running on a 12Gb SAS shelf configured with
ADPv2. Six SAP HANA hosts are attached to each storage controller. Four separate aggregates, two at
each storage controller, are configured. Each aggregate is configured with 11 disks with nine data and
two parity disk partitions. For each controller, two spare partitions are available.

18 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Figure 13) Aggregate layout with ADPv2.

Storage Virtual Machine Configuration

Multiple SAP landscapes with SAP HANA databases can use a single SVM. An SVM can also be
assigned to each SAP landscape, if necessary, in case they are managed by different teams within a
company.

Logical Interface Configuration

For SAP HANA production systems, you must use different LIFs for mounting the data volume and the
log volume from the SAP HANA host. Therefore at least two LIFs are required.
The data and log volume mounts of different SAP HANA hosts can share a physical storage network port
by using either the same LIFs or by using individual LIFs for each mount.
The maximum number of data and log volume mounts per physical interface are shown in Table 4.

Table 4) Maximum number of mounts per physical interface.

Ethernet Port Speed 10GbE 25GbE 40GbE 100GeE

Maximum number of log
or data volume mounts 2 6 12 24
per physical port

Note: Sharing one LIF between different SAP HANA hosts might require a remount of data or log
volumes to a different LIF. This change avoids performance penalties if a volume is moved to a
different storage controller.
Development and test systems can use more data and volume mounts or LIFs on a physical network
interface.
For production, development, and test systems, the /hana/shared file system can use the same LIF as
the data or log volume.

19 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Volume Configuration for SAP HANA Single-Host Systems
Figure 14 shows the volume configuration of four single-host SAP HANA systems. The data and log
volumes of each SAP HANA system are distributed to different storage controllers. For example, volume
SID1_data_mnt00001 is configured on controller A, and volume SID1_log_mnt00001 is configured
on controller B.
Note: If only one storage controller of an HA pair is used for the SAP HANA systems, data and log
volumes can also be stored on the same storage controller.
Note: If the data and log volumes are stored on the same controller, access from the server to the
storage must be performed with two different LIFs: one LIF to access the data volume and one to
access the log volume.

Figure 14) Volume layout for SAP HANA multiple single-host systems.

For each SAP HANA DB host, a data volume, a log volume, and a volume for /hana/shared are
configured. Table 5 shows an example configuration for single-host SAP HANA systems.

Table 5) Volume configuration for SAP HANA single-host systems.

Purpose Aggregate 1 at Aggregate 2 at Aggregate 1 at Aggregate 2 at

Controller A Controller A Controller B Controller b
Data, log, and Data volume: Shared volume: Log volume:
shared volumes SID1_data_mnt00001 SID1_shared SID1_log_mnt00001
for system SID1

Data, log, and Log volume: Data volume: Shared volume:

shared volumes SID2_log_mnt00001 SID2_data_mnt00001 SID2_shared
for system SID2

Data, log, and Shared volume: Data volume: Log volume:

shared volumes SID3_shared SID3_data_mnt00001 SID3_log_mnt00001
for system SID3

20 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Purpose Aggregate 1 at Aggregate 2 at Aggregate 1 at Aggregate 2 at
Controller A Controller A Controller B Controller b
Data, log, and Log volume: Shared volume: Data volume:
shared volumes SID4_log_mnt00001 SID4_shared SID4_data_mnt00001
for system SID4

Table 6 shows an example of the mount point configuration for a single-host system. To place the home
directory of the sidadm user on the central storage, the /usr/sap/SID file system should be mounted
from the SID_shared volume.

Table 6) Mount points for single-host systems.

Junction Path Directory Mount Point at HANA Host

SID_data_mnt00001 /hana/data/SID/mnt00001

SID_log_mnt00001 /hana/log/SID/mnt00001

SID_shared usr-sap /usr/sap/SID

shared /hana/shared

Volume Configuration for SAP HANA Multiple-Host Systems

Figure 15 shows the volume configuration of a 4+1 SAP HANA system. The data and log volumes of
each SAP HANA host are distributed to different storage controllers. For example, volume
SID1_data1_mnt00001 is configured on controller A, and volume SID1_log1_mnt00001 is
configured on controller B.
Note: If only one storage controller of an HA pair is used for the SAP HANA system, the data and log
volumes can also be stored on the same storage controller.
Note: If the data and log volumes are stored on the same controller, access from the server to the
storage must be performed with two different LIFs: one to access the data volume and one to
access the log volume.

Figure 15) Volume layout for SAP HANA multiple-host systems.

21 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
For each SAP HANA host, a data volume and a log volume are created. The /hana/shared volume is
used by all hosts of the SAP HANA system. Table 7 shows an example configuration for a multiple-host
SAP HANA system with four active hosts.

Table 7) Volume configuration for SAP HANA multiple-host systems.

Purpose Aggregate 1 at Aggregate 2 at Aggregate 1 at Aggregate 2 at

Controller A Controller A Controller B Controller B
Data and log Data volume: Log volume:
volumes for node 1 SID_data_mnt00001 SID_log_mnt00001

Data and log Log volume: Data volume:

volumes for node 2 SID_log_mnt00002 SID_data_mnt00002

Data and log Data volume: Log volume:

volumes for node 3 SID_data_mnt00003 SID_log_mnt00003

Data and log Log volume: Data volume:

volumes for node 4 SID_log_mnt00004 SID_data_mnt00004

Shared volume for Shared volume:

all hosts SID_shared

Table 8 shows the configuration and the mount points of a multiple-host system with four active SAP
HANA hosts. To place the home directories of the sidadm user of each host on the central storage, the
/usr/sap/SID file systems are mounted from the SID_shared volume.

Table 8) Mount points for multiple-host systems.

Junction Path Directory Mount Point at SAP Note

HANA Host
SID_data_mnt00001 /hana/data/SID/mnt00001 Mounted at all hosts

SID_log_mnt00001 /hana/log/SID/mnt00001 Mounted at all hosts

SID_data_mnt00002 /hana/data/SID/mnt00002 Mounted at all hosts

SID_log_mnt00002 /hana/log/SID/mnt00002 Mounted at all hosts

SID_data_mnt00003 /hana/data/SID/mnt00003 Mounted at all hosts

SID_log_mnt00003 /hana/log/SID/mnt00003 Mounted at all hosts

SID_data_mnt00004 /hana/data/SID/mnt00004 Mounted at all hosts

SID_log_mnt00004 /hana/log/SID/mnt00004 Mounted at all hosts

SID_shared shared /hana/shared/ Mounted at all hosts

SID_shared usr-sap-host1 /usr/sap/SID Mounted at host 1

SID_shared usr-sap-host2 /usr/sap/SID Mounted at host 2

SID_shared usr-sap-host3 /usr/sap/SID Mounted at host 3

SID_shared usr-sap-host4 /usr/sap/SID Mounted at host 4

SID_shared usr-sap-host5 /usr/sap/SID Mounted at host 5

22 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Volume Options
You must verify and set the volume options listed in Table 9 on all SVMs. For some of the commands,
you must switch to the advanced privilege mode within ONTAP.

Table 9) Volume options.

Action Command
Disable visibility of Snapshot directory vol modify -vserver <vserver-name> -volume <volname> -
snapdir-access false

Disable automatic Snapshot copies vol modify –vserver <vserver-name> -volume <volname> -
snapshot-policy none

Disable access time update except of the set advanced

SID_shared volume vol modify -vserver <vserver-name> -volume <volname> -
atime-update false
set admin

NFS Configuration for NFSv3

The NFS options listed in Table 10 must be verified and set on all storage controllers. For some of the
commands shown in Table 10, you must switch to the advanced privilege mode within ONTAP.

Table 10) NFSv3 options.

Action Command
Enable NFSv3 nfs modify -vserver <vserver-name> v3.0 enabled

ONTAP 9: set advanced

Set NFS TCP maximum transfer size to 1MB nfs modify -vserver <vserver_name> -tcp-max-xfer-size
1048576
set admin

ONTAP 8: set advanced

Set NFS read and write size to 64KB nfs modify -vserver <vserver-name> -v3-tcp-max-read-
size 65536
nfs modify -vserver <vserver-name> -v3-tcp-max-write-
size 65536
set admin

NFS Configuration for NFSv4

The NFS options listed in Table 11 must be verified and set on all SVMs.
For some of the commands in Table 11, you must switch to the advanced privilege mode within ONTAP.

Table 11) NFSv4 options.

Action Command
Enable NFSv4 nfs modify -vserver <vserver-name> -v4.1
enabled

ONTAP 9: set advanced

Set NFS TCP maximum transfer size to 1MB nfs modify -vserver <vserver_name>

23 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 Action Command
-tcp-max-xfer-size 1048576
set admin

ONTAP 8: set advanced

Set NFS read and write size to 64KB nfs modify -vserver <vserver_name>
-tcp-max-xfer-size 65536
set admin

Disable NFSv4 access control lists (ACLs) nfs modify -vserver <vserver_name> -v4.1-
acl disabled

Set NFSv4 domain ID nfs modify -vserver <vserver_name> -v4-id-

domain <domain-name>

Disable NFSv4 read delegation nfs modify -vserver <vserver_name> -v4.1-

read-delegation disabled

Disable NFSv4 write delegation nfs modify -vserver <vserver_name> -v4.1-

write-delegation disabled

Set the NFSv4 lease time set advanced

nfs modify -vserver <vserver_name> -v4-
lease-seconds 10
set admin

Disable NFSv4 numeric ids nfs modify -vserver <vserver_name> -v4-

numeric-ids disabled

Note: For NFS version 4.0, replace 4.1 with 4.0 in the previous commands. Although NFSv4.0 is
supported, using NFSv4.1 is preferred.
Note: The NFSv4 domain ID must be set to the same value on all Linux servers (/etc/idmapd.conf)
and SVMs, as described in “SAP HANA Installation Preparations for NFSv4.”
Note: If you are using NFSV4.1, then pNFS is enabled and used by default (recommended).
Set the NFSv4 lease time at the SVM as shown in Table 12 if SAP HANA multiple-host systems are used.

Table 12) Additional NFSv4 options for SAP HANA multiple-host systems.

Action Command
Set the NFSv4 lease time. set advanced
nfs modify -vserver <vserver_name> -v4-
lease-seconds 10
set admin

Starting with HANA 2.0 SPS4, HANA provides parameters to control failover behavior. Instead of setting
the lease time at the SVM level, NetApp recommends using these HANA parameters. The parameters
are within nameserver.ini as shown in Table 13. Keep the default retry interval of 10 seconds within
these sections.

24 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Table 13) Setting SAP HANA failover parameters.

Section within Parameter Value

nameserver.ini

failover normal_retries 9

distributed_watchdog deactivation_retries 11

distributed_watchdog takeover_retries 9

Mount Volumes to Namespace and Set Export Policies

When a volume is created, the volume must be mounted to the namespace. In this document, we assume
that the junction path name is the same as the volume name. By default, the volume is exported with the
default policy. The export policy can be adapted if required.

Mount Volumes to Namespace and Set Export Policies

When a volume is created, the volume must be mounted to the namespace. In this document, we assume
that the junction path name is the same as the volume name. By default, the volume is exported with the
default policy. The export policy can be adapted if necessary.

4.4 Host Setup

All the steps described in this section are valid for both SAP HANA environments on physical servers and
for SAP HANA running on VMware vSphere.

Configuration Parameter for SUSE Linux Enterprise Server

Additional kernel and configuration parameters at each SAP HANA host must be adjusted for the
workload generated by SAP HANA.

SUSE Linux Enterprise Server 12 and 15

Starting with SUSE Linux Enterprise Server 12 SP1, the kernel parameter must be set in a configuration
file in the /etc/sysctl.d directory. For example, a configuration file with the name 91-NetApp-
HANA.conf must be created.
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 16777216
net.core.wmem_default = 16777216
net.core.optmem_max = 16777216
net.ipv4.tcp_rmem = 65536 16777216 16777216
net.ipv4.tcp_wmem = 65536 16777216 16777216
net.core.netdev_max_backlog = 300000
net.ipv4.tcp_slow_start_after_idle=0
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1
If NFSv3 is used for connecting the storage, the sunrpc.tcp_max_slot_table_entries parameter
must be set in/etc/modprobe.d/sunrpc.conf. If the file does not exist, it must first be created by
adding the following line:
options sunrpc tcp_max_slot_table_entries=128

25 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Configuration Parameter for Red Hat Enterprise Linux 7.2 or Later
You must adjust additional kernel and configuration parameters at each SAP HANA host must for the
workload generated by SAP HANA.
If NFSv3 is used for connecting the storage, you must set the parameter
sunrpc.tcp_max_slot_table_entries in/etc/modprobe.d/sunrpc.conf. If the file does not
exist, you must first create it by adding the following line:
options sunrpc tcp_max_slot_table_entries=128

Starting with Red Hat Enterprise Linux 7.2, you must set the kernel parameters in a configuration file in
the /etc/sysctl.d directory. For example, a configuration file with the name 91-NetApp-HANA.conf
must be created.
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 16777216
net.core.wmem_default = 16777216
net.core.optmem_max = 16777216
net.ipv4.tcp_rmem = 65536 16777216 16777216
net.ipv4.tcp_wmem = 65536 16777216 16777216
net.core.netdev_max_backlog = 300000
net.ipv4.tcp_slow_start_after_idle=0
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1

Create Subdirectories in /hana/shared Volume

Note: The examples show an SAP HANA database with SID=NF2.
To create the required subdirectories, take one of the following actions:
• For a single-host system, mount the /hana/shared volume and create the shared and usr-sap
subdirectories.
stlrx300s8-50:/mnt # mount <storage-hostname>:/NF2_shared /mnt/tmp
stlrx300s8-50:/mnt # cd /mnt/tmp
stlrx300s8-50:/mnt/tmp # mkdir shared
stlrx300s8-50:/mnt/tmp # mkdir usr-sap
stlrx300s8-50:/mnt/tmp # umount /mnt/tmp
• For a multiple-host system, mount the /hana/shared volume and create the shared and the usr-
sap subdirectories for each host.
The example commands show a 2+1 multiple-host HANA system.
stlrx300s8-50:/mnt # mount <storage-hostname>:/NF2_shared /mnt/tmp
stlrx300s8-50:/mnt # cd /mnt/tmp
stlrx300s8-50:/mnt/tmp # mkdir shared
stlrx300s8-50:/mnt/tmp # mkdir usr-sap-host1
stlrx300s8-50:/mnt/tmp # mkdir usr-sap-host2
stlrx300s8-50:/mnt/tmp # mkdir usr-sap-host3
stlrx300s8-50:/mnt # cd ..
stlrx300s8-50:/mnt/tmp # umount /mnt/tmp

Create Mount Points

Note: The examples show an SAP HANA database with SID=NF2.
To create the required mount point directories, take one of the following actions:
• For a single-host system, create mount points and set the permissions on the database host.

26 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
stlrx300s8-50:/ # mkdir -p /hana/data/NF2/mnt00001
stlrx300s8-50:/ # mkdir -p /hana/log/NF2/mnt00001
stlrx300s8-50:/ # mkdir -p /hana/shared
stlrx300s8-50:/ # mkdir -p /usr/sap/NF2

stlrx300s8-50:/ # chmod –R 777 /hana/log/NF2

stlrx300s8-50:/ # chmod –R 777 /hana/data/NF2
stlrx300s8-50:/ # chmod -R 777 /hana/shared
stlrx300s8-50:/ # chmod -R 777 /usr/sap/NF2

• For a multiple-host system, create mount points and set the permissions on all worker and standby
hosts.
The following example commands are for a 2+1 multiple-host HANA system.
− First worker host:
stlrx300s8-50:~ # mkdir -p /hana/data/NF2/mnt00001
stlrx300s8-50:~ # mkdir -p /hana/data/NF2/mnt00002
stlrx300s8-50:~ # mkdir -p /hana/log/NF2/mnt00001
stlrx300s8-50:~ # mkdir -p /hana/log/NF2/mnt00002
stlrx300s8-50:~ # mkdir -p /hana/shared
stlrx300s8-50:~ # mkdir -p /usr/sap/NF2

stlrx300s8-50:~ # chmod -R 777 /hana/log/NF2

stlrx300s8-50:~ # chmod -R 777 /hana/data/NF2
stlrx300s8-50:~ # chmod -R 777 /hana/shared
stlrx300s8-50:~ # chmod -R 777 /usr/sap/NF2
− Second worker host:
stlrx300s8-51:~ # mkdir -p /hana/data/NF2/mnt00001
stlrx300s8-51:~ # mkdir -p /hana/data/NF2/mnt00002
stlrx300s8-51:~ # mkdir -p /hana/log/NF2/mnt00001
stlrx300s8-51:~ # mkdir -p /hana/log/NF2/mnt00002
stlrx300s8-51:~ # mkdir -p /hana/shared
stlrx300s8-51:~ # mkdir -p /usr/sap/NF2

stlrx300s8-51:~ # chmod -R 777 /hana/log/NF2

stlrx300s8-51:~ # chmod -R 777 /hana/data/NF2
stlrx300s8-51:~ # chmod -R 777 /hana/shared
stlrx300s8-51:~ # chmod -R 777 /usr/sap/NF2

− Standby host:
stlrx300s8-52:~ # mkdir -p /hana/data/NF2/mnt00001
stlrx300s8-52:~ # mkdir -p /hana/data/NF2/mnt00002
stlrx300s8-52:~ # mkdir -p /hana/log/NF2/mnt00001
stlrx300s8-52:~ # mkdir -p /hana/log/NF2/mnt00002
stlrx300s8-52:~ # mkdir -p /hana/shared
stlrx300s8-52:~ # mkdir -p /usr/sap/NF2

stlrx300s8-52:~ # chmod -R 777 /hana/log/NF2

stlrx300s8-52:~ # chmod -R 777 /hana/data/NF2
stlrx300s8-52:~ # chmod -R 777 /hana/shared
stlrx300s8-52:~ # chmod -R 777 /usr/sap/NF2

Mount File Systems

Different mount options must be used depending on the NFS version and ONTAP release. The following
file systems must be mounted to the hosts:
• /hana/data/SID/mnt0000*
• /hana/log/SID/mnt0000*
• /hana/shared
• /usr/sap/SID
Table 14 shows the NFS versions that must be used for the different file systems for single-host and
multiple-host SAP HANA databases.

27 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Table 14) NFS versions to be used.

File systems SAP HANA single host SAP HANA multiple hosts
/hana/data/SID/mnt0000* NFSv3 or NFSv4 NFSv4

/hana/log/SID/mnt0000* NFSv3 or NFSv4 NFSv4

/hana/shared NFSv3 or NFSv4 NFSv3 or NFSv4

/usr/sap/SID NFSv3 or NFSv4 NFSv3 or NFSv4

Table 15 shows the mount options for the various NFS versions and ONTAP releases. The common
parameters are independent of the NFS and ONTAP versions.
For NFSv3, you must switch off NFS locking to avoid NFS lock cleanup operations if there is a software or
server failure.
With ONTAP 9, the NFS transfer size can be configured up to 1MB. Specifically, with 40GbE or faster
connections to the storage system, you must set the transfer size to 1MB to achieve the expected
throughput values.

Table 15) Mount options.

Common NFSv3 NFSv4 NFSv4.1 NFS Transfer Size NFS Transfer Size
Parameter with ONTAP 9 with ONTAP 8
rw, bg, hard, vers=3, vers=4, vers=4, rsize=1048576, rsize=65536,
timeo=600, nolock, minorversion= minorversion= wsize=1048576, wsize=65536,
noatime, 0, 1,
lock lock

Note: To improve read performance with NFSv3, it is recommended that you use the nconnect=n
mount option, which is available with SUSE Linux Enterprise Server 12 SP4 or later.
Note: Performance tests show that nconnect=8 provides good results.
Note: For NFSv4, the nconnect option is not supported by NetApp for SAP HANA.
To mount the file systems during system boot with the /etc/fstab configuration file, complete the
following steps:
The following example shows a single host SAP HANA database with SID=NF2 using NFSv3 and an NFS
transfer size of 1MB.
1. Add the required file systems to the /etc/fstab configuration file.
stlrx300s8-50:/ # cat /etc/fstab
<storage-vif-data01>:/NF2_data_mnt00001 /hana/data/NF2/mnt00001 nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,nolock 0 0
<storage-vif-log01>:/NF2_log_mnt00001 /hana/log/NF2/mnt00001 nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,nolock 0 0
<storage-vif-data01>:/NF2_shared/usr-sap /usr/sap/NF2 nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg, noatime,nolock 0 0
<storage-vif-data01>:/NF2_shared/shared /hana/shared nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg, noatime,nolock 0 0

2. Run mount –a to mount the file systems on all hosts.

The next example shows a multiple-host SAP HANA database with SID=NF2 using NFSv4.1 for data and
log file systems and NFSv3 for the /hana/shared and /usr/sap/NF2 file systems. An NFS transfer
size of 1MB is used.
1. Add the required file systems to the /etc/fstab configuration file on all hosts.

28 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Note: The /usr/sap/NF2 file system is different for each database host. The following example shows
/NF2_shared/usr_sap_host1.
stlrx300s8-5:/ # cat /etc/fstab
<storage-vif-data01>:/NF2_data_mnt00001 /hana/data/NF2/mnt00001 nfs rw, vers=4
minorversion=1,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,lock 0 0
<storage-vif-data02>:/NF2_data_mnt00002 /hana/data/NF2/mnt00002 nfs rw, vers=4
minorversion=1,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,lock 0 0
<storage-vif-log01>:/NF2_log_mnt00001 /hana/log/NF2/mnt00001 nfs rw, vers=4
minorversion=1,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,lock 0 0
<storage-vif-log02>:/NF2_log_mnt00002 /hana/log/NF2/mnt00002 nfs rw, vers=4
minorversion=1,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,lock 0 0
<storage-vif-data02>:/NF2_shared/usr-sap_host1 /usr/sap/NF2 nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,nolock 0 0
<storage-vif-data02>:/NF2_shared/shared /hana/shared nfs
rw,vers=3,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,nolock 0 0

2. Run mount –a to mount the file systems on all hosts.

4.5 SAP HANA Installation Preparations for NFSv4

NFS version 4 and higher requires user authentication. This authentication can be accomplished by using
a central user management tool such as a Lightweight Directory Access Protocol (LDAP) server or with
local user accounts. The following sections describe how to configure local user accounts.
The administration user <sidadm> and the sapsys group must be created manually on the SAP HANA
hosts and the storage controllers before the installation of the SAP HANA software begins.

SAP HANA Hosts

If it doesn’t exist, the sapsys group must be created on the SAP HANA host. A unique group ID must be
chosen that does not conflict with the existing group IDs on the storage controllers.
The user <sidadm> is created on the SAP HANA host. A unique ID must be chosen that does not conflict
with existing user IDs on the storage controllers.
For a multiple-host SAP HANA system, the user and group ID must be the same on all SAP HANA hosts.
The group and user are created on the other SAP HANA hosts by copying the affected lines in
/etc/group and /etc/passwd from the source system to all other SAP HANA hosts.
Note: The NFSv4 domain must be set to the same value on all Linux servers (/etc/idmapd.conf)
and SVMs. Set the domain parameter “Domain = <domain-name>” in the file
/etc/idmapd.conf for the Linux hosts.
Enable and start the NFS IDMAPD service.
systemctl enable nfs-idmapd.service
systemctl start nfs-idmapd.service

Storage Controllers
The user ID and group ID must be the same on the SAP HANA hosts and the storage controllers. The
group and user are created by entering the following commands on the storage cluster:
vserver services unix-group create -vserver <vserver> -name <group name> -id <group id>
vserver services unix-user create -vserver <vserver> -user <user name> -id <user-id> -primary-gid
<group id>

Additionally, set the group ID of the UNIX user root of the SVM to 0.
vserver services unix-user modify -vserver <vserver> -user root -primary-gid 0

29 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
4.6 I/O Stack Configuration for SAP HANA
Starting with SAP HANA 1.0 SPS10, SAP introduced parameters to adjust the I/O behavior and optimize
the database for the file and storage systems used.
NetApp conducted performance tests to define the ideal values. The following table lists the optimal
values inferred from the performance tests.

Parameter Value
max_parallel_io_requests 128
async_read_submit on
async_write_submit_active on
async_write_submit_blocks all

For SAP HANA 1.0 versions up to SPS12, these parameters can be set during the installation of the SAP
HANA database, as described in SAP note 2267798: Configuration of the SAP HANA Database During
Installation Using hdbparam.
Alternatively, the parameters can be set after the SAP HANA database installation by using the
hdbparam framework.
nf2adm@stlrx300s8-50:/usr/sap/NF2/HDB00> hdbparam --paramset fileio.max_parallel_io_requests=128
nf2adm@stlrx300s8-50:/usr/sap/NF2/HDB00> hdbparam --paramset fileio.async_write_submit_active=on
nf2adm@stlrx300s8-50:/usr/sap/NF2/HDB00> hdbparam --paramset fileio.async_read_submit=on
nf2adm@stlrx300s8-50:/usr/sap/NF2/HDB00> hdbparam --paramset fileio.async_write_submit_blocks=all

Starting with SAP HANA 2.0, hdbparam has been deprecated, and the parameters have been moved to
global.ini. The parameters can be set using SQL commands or SAP HANA Studio. For more details,
see SAP note 2399079: Elimination of hdbparam in HANA 2. You can also set the parameters within
global.ini as shown in the following text:
SS3adm@stlrx300s8-6: /usr/sap/SS3/SYS/global/hdb/custom/config> cat global.ini
…
[fileio]
async_read_submit = on
async_write_submit_active = on
max_parallel_io_requests = 128
async_write_submit_blocks = all
…

4.7 SAP HANA Data Volume Size

As the default, SAP HANA uses only one data volume per SAP HANA service. Due to the maximum file
size limitation of the file system, we recommend limiting the maximum data volume size.
To do so automatically, set the following parameter in global.ini in the section [persistence]:
datavolume_striping = true
datavolume_striping_size_gb = 8000

This creates a new data volume after the 8,000GB limit is reached. SAP note 240005 question 15
provides more information.

4.8 SAP HANA Software Installation

Install on Single-Host System

The SAP HANA software installation does not require any additional preparation for a single-host system.

30 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Install on Multiple-Host System
To install SAP HANA on a multiple-host system, complete the following steps:
1. Using the SAP hdbclm installation tool, start the installation by running the following command at one
of the worker hosts. Use the addhosts option to add the second worker (stlrx300s8-51) and the
standby host (stlrx300s8-52).
stlrx300s8-50:/mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/HDB_LCM_LINUX_X86_64# ./hdblcm --action=install --addhosts=stlrx300s8-
51:role=worker,stlrx300s8-52:role=standby

SAP HANA Lifecycle Management - SAP HANA Database 2.00.030.00.1522209842

************************************************************************

Scanning software locations...

Detected components:
SAP HANA Database (2.00.030.00.1522209842) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server
SAP HANA AFL (incl.PAL,BFL,OFL) (2.00.030.0001.1522223444) in /mnt/hwval/Software/SAP-
Installation/HANA-DB-20SPS3/51053061/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages
SAP HANA EML AFL (2.00.030.0001.1522223444) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/HDB_EML_AFL_10_LINUX_X86_64/packages
SAP HANA EPM-MDS (2.00.030.0001.1522223444) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/SAP_HANA_EPM-MDS_10/packages
SAP HANA Database Client (2.3.78.1521836270) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client
SAP HANA Studio (2.3.35.000000) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio
SAP HANA Smart Data Access (2.00.3.000.0) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/SAP_HANA_SDA_20_LINUX_X86_64/packages
SAP HANA XS Advanced Runtime (1.0.82.303870) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_RT_10_LINUX_X86_64/packages
GUI for HALM for XSA (including product installer) Version 1 (1.12.5) in
/mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACALMPIUI12_5.zip
XSAC FILEPROCESSOR 1.0 (1.000.22) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACFILEPROC00_22.zip
SAP Enterprise Architecture Designer 1.0 for SAP HANA (1.004.) in /mnt/hwval/Software/SAP-
Installation/HANA-DB-20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSAC_HANA_EADESIGNER-1.4.0.zip
SAP HANA tools for accessing catalog content, data preview, SQL console, etc. (2.005.36) in
/mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSAC_HRTT_20/XSACHRTT05_36.zip
XS Messaging Service 1 (1.003.2) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACMESSSRV03_2.zip
XS Monitoring 1 (1.006.3) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACMONITORING06_3.zip
Develop and run portal services for custome apps on XSA (1.002.2) in /mnt/hwval/Software/SAP-
Installation/HANA-DB-20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACPORTALSERV02_2.zip
SAP Web IDE Web Client (4.003.0) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSAC_SAP_WEB_IDE_20/XSACSAPWEBIDE03_0.zip
XS Services 1 (1.006.5) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACSERVICES06_5.zip
SAPUI5 FESV4 XSA 1 - SAPUI5 1.52 (1.052.9) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACUI5FESV452_9.zip
SAPUI5 SERVICE BROKER XSA 1 - SAPUI5 Service Broker 1.0 (1.000.1) in /mnt/hwval/Software/SAP-
Installation/HANA-DB-20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACUI5SB00_1.zip
Xsa Cockpit 1 (1.001.7) in /mnt/hwval/Software/SAP-Installation/HANA-DB-
20SPS3/51053061/DATA_UNITS/XSA_CONTENT_10/XSACXSACOCKPIT01_7.zip

SAP HANA Database version '2.00.030.00.1522209842' will be installed.

Select additional components for installation:

Index | Components | Description

---------------------------------------------------------------------------------------------

31 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 1 | all | All components
2 | server | No additional components
3 | client | Install SAP HANA Database Client version 2.3.78.1521836270
4 | studio | Install SAP HANA Studio version 2.3.35.000000
5 | smartda | Install SAP HANA Smart Data Access version 2.00.3.000.0
6 | xs | Install SAP HANA XS Advanced Runtime version 1.0.82.303870
7 | afl | Install SAP HANA AFL (incl.PAL,BFL,OFL) version 2.00.030.0001.1522223444
8 | eml | Install SAP HANA EML AFL version 2.00.030.0001.1522223444
9 | epmmds | Install SAP HANA EPM-MDS version 2.00.030.0001.1522223444

Enter comma-separated list of the selected indices

2. Verify that the installation tool installed all selected components at all worker and standby hosts.

4.9 Adding Additional Data Volume Partitions for SAP HANA Single-Host
Systems
Starting with SAP HANA 2.0 SPS4, you can configure additional data volume partitions, which allows you
to configure two or more volumes for the data volume of an SAP HANA tenant database. You can also
scale beyond the size and performance limits of a single volume.
Note: Using two or more individual volumes for the data volume is available for SAP HANA single-host
and multiple-host systems. You can add additional data volume partitions at any time, but doing
so might require a restart of the SAP HANA database.

Enabling Additional Data Volume Partitions

Add the following entry within global.ini:

[customizable_functionalities]
persistence_datavolume_partition_multipath = true

Restart the database to enable the feature. To avoid restarting the database, add the parameter to
global.ini with SAP HANA Studio using Systemdb configuration.

Volume Configuration for a Single-Host SAP HANA System

The layout of volumes for a single-host SAP HANA system with multiple partitions is like the layout for a
system with one data volume partition, but with an additional data volume stored on a different aggregate
as the log volume and the other data volume. Table 16 shows an example configuration of an SAP HANA
single-host system with two data volume partitions.

Table 16) Volume configuration for SAP HANA single-host system with two data partitions.

Aggregate 1 at Aggregate 2 at Aggregate 1 at Aggregate 2 at

Controller A Controller A Controller B Controller b
Data volume: Shared volume: Data volume: Log volume:
SID_data_mnt00001 SID_shared SID_data2_mnt00001 SID_log_mnt00001

Table 17 shows an example of the mount point configuration for a single-host system with two data
volume partitions.

Table 17) Mount points for single-host system with two data partitions.

Junction Path Directory Mount Point at HANA Host

SID_data_mnt00001 /hana/data/SID/mnt00001

32 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 Junction Path Directory Mount Point at HANA Host
SID_data2_mnt00001 /hana/data2/SID/mnt00001

SID_log_mnt00001 /hana/log/SID/mnt00001

SID_shared usr-sap /usr/sap/SID

shared /hana/shared

Create the new data volume and mount it to the namespace using either ONTAP System Manager or the
ONTAP cluster command line interface.

Volume Configuration for Multiple-Host SAP HANA system

The layout of volumes for a multiple-host SAP HANA system with multiple partitions is like the layout for a
system with one data volume partition, but with an additional data volume stored on a different aggregate
as the log volume and the other data volume. Table 18 shows an example configuration of an SAP HANA
multiple-host system with two data volume partitions.

Table 18) Volume configuration for SAP HANA multiple-host system with two data partitions.

Purpose Aggregate 1 at Aggregate 2 at Aggregate 1 at Aggregate 2 at

Controller A Controller A Controller B Controller B
Data Data volume: Log volume: Data2 volume:
and log SID_data_mnt00001 SID_log_mnt00001 SID_data2_mnt00001
volumes
for node
1

Data Log volume: Data2 volume: Data volume:

and log SID_log_mnt00002 SID_data2_mnt00002 SID_data_mnt00002
volumes
for node
2

Data Data volume: Data2 volume: Log volume:

and log SID_data_mnt00003 SID_data2_mnt00003 SID_log_mnt00003
volumes
for node
3

Data Data2 volume: Log volume: Data volume:

and log SID_data2_mnt00004 SID_log_mnt00004 SID_data_mnt00004
volumes
for node
4

Shared Shared volume:

volume SID_shared
for all
hosts

Table 19 shows an example of the mount point configuration for a single-host system with two data
volume partitions.

33 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Table 19) Mount points for multiple-host system with two data partitions.

Junction Path Directory Mount Point at SAP HANA Host Note

SID_data_mnt00001 /hana/data/SID/mnt00001 Mounted at all hosts

SID_data2_mnt00001 /hana/data2/SID/mnt00001 Mounted at all hosts

SID_log_mnt00001 /hana/log/SID/mnt00001 Mounted at all hosts

SID_data_mnt00002 /hana/data/SID/mnt00002 Mounted at all hosts

SID_data2_mnt00002 /hana/data2/SID/mnt00002 Mounted at all hosts

SID_log_mnt00002 /hana/log/SID/mnt00002 Mounted at all hosts

SID_data_mnt00003 /hana/data/SID/mnt00003 Mounted at all hosts

SID_data2_mnt00003 /hana/data2/SID/mnt00003 Mounted at all hosts

SID_log_mnt00003 /hana/log/SID/mnt00003 Mounted at all hosts

SID_data_mnt00004 /hana/data/SID/mnt00004 Mounted at all hosts

SID_data2_mnt00004 /hana/data2/SID/mnt00004 Mounted at all hosts

SID_log_mnt00004 /hana/log/SID/mnt00004 Mounted at all hosts

SID_shared shared /hana/shared/SID Mounted at all hosts

SID_shared usr-sap-host1 /usr/sap/SID Mounted at host 1

SID_shared usr-sap-host2 /usr/sap/SID Mounted at host 2

SID_shared usr-sap-host3 /usr/sap/SID Mounted at host 3

SID_shared usr-sap-host4 /usr/sap/SID Mounted at host 4

SID_shared usr-sap-host5 /usr/sap/SID Mounted at host 5

Create the new data volume and mount it to the namespace using either ONTAP System Manager or the
ONTAP cluster command line interface.

Host Configuration
In addition to the tasks described in section 4.4 “Host Setup,” you must create the additional mount points
and fstab entries for the new additional data volume(s), and you must mount the new volumes.
3. Create additional mount points:
• For a single-host system, create mount points and set the permissions on the database host.
stlrx300s8-50:/ # mkdir -p /hana/data2/SID/mnt00001
stlrx300s8-50:/ # chmod –R 777 /hana/data2/SID

• For a multiple-host system, create mount points and set the permissions on all worker and
standby hosts. The following example commands are for a 2+1 multiple-host HANA system.
− First worker host:
stlrx300s8-50:~ # mkdir -p /hana/data2/SID/mnt00001
stlrx300s8-50:~ # mkdir -p /hana/data2/SID/mnt00002
stlrx300s8-50:~ # chmod -R 777 /hana/data2/SID

− Second worker host:

34 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
 stlrx300s8-51:~ # mkdir -p /hana/data2/SID/mnt00001
stlrx300s8-51:~ # mkdir -p /hana/data2/SID/mnt00002
stlrx300s8-51:~ # chmod -R 777 /hana/data2/SID

− Standby host:
stlrx300s8-51:~ # mkdir -p /hana/data2/SID/mnt00001
stlrx300s8-51:~ # mkdir -p /hana/data2/SID/mnt00002
stlrx300s8-51:~ # chmod -R 777 /hana/data2/SID

4. Add the additional file systems to the /etc/fstab configuration file on all hosts. An example for a
single-host system using NFSv4.1 is as follows:
<storage-vif-data02>:/SID_data2_mnt00001 /hana/data2/SID/mnt00001 nfs rw, vers=4
minorversion=1,hard,timeo=600,rsize=1048576,wsize=1048576,bg,noatime,lock 0 0

Note: Use a different storage virtual interface for connecting to each data volume to make sure that
different TCP sessions are used for each volume.
5. To mount the file systems, run the mount –a command.

Adding an Additional Data Volume Partition

Execute the following SQL statement against the tenant database to add an additional data volume
partition to your tenant database. Use the path to additional volume(s):
ALTER SYSTEM ALTER DATAVOLUME ADD PARTITION PATH '/hana/data2/SID/';

Figure 16) Add additional data volume partition.

Where to Find Additional Information

To learn more about the information described in this document, refer to the following documents and/or
websites:
• Best Practices and Recommendations for Scale-Up Deployments of SAP HANA on VMware vSphere
www.vmware.com/files/pdf/SAP_HANA_on_vmware_vSphere_best_practices_guide.pdf
• Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware
vSphere
www.vmware.com/files/pdf/sap-hana-scale-out-deployments-on-vsphere.pdf

35 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
• SAP Certified Enterprise Storage Hardware for SAP HANA
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/enterprise-storage.html
• SAP HANA Storage Requirements
http://go.sap.com/documents/2015/03/74cdb554-5a7c-0010-82c7-eda71af511fa.html
• SAP HANA Tailored Data Center Integration Frequently Asked Questions
www.sap.com/documents/2016/05/e8705aae-717c-0010-82c7-eda71af511fa.html
• TR-4646: SAP HANA Disaster Recovery with Asynchronous Storage Replication Using SnapCenter
4.0 SAP HANA Plug-In
www.netapp.com/us/media/tr-4646.pdf
• TR-4614: SAP HANA Backup and Recovery with SnapCenter
www.netapp.com/us/media/tr-4614.pdf
• TR-4338: SAP HANA on VMware vSphere with NetApp FAS and AFF Systems
www.netapp.com/us/media/tr-4338.pdf
• TR-4667: Automating SAP System Copies Using the SnapCenter 4.0 SAP HANA Plug-In
www.netapp.com/us/media/tr-4667.pdf
• NetApp Documentation Centers
https://www.netapp.com/us/documentation/index.aspx
• NetApp FAS Storage System Resources
https://mysupport.netapp.com/info/web/ECMLP2676498.html
• SAP HANA Software Solutions
www.netapp.com/us/solutions/applications/sap/index.aspx#sap-hana

Version History
Version Date Document Version History
Version 1.0 April 2014 Initial version

Version 2.0 August 2014 Updated disk sizing selection and added SSD configuration
Added Red Hat Enterprise Linux OS configuration
Added SAP HANA storage connector information
Added information about VMware configuration

Version 2.1 November 2014 Updated storage sizing section

Version 2.2 January 2015 Updated storage connector API section

Updated aggregate and volume configuration

Version 2.3 March 2015 Added new STONITH implementation for SAP HANA SPS9
Added compute node setup and HANA installation section

Version 3.0 October 2015 Added NFSv4 support for cDOT

Updated sysctl parameter
Included I/O parameter for SAP HANA and HWVAL > SPS10

Version 3.1 March 2016 Updated capacity sizing

Updated mount options for /hana/shared
Updated sysctl parameter

36 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
Version Date Document Version History
Version 4.0 February 2017 New NetApp storage systems and disk shelves
New features of ONTAP 9
Support for 40GbE
New OS releases (SUSE Linux Enterprise Server12 SP1 and
Red Hat Enterprise Linux 7.2)
New SAP HANA release

Version 4.1 July 2017 Minor updates

Version 5.0 September 2018 New NetApp storage systems

New OS releases (SUSE Linux Enterprise Server 12 SP3 and
Red Hat Enterprise Linux 7.4)
Additional minor changes
SAP HANA 2.0 SPS3

Version 5.1 September 2019 New OS releases (SUSE Linux Enterprise Server 12 SP4,
SUSE Linux Enterprise Server 15, and Red Hat Enterprise Linux
7.6)
Max data volume size
Minor changes

Version 5.2 December 2019 New NetApp storage systems

New OS release SUSE Linux Enterprise Server 15 SP1

Version 5.3 March 2020 Support of nconnect for NFSv3

New OS release Red Hat Enterprise Linux 8

Version 5.4 May 2020 Introduced multiple data partition features available since SAP
HANA 2.0 SPS4

Version 5.5 June 2020 Additional information about optional functionalities

Minor updates

37 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.
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.
Copyright Information
Copyright © 2020 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).
Trademark Information
NETAPP, the NETAPP logo, and the marks listed at http://www.netapp.com/TM are trademarks of
NetApp, Inc. Other company and product names may be trademarks of their respective owners.

TR-4290-0620

38 SAP HANA on NetApp FAS Systems with NFS—Configuration Guide © 2020 NetApp, Inc. All rights reserved.