SUSE_Linux_Enterprise_Server_15_x_for_SAP_Applications_Configuration_Guide_for_SAP_HANA_en
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
LVM striping is used to optimize the I/O performance to SAP HANA file systems. Consider the following
recommendations:
●
●
●
When increasing the number of ports, the minimum number of LUNs should be equal or a multiple of the
number of active paths.
When increasing the number of LUNs, they should be a multiple of the number of active paths.
The number of lv stripes should match the number of LUNs.
● We recommend a stripe size of 256 K.
●
●
Create the required LUNs on the storage subsystem and map them to the server partition. This also
assumes that the appropriate SAP Ariba Network zoning in the SAN switches has been performed.
Use the rescan-scsi-bus.sh to scan and detect the new storage LUNs without rebooting the system
# rescan-scsi-bus.sh
Scanning SCSI subsystem for new devices
Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
[....]
●
The multipath -ll command can be used to display the new devices and check the available paths. The
following command shows the sample output for a single LUN of an SAP Ariba Network Volume Controller
storage subsystem using four active and four passive paths (passive paths are paths with a lower priority
and only used if the corresponding higher priority paths fail, for example if one of the SVC nodes is
rebooted):
# multipath -ll 3600507640081811fe8000000000014a4
3600507640081811fe8000000000014a4 dm-0 IBM,2145
size=64G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 2:0:1:0 sdd 8:48 active ready running
| |- 1:0:1:0 sdh 8:112 active ready running
| |- 4:0:1:0 sdg 8:96 active ready running
| `- 3:0:1:0 sdf 8:80 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
|- 2:0:0:0 sdb 8:16 active ready running
|- 3:0:0:0 sdc 8:32 active ready running
|- 4:0:0:0 sde 8:64 active ready running
`- 1:0:0:0 sda 8:0 active ready running
●
The next step is to initialize the new volumes for use by LVM:
# pvcreate /dev/mapper/3600507680185000d38000000000004b9
Physical volume "/dev/mapper/3600507680185000d38000000000004b9" successfully
created
●
Assuming you have created four active paths to the storage subsystem and you have created four physical
volumes for use with LVM, you can now create a volume group for the SAP HANA log files (make sure that
you use the /dev/mapper/wwid device names (or use an alternative method) and not any other device
names if available):
# vgcreate hn1logvg /dev/mapper/3600507680185000d38000000000004df
/dev/mapper/3600507680185000d38000000000004e0
/dev/mapper/3600507680185000d38000000000004e1
/dev/mapper/3600507680185000d38000000000004e2
Volume group "hn1logvg" successfully created
●
Create the physical volumes and volume groups for the other SAP HANA file systems as well. The following
shows a sample configuration for a small test system:
# pvs
PV VG Fmt Attr PSize PFree
SUSE Linux Enterprise Server 15.x for SAP Applications Configuration Guide for SAP HANA
Sample Installation of SLES 15 for SAP Applications P U B L I C 37