SUSE_Linux_Enterprise_Server_15_x_for_SAP_Applications_Configuration_Guide_for_SAP_HANA_en

/dev/mapper/3600507680185000d38000000000004de hn1sharedvg lvm2 a-- 128,00g 0
/dev/mapper/3600507680185000d38000000000004df hn1logvg lvm2 a-- 16,00g 0
/dev/mapper/3600507680185000d38000000000004e0 hn1logvg lvm2 a-- 16,00g 0
/dev/mapper/3600507680185000d38000000000004e1 hn1logvg lvm2 a-- 16,00g 0
/dev/mapper/3600507680185000d38000000000004e2 hn1logvg lvm2 a-- 16,00g 0
/dev/mapper/3600507680185000d38000000000004e3 hn1datavg lvm2 a-- 64,00g 0
/dev/mapper/3600507680185000d38000000000004e4 hn1datavg lvm2 a-- 64,00g 0
/dev/mapper/3600507680185000d38000000000004e5 hn1datavg lvm2 a-- 64,00g 0
/dev/mapper/3600507680185000d38000000000004e6 hn1datavg lvm2 a-- 64,00g 0
/dev/mapper/3600507680185000d38000000000004e7 hn1bkupvg lvm2 a-- 192,00g 0
/dev/mapper/3600507680185000d380000000000053e_part2 system lvm2 a-- 63,80g
15,80g
●
Next step is to create the striped logical volumes that will be used for the SAP HANA file system. In this
sample, you create a log volume with 64 GB space striped over four disks (-i 4) with a stripe size of 256
K. Once again make sure that you use the /dev/mapper/wwid designation for the physical volumes.
The LVM uses “-“ to separate the logical volume name from the volume group name. It is best practice not
to use this separator inside names:
# lvcreate -i 4 -I 256 -L 64G hn1logvg -n hn1log
/dev/mapper/3600507680185000d38000000000004df
/dev/mapper/3600507680185000d38000000000004e0
/dev/mapper/3600507680185000d38000000000004e1
/dev/mapper/3600507680185000d38000000000004e1
Logical volume "hn1log" created
●
Use the lvcreate command to create the other required logical volumes. The following shows the list of
logical volumes on the sample test system:
# lvs
LV VG Attr LSize Pool Origin Data% Move Log Copy%
Convert
hn1bkup hn1bkupvg -wi-ao--- 192,00g
hn1data hn1datavg -wi-ao--- 255,98g
hn1log hn1logvg -wi-ao--- 63,98g
hn1shared hn1sharedvg -wi-ao--- 64,00g
usr_sap hn1sharedvg -wi-ao--- 64,00g
home system -wi-ao--- 16,00g
root system -wi-ao--- 60,00g
swap system -wi-ao--- 2,00g
●
Finally configure the multipath.conf file. A correct configuration ensures to seamlessly protect from a
mentionable amount of failure in the stack transparently. The use of aliases helps within a single server to
identify the disks. However using automated management, handling aliases can become cumbersome
depending on the product used.
Here a sample /etc/multipath.conf:
defaults {
verbosity 2
polling_interval 5
max_polling_interval 20
reassign_maps "no"
multipath_dir "/lib64/multipath"
path_selector "round-robin 0"
path_grouping_policy "failover"
prio "const"
prio_args ""
features "0"
path_checker "directio"
alias_prefix "mpath"
failback "manual"
# rr_min_io 1000 # only for systems running kernels older that 2.6.31.
Newer systems should use rr_min_io_rq
38 P U B L I C
SUSE Linux Enterprise Server 15.x for SAP Applications Configuration Guide for SAP HANA
Sample Installation of SLES 15 for SAP Applications