Set up FSx for ONTAP file system, SVMs, and volumes - SAP HANA on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Set up FSx for ONTAP file system, SVMs, and volumes

Before you create FSx for ONTAP file system, determine the total storage space you need for your SAP HANA workload. You can increase the storage size later. To decrease the storage size, you must create a new file system.

To create a FSx for ONTAP file system, see Step 1: Create an Amazon FSx for NetApp ONTAP file system. For more information, see Managing FSx for ONTAP file systems.

Note

Only single Availability Zone file systems are supported for SAP HANA workloads.

Create storage virtual machines (SVM)

You get one SVM per FSx for ONTAP file system by default. You can create additional SVMs at any time. For optimal performance, mount data and log volumes using different IP addresses. You can achieve this using separate SVMs for data and log volumes. If you plan to use NetApp SnapCenter, all SVMs used for SAP HANA must have unique names. You don't need to join your file system to Active Directory for SAP HANA. For more information, see Managing FSx for ONTAP storage virtual machines.

Volume configuration

The storage capacity of your file system should align with the needs of /hana/shared, /hana/data, and /hana/log volumes. You must also consider the capacity required for snapshots, if applicable.

We recommend creating separate FSx for ONTAP volumes for each of SAP HANA data, log, shared, and binary volumes. The following table lists the recommended minimum sizes per volume.

Volume Recommended size for scale-up Recommended size for scale-out
/usr/sap 50 GiB 50 GiB
/hana/shared Minimum of 1 x memory of your Amazon EC2 instance or 1TB 1 x memory of your Amazon EC2 instance for every 4 subordinate nodes*
/hana/data At least 1.2 x memory of your Amazon EC2 instance At least 1.2 x memory of your Amazon EC2 instance
/hana/log Minimum of 0.5 x memory of your Amazon EC2 instance or 600 GiB Minimum of 0.5 x memory of your Amazon EC2 instance or 600 GiB

*For example, if you have 2-4 scale-out nodes, you need 1 x memory of your single Amazon EC2 instance. If you have 5-8 scale-out nodes, you need 2 x memory of your single Amazon EC2 instance.

The following limitations apply when you create a FSx for ONTAP file system for SAP HANA.

  • Storage Efficiency is not supported for SAP HANA and must be disabled.

  • Capacity Pool Tiering is not supported for SAP HANA and must be set to None.

  • Daily automatic backups must be disabled for SAP HANA. Default FSx for ONTAP backups are not application-aware and cannot be used to restore SAP HANA to a consistent state.

Volume layout

SAP HANA scale-up

The following table presents an example of volume and mount point configuration for scale-up setup. It includes a single host. HDB is the SAP HANA system ID. To place the home directory of the hdbadm user on the central storage, the /usr/sap/HDB file system must be mounted from the HDB_shared volume.

Volume name Junction path Directory Mount point
HDB_data_mnt00001 HDB_data_mnt00001 - /hana/data/HDB/mnt00001
HDB_log_mnt00001 HDB_log_mnt00001 - /hana/log/HDB/mnt00001
HDB_shared HDB_shared usr-sap /usr/sap/HDB
shared /hana/shared

SAP HANA scale-out

You must mount all the data, log, and shared volumes in every node, including the standby node.

The following table presents an example of volume and mount point configuration for a scale-out setup. It includes four active and one standby host. HDB is the SAP HANA system ID. The home (/usr/sap/HDB) and shared ((/hana/shared) directories of every host are stored in the HDB_shared volume. To place the home directory of the hdbadm user on the central storage, the /usr/sap/HDB file system must be mounted from the HDB_shared volume.

Volume name Junction path Directory Mount point Note
HDB_data_mnt00001 HDB_data_mnt00001 N/A /hana/data/HDB/mnt00001 Mounted on all hosts
HDB_log_mnt00001 HDB_log_mnt00001 N/A /hana/log/HDB/mnt00001 Mounted on all hosts
HDB_data_mnt00002 HDB_data_mnt00002 N/A /hana/data/HDB/mnt00002 Mounted on all hosts
HDB_log_mnt00002 HDB_log_mnt00002 N/A /hana/log/HDB/mnt00002 Mounted on all hosts
HDB_data_mnt00003 HDB_data_mnt00003 N/A /hana/data/HDB/mnt00003 Mounted on all hosts
HDB_log_mnt00003 HDB_log_mnt00003 N/A /hana/log/HDB/mnt00003 Mounted on all hosts
HDB_data_mnt00004 HDB_data_mnt00004 N/A /hana/data/HDB/mnt00004 Mounted on all hosts
HDB_log_mnt00004 HDB_log_mnt00004 N/A /hana/log/HDB/mnt00004 Mounted on all hosts
HDB_shared HDB_shared HDB_shared /hana/shared/HDB Mounted on all hosts
HDB_shared HDB_shared usr-sap-host1 /usr/sap/HDB Mounted on host 1
HDB_shared HDB_shared usr-sap-host2 /usr/sap/HDB Mounted on host 2
HDB_shared HDB_shared usr-sap-host3 /usr/sap/HDB Mounted on host 3
HDB_shared HDB_shared usr-sap-host4 /usr/sap/HDB Mounted on host 4
HDB_shared HDB_shared usr-sap-host5 /usr/sap/HDB Mounted on host 5

File system setup

After creating a FSx for ONTAP file system, you must complete additional file system setup.

Set administrative password

If you did not create an administrative password during FSx for ONTAP file system creation, you must set an ONTAP administrative password for fsxadmin user.

The administrative password enables you to access the file system via SSH, the ONTAP CLI, and REST API. To use tools like NetApp SnapCenter, you must have an administrative password.

Sign in to the management endpoint via SSH

Get the DNS name of the management endpoint from Amazon console. Sign in to the management endpoint via SSH, using the fsxadmin user and administrative password.

ssh fsxadmin@management.<file-system-id>.fsx.<aws-region>.amazonaws.com Password:

Set TCP max transfer size

We recommend a TCP max transfer size of 262,144 for your SAP HANA workloads. Elevate the privilege level to advanced and use the following command on each SVM.

set advanced nfs modify -vserver <svm> -tcp-max-xfer-size 262144 set admin

Set the lease time on NFSv4 protocol

This task applies to SAP HANA scale-out with standby node setup.

Lease period refers to the time in which ONTAP irrevocably grants a lock to a client. It is set to 30 seconds by default. You can have faster server recovery by setting shorter lease time.

You can change the lease time with the following command.

set advanced
 nfs modify -vserver <svm> -v4-lease-seconds 10 set admin
Note

Starting with SAP HANA 2.0 SPS4, SAP provides parameters to control failover behavior. NetApp recommends using these parameters instead of setting the lease time at the SVM level. For more details, see.

Disable snapshots

FSx for ONTAP automatically enables a snapshot policy for volumes that take hourly snapshots. The default policy offers limited value to SAP HANA due to missing application awareness. We recommend disabling the automatic snapshots by setting the policy to none. You can disable snapshots during volume creation or by using the following command.

volume modify -vserver <vserver-name> -volume <volume-name> -snapshot-policy none

Data volume

The automatic FSx for ONTAP snapshots do not have application awareness. A database-consistent snapshot of the SAP HANA data volume must be prepared by creating a data snapshot. For more information, see Create a Data Snapshot.

Log volume

The log volume is automatically backed up every 15 minutes by SAP HANA. An hourly volume snapshot does not offer any additional value in terms of RPO reduction.

The high frequency of changes on the log volume can rapidly increase the total capacity used for snapshots. This can cause the log volume to run out of capacity, making the SAP HANA workload unresponsive.

Quality of Service (QoS)

Quality of Service (QoS) enables FSx for ONTAP to consistently deliver predictable performance to multiple applications, and eliminate noisy neighbor applications. When sharing a file system, you can use the quality of service feature for consistent performance and reduced interference between competing workloads. For more information, see Using Quality of Service in Amazon FSx for NetApp ONTAP.

QoS is configured by creating a QoS policy group, setting ceiling or floor performance levels (minimum or maximum performance), and assigning the policy to an SVM or volume. Performance can be specified in either IOPS or throughput.

Example

You are creating a test system, based on a snapshot from production, on the same file system as your production SAP HANA database. You want to ensure that the test system does not impact the performance of the production system. You create a QoS policy group (qos-test) and define an upper limit of 200 MB/s for data and log volumes (vol-data and vol-log), which share the same SVM (svm-test).

# Create QoS policy group qos policy-group create -policy-group qos-test -vserver svm-test -is-shared false -max-throughput 200MBs # Assign QoS policy group to data on log volumes volume modify -vserver svm-test -volume vol-data -qos-policy-group qos-test volume modify -vserver svm-test -volume vol-log -qos-policy-group qos-test