Skip to main content
NetApp solutions for SAP

Contributors netapp-mschoen
PDFs

Single host

This section describes the configuration of the NetApp storage system specific to SAP HANA single-host systems

Volume and LUN configuration for SAP HANA single-host systems

The following figure 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. Within each volume, a single LUN is configured.

Note If only one storage controller of a HA pair is used for the SAP HANA systems, data volumes and log volumes can also be stored on the same storage controller.

Figure showing input/output dialog or representing written content

For each SAP HANA host, a data volume, a log volume, and a volume for /hana/shared are configured. The following table shows an example configuration with four SAP HANA single-host systems.

Purpose Aggregate 1 at Controller A Aggregate 2 at Controller A Aggregate 1 at Controller B Aggregate 2 at Controller B

Data, log, and shared volumes for system SID1

Data volume: SID1_data_mnt00001

Shared volume: SID1_shared

–

Log volume: SID1_log_mnt00001

Data, log, and shared volumes for system SID2

–

Log volume: SID2_log_mnt00001

Data volume: SID2_data_mnt00001

Shared volume: SID2_shared

Data, log, and shared volumes for system SID3

Shared volume: SID3_shared

Data volume: SID3_data_mnt00001

Log volume: SID3_log_mnt00001

–

Data, log, and shared volumes for system SID4

Log volume: SID4_log_mnt00001

–

Shared volume: SID4_shared

Data volume: SID4_data_mnt00001

The following table shows an example of the mount point configuration for a single-host system.

LUN Mount point at SAP HANA host Note

SID1_data_mnt00001

/hana/data/SID1/mnt00001

Mounted using /etc/fstab entry

SID1_log_mnt00001

/hana/log/SID1/mnt00001

Mounted using /etc/fstab entry

SID1_shared

/hana/shared/SID1

Mounted using /etc/fstab entry
Note With the described configuration, the /usr/sap/SID1 directory in which the default home directory of user SID1adm is stored, is on the local disk. In a disaster recovery setup with disk-based replication, NetApp recommends creating an additional LUN within the SID1_shared volume for the /usr/sap/SID1 directory so that all file systems are on the central storage.

Volume and LUN configuration for SAP HANA single-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. The following table shows an example for two LUNs per volume group.

Note It is not necessary to use LVM with multiple LUNs to fulfill the SAP HANA KPIs, but it is recommended.
Purpose Aggregate 1 at Controller A Aggregate 2 at Controller A Aggregate 1 at Controller B Aggregate 2 at Controller B

Data, log, and shared volumes for LVM based system

Data volume: SID1_data_mnt00001

Shared volume: SID1_shared
Log2 volume: SID1_log2_mnt00001

Data2 volume: SID1_data2_mnt00001

Log volume: SID1_log_mnt00001

Volume options

The volume options listed in the following table must be verified and set on all volumes used for SAP HANA.

Action ONTAP 9

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 and mapping LUNs to initiator groups using the CLI

This section shows an example configuration using the command line with ONTAP 9 for a SAP HANA single host system with SID FC5 using LVM and two LUNs per LVM volume group:

  1. 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_mnt00001  -aggregate aggr1_2 -size 280g -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_mnt00001  -aggregate aggr1_1 -size 280g -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

  2. 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_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

  3. Create the initiator group for all ports belonging to sythe hosts of FC5.

    lun igroup create -igroup HANA-FC5 -protocol fcp -ostype linux -initiator 10000090fadcc5fa,10000090fadcc5fb -vserver hana

  4. 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_log_mnt00001/FC5_log_mnt00001  -igroup HANA-FC5
lun map -path /vol/FC5_log2_mnt00001/FC5_log2_mnt00001  -igroup HANA-FC5