Suggest changes
PDFs
Multiple hosts
This section describes the configuration of the NetApp storage system specific to SAP HANA multiple-hosts systems
Volume and LUN configuration for SAP HANA multiple-host systems
The following figure shows the volume configuration of a 4+1 multiple-host SAP HANA system. The data volumes and log volumes of each SAP HANA host are distributed to different storage controllers. For example, the volume SID_data_mnt00001 is configured on controller A and the volume SID_log_mnt00001 is configured on controller B. One LUN is configured within each volume.
The /hana/shared volume must be accessible by all HANA hosts and is therefore exported by using NFS. Even though there are no specific performance KPIs for the /hana/shared file system, NetApp recommends using a 10Gb Ethernet connection.
|
If only one storage controller of an HA pair is used for the SAP HANA system, data and log volumes can also be stored on the same storage controller. |
|
|
NetApp ASA systems do not support NFS as a protocol. NetApp recommends using an additional AFF or FAS system for the /hana/shared file system.
|
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. The following table shows an example configuration for a 4+1 multiple-host SAP HANA system.
| Purpose | Aggregate 1 at Controller A | Aggregate 2 at Controller A | Aggregate 1 at Controller B | Aggregate 2 at Controller B |
|---|---|---|---|---|
Data and log volumes for node 1 |
Data volume: SID_data_mnt00001 |
– |
Log volume: SID_log_mnt00001 |
– |
Data and log volumes for node 2 |
Log volume: SID_log_mnt00002 |
– |
Data volume: SID_data_mnt00002 |
– |
Data and log volumes for node 3 |
– |
Data volume: SID_data_mnt00003 |
– |
Log volume: SID_log_mnt00003 |
Data and log volumes for node 4 |
– |
Log volume: SID_log_mnt00004 |
– |
Data volume: SID_data_mnt00004 |
Shared volume for all hosts |
Shared volume: SID_shared |
– |
– |
– |
The following table shows the configuration and the mount points of a multiple-host system with four active SAP HANA hosts.
| LUN or volume | Mount point at SAP HANA host | Note |
|---|---|---|
LUN: SID_data_mnt00001 |
/hana/data/SID/mnt00001 |
Mounted using storage connector |
LUN: SID_log_mnt00001 |
/hana/log/SID/mnt00001 |
Mounted using storage connector |
LUN: SID_data_mnt00002 |
/hana/data/SID/mnt00002 |
Mounted using storage connector |
LUN: SID_log_mnt00002 |
/hana/log/SID/mnt00002 |
Mounted using storage connector |
LUN: SID_data_mnt00003 |
/hana/data/SID/mnt00003 |
Mounted using storage connector |
LUN: SID_log_mnt00003 |
/hana/log/SID/mnt00003 |
Mounted using storage connector |
LUN: SID_data_mnt00004 |
/hana/data/SID/mnt00004 |
Mounted using storage connector |
LUN: SID_log_mnt00004 |
/hana/log/SID/mnt00004 |
Mounted using storage connector |
Volume: SID_shared |
/hana/shared |
Mounted at all hosts using NFS and /etc/fstab entry |
|
|
With the described configuration, the /usr/sap/SID directory in which the default home directory of user SIDadm is stored, is on the local disk for each HANA host. In a disaster recovery setup with disk-based replication, NetApp recommends creating four additional subdirectories in the SID_shared volume for the /usr/sap/SID file system so that each database host has all its file systems on the central storage.
|
Volume and LUN configuration for SAP HANA multiple-host systems using Linux LVM
The Linux LVM can be used to increase performance and to address LUN size limitations. The different LUNs of an LVM volume group should be stored within a different aggregate and at a different controller.
|
|
It is not necessary to use LVM to combine several LUN to fulfill the SAP HANA KPIs, but it is recommended |
The following table shows an example for two LUNs per volume group for a 2+1 SAP HANA multiple host system.
| Purpose | Aggregate 1 at Controller A | Aggregate 2 at Controller A | Aggregate 1 at Controller B | Aggregate 2 at Controller B |
|---|---|---|---|---|
Data and log volumes for node 1 |
Data volume: SID_data_mnt00001 |
Log2 volume: SID_log2_mnt00001 |
Log volume: SID_log_mnt00001 |
Data2 volume: SID_data2_mnt00001 |
Data and log volumes for node 2 |
Log2 volume: SID_log2_mnt00002 |
Data volume: SID_data_mnt00002 |
Data2 volume: SID_data2_mnt00002 |
Log volume: SID_log_mnt00002 |
Shared volume for all hosts |
Shared volume: SID_shared |
– |
– |
– |
Volume options
The volume options listed in the following table must be verified and set on all SVMs.
| Action | |
|---|---|
Disable automatic Snapshot copies |
vol modify –vserver <vserver-name> -volume <volname> -snapshot-policy none |
Disable visibility of Snapshot directory |
vol modify -vserver <vserver-name> -volume <volname> -snapdir-access false |
Creating LUNs, volumes, and mapping LUNs to initiator groups
You can use NetApp ONTAP System Manager to create storage volumes and LUNs and the map them to the igroups of the servers and the ONTAP CLI. This guide describes the usage of the CLI.
Creating LUNs, volumes, and mapping LUNs to initiator groups using the CLI
This section shows an example configuration using the command line with ONTAP 9 for a 2+1 SAP HANA multiple host system with SID FC5 using LVM and two LUNs per LVM volume group:
-
Create all necessary volumes.
vol create -volume FC5_data_mnt00001 -aggregate aggr1_1 -size 1200g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_log_mnt00002 -aggregate aggr2_1 -size 280g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_log_mnt00001 -aggregate aggr1_2 -size 280g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_data_mnt00002 -aggregate aggr2_2 -size 1200g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_data2_mnt00001 -aggregate aggr1_2 -size 1200g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_log2_mnt00002 -aggregate aggr2_2 -size 280g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_log2_mnt00001 -aggregate aggr1_1 -size 280g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_data2_mnt00002 -aggregate aggr2_1 -size 1200g -snapshot-policy none -foreground true -encrypt false -space-guarantee none vol create -volume FC5_shared -aggregate aggr1_1 -size 512g -state online -policy default -snapshot-policy none -junction-path /FC5_shared -encrypt false -space-guarantee none
-
Create all LUNs.
lun create -path /vol/FC5_data_mnt00001/FC5_data_mnt00001 -size 1t -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_data2_mnt00001/FC5_data2_mnt00001 -size 1t -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_data_mnt00002/FC5_data_mnt00002 -size 1t -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_data2_mnt00002/FC5_data2_mnt00002 -size 1t -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_log_mnt00001/FC5_log_mnt00001 -size 260g -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_log2_mnt00001/FC5_log2_mnt00001 -size 260g -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_log_mnt00002/FC5_log_mnt00002 -size 260g -ostype linux -space-reserve disabled -space-allocation disabled -class regular lun create -path /vol/FC5_log2_mnt00002/FC5_log2_mnt00002 -size 260g -ostype linux -space-reserve disabled -space-allocation disabled -class regular
-
Create the initiator group for all servers belonging to system FC5.
lun igroup create -igroup HANA-FC5 -protocol fcp -ostype linux -initiator 10000090fadcc5fa,10000090fadcc5fb,10000090fadcc5c1,10000090fadcc5c2,10000090fadcc5c3,10000090fadcc5c4 -vserver hana
-
Map all LUNs to created initiator group.
lun map -path /vol/FC5_data_mnt00001/FC5_data_mnt00001 -igroup HANA-FC5 lun map -path /vol/FC5_data2_mnt00001/FC5_data2_mnt00001 -igroup HANA-FC5 lun map -path /vol/FC5_data_mnt00002/FC5_data_mnt00002 -igroup HANA-FC5 lun map -path /vol/FC5_data2_mnt00002/FC5_data2_mnt00002 -igroup HANA-FC5 lun map -path /vol/FC5_log_mnt00001/FC5_log_mnt00001 -igroup HANA-FC5 lun map -path /vol/FC5_log2_mnt00001/FC5_log2_mnt00001 -igroup HANA-FC5 lun map -path /vol/FC5_log_mnt00002/FC5_log_mnt00002 -igroup HANA-FC5 lun map -path /vol/FC5_log2_mnt00002/FC5_log2_mnt00002 -igroup HANA-FC5