Suse linux enterprise_server_15_x_for_sap_applications_configuration_guide_for_sap_hana_en

PUBLIC
SAP HANA Platform
Document Version: 1.0 – 2019-05-28
SUSE Linux Enterprise Server 15.x for SAP
Applications Configuration Guide for SAP HANA
x86_64 and POWER Architectures
©
2019
SAP
SE
or
an
SAP
affiliate
company.
All
rights
reserved.
THE BEST RUN

Content
1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2.2 Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Further Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Sample Installation of SLES 15 for SAP Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Installation on Intel-based Platform (x86_64). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Installation on Power-based Platform (ppc64le). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Partitioning Layout for OS root file-system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Partitioning Layout for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Sample Partition Layout for /, /usr/sap and swap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3 Clock and Time Zone Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.4 Password for the System Administrator “root”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.5 Software selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.6 Initial Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Change the Hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adapt the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Set up Logging and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Enter Performance Settings for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Updates and Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.7 Create the Partitions for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Example Multipath Disk Attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Example Internal Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.8 Create filesystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
File System for SAP HANA log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
File system for SAP HANA shared. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
File system for SAP HANA data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
File system for /usr/sap/. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9 Create Mount Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.10 Tweak the Default System Settings for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4 SAP HANA Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2 P U B L I C
SUSE Linux Enterprise Server 15.x for SAP Applications Configuration Guide for SAP HANA
Content

5 Installation of Additional Software on SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1 High Availability Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2 Antivirus Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.3 Backup Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6 Automated Installation with AutoYast2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7 Tips for Remote Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.1 Package List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
8.2 Networking ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.3 Configure a PXE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.4 Installation in a Virtual Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Content P U B L I C 3

1 About this Document
This guide serves as a supplement to the existing documentation of SAP and the hardware vendors to provide
specific guidance on how to configure SUSE Linux Enterprise Server for SAP Applications (SLES for SAP
Applications) to be used with SAP HANA. This guide does not replace any existing SAP HANA documentation
and sizing guides. Furthermore, it does not replace any SAP HANA hardware vendor documentation.
4 P U B L I C
About this Document

2 Prerequisites
Before you begin with the installation of SAP HANA, ensure that you have fulfilled the prerequisites listed in the
following sections.
SAP HANA offers two distinct deployment models, a complete pre-installed and pre-configured (so called
“Appliance”) model from hardware vendors or the tailored data center integration (TDI) where the customer
takes responsibility for the construction and validation of their SAP HANA environment but by that providing a
better integration into their IT infrastructures.
This guide does not describe all valid variants to deploy SAP HANA. It describes the base configurations along
with the minimum requirements. The topics are discussed based on a sample SUSE OS installation for SAP
HANA.
2.1 Hardware
Your hardware platform must be validated for SAP HANA independent which delivery approach you may use.
For a list of validated Intel hardware platforms, see SAP Certified and Supported SAP HANA Hardware Directory
Certified Appliances and Supported Intel Systems .
For a list of valid partition sizes inside IBM Power Servers, see SAP Certified and Supported SAP HANA
Hardware Directory Supported Power Systems and SAP Note 2188482 - SAP HANA on IBM Power Systems:
Allowed Hardware .
2.2 Storage
The appliance hardware vendors provide storage within their pre-build SAP HANA systems.
If you want to use the TDI approach, SAP HANA requires an SAP HANA TDI certified storage subsystem. For a
list of valid Storage Subsystems (TDI only), see SAP Certified and Supported SAP HANA Hardware Directory
Certified Enterprise Storage . You need to apply the file system layout / partitioning which is outlined in the
SAP HANA Server Installation and Update Guide and the SAP HANA TDI – Storage Requirements Guide .
Also download the storage vendor's TDI documentation.
This document describes a standard filesystem setup. Cross check the most recent vendor TDI storage
documentation. In case of scale-out installation including SAP HANA Host Auto-Failover also review the SAP
HANA TDI – Storage Requirements Guide .
Ensure to pick the right chapters and clearly distinguish between shared file system-based installations (e.g.
NFS or Spectrum Scale) and shared disk based installation (e.g. XFS) in case of a scale-out installation if SAP
HANA Host Auto-Failover protection is implemented.
Prerequisites P U B L I C 5

The mount points used for this sample deployment do apply for scale-up deployments and for shared file
system deployments. For shared disk deployments the mount points are documented in SAP HANA Host Auto-
Failover (basically /hana/data/mntxxxx etc.).
For further details and mount points for shared disk deployments the following documentation gives the
required guidance:
● SAP HANA Server Installation and Update Guide
● The hardware vendor’s documentation
● SAP HANA TDI – Storage Requirements Guide
● SAP Note 1900823 – Storage Connector API
● SAP HANA Host Auto-Failover
Mount Point Description Minimal Size
/ root filesystem for OS 60 GiB
/usr/sap System instances 50 GiB
/hana/shared Installation path SAP HANA TDI – Storage Require
ments Guide
/hana/data Data volume The SAP Sizing report will define the
disk size. For Greenfield deployments
use the SAP HANA TDI – Storage Re
quirements Guide
/hana/log Log volume The SAP Sizing report will define the
disk size. For Greenfield deployments
use the SAP HANA TDI – Storage Re
quirements Guide
2.3 Software
The following software was used for the sample installation:
● ISO image SUSE Linux Enterprise 15 (SLE-15-Installer-DVD-x86_64-GM-DVD1.iso + SLE-15-Packages-
x86_64-GM-DVD1.iso).
● Required registration key for the SUSE subscriptions in order to get SUSE maintenance updates.
● SAP HANA media and temporary license in order to install SAP HANA.
● The minimum version of the SUSE Linux Enterprise Server for SAP Applications software is linked to the
SAP HANA software version. Verify the minimum requirement based on the SAP HANA documentation
(SAP Note 2235581 - SAP HANA: Supported Operating Systems ).
6 P U B L I C
Prerequisites

2.4 Further Information
You must have the following information about the host on which you intend to perform the installation:
● IP address of the host
● IP alias for SAP HANA (optional)
● Host name of the host
● Subnet mask
● Domain name
● IP address of the name servers
● Address of a time server (ntp / chrony)
● Gateway IP address
● Proxy IP address and credential (optional)
● Password for the root user and credential (optional)
● SAP master password (<sid>adm and sapadm password)
● SID and instance for the SAP HANA installation
● UID for the linux user of the system database
● GID for linux group of the SAP Host Agent
Prerequisites P U B L I C 7

3 Sample Installation of SLES 15 for SAP
Applications
SUSE Linux comes per default with the YaST2 installation tool. YaST2 can run in a graphical environment as
well in a text based (ncurses) environment.
● For x86_64 hardware:
Download the SUSE® Linux Enterprise 15 Installer DVD iso image (DVD1).
● For ppc64le hardware:
Download the SUSE® Linux Enterprise 15 Installer DVD iso image (DVD1).
Required Downloads
The following downloads are required for each architecture you would like to install on:
● Regular Installation (with Internet access):
DVD1 of the installer medium
● Offline Installation (without internet access):
○ DVD1 of the installer medium
○ DVD1 of the packages medium
All other images are optional and not required for the installation.
3.1 Installation
The installation workflow for x86_64 and ppc64le differs at the beginning until the YaST installation Wizards is
running.
The steps are:
● Power on and boot from the Installer media
● Updating the Installer (if internet connection is available)
● Language, Keyboard and Product Selection
○ Choose English as language.
○ Choose SUSE Linux Enterprise Server for SAP Applications 15.
● Agree with the License Terms.
● Register your system via SCC or SMT / RMT.
● Enable updates if the message appears.
● Additionally select the Legacy Module 15 from the Extension and Module Selection page.
● Choose SLES for SAP Applications from the System Role page.
8 P U B L I C
Sample Installation of SLES 15 for SAP Applications

● Modify the RDP and SAP Installation Wizard option to your needs.
● Normally you can accept the suggested partitioning, otherwise choose Guided Setup or Expert Partitioner.
● Set date and time.
● Define a root password.
● Adapt the software selection and add the package libopenssl1_0_0.
● Accept the automatic changes.
● Modify the ssh and firewall settings to your needs.
● Modify the default systemd target. We recommend Text mode.
3.1.1 Installation on Intel-based Platform (x86_64)
Boot your machine from the SUSE Linux Enterprise media. On machines with a traditional BIOS, you see the
graphical boot screen shown below. On machines equipped with UEFI, or POWER architecture a slightly
different boot screen is used. Secure boot on UEFI machines is supported.
1.
Choose Installation on the boot screen, then press Enter. This boots the system and loads the SUSE Linux
Enterprise Server installer.
For more information about the other choices, see the SUSE Linux Enterprise Server for SAP Applications
documentation.
Sample Installation of SLES 15 for SAP Applications P U B L I C 9

The Installer will receive updates if possible.
2.
10 P U B L I C

The Language and Keyboard Layout are initialized with the language settings you have chosen on the boot
screen. Change them here, if necessary. Choose the product SUSE Linux Enterprise Server for SAP
Applications 15.
3.
Read the License Agreement. It is presented in the language you have chosen on the boot screen. License
translations are available. You need to accept the agreement by checking I Agree to the License Terms to
install SUSE Linux Enterprise Server for SAP Applications 15. Proceed with Next.
After booting into the installation, the installation routine is set up. During this setup, an attempt to
configure at least one network interface with DHCP is made. In case this attempt fails, the Network Settings
dialog launches.

4.
Choose a network interface from the list and click Edit to change its settings. Use the tabs to configure DNS
and routing.
12 P U B L I C

5.
When you are done with the network settings, choose Next to proceed or return to the Registration screen.
After at least one network interface has been configured you can register your system at the SUSE
Customer Center (SCC).

6.
Enter the e-mail address associated with your SCC account and the registration code for SUSE Linux
Enterprise Server. A successful registration is a prerequisite for getting product updates and being entitled
to technical support. This is in addition necessary to get the additional module channels.
In case of an offline installation the Packages DVD is needed. After the installation register your system
against either SCC / SMT / RMT or SUSE Manager to be able to receive updates.
14 P U B L I C

7.
If SUSE Linux Enterprise Server for SAP Applications has been successfully registered at the SUSE
Customer Center, you are asked whether to install the latest available online updates during the
installation. If choosing Yes, the system will be installed with the most current packages without having to
apply the updates after installation. Activating this option is recommended.
If you have successfully registered your system in the previous step, a list of available modules and
extensions based on SUSE Linux Enterprise Server is shown.

8.
Add the Legacy Module in order to be able to install for example libopenssl1_0_0.
Other interesting modules you may need, depending on your usage of the system, are:
○ SUSE Linux Enterprise Live Patching 15 (adds support for performing critical patching)
○ Development Tools Module 15 (contains compilers like gcc)
○ If you use SAP HANA in the public clouds, the Public Cloud Module 15
Choose Next to proceed with the installation workflow.
16 P U B L I C

9.
After all extensions and modules are registered the next step is available. The installation of Add On
Product’s can be prepared if needed.
Proceed with Next.

10.
Choose Next for the System Role selection.
18 P U B L I C

11.
Choose the default SLES for SAP Applications and choose Next. This option is the preferred and the
recommended installation.

12.
Deselect the two options, if they are not needed later and go continue with Next.
3.1.2 Installation on Power-based Platform (ppc64le)
Boot the LPAR by adding the iso image into the media Library of your VIOS Server. All subsequent LPARs are
easy to deploy based on images using PowerVC, Novalink or CAMS. The following steps describe how to add a
media into the VIOS.
This is identical across common VIOS versions. A detailed documentation can be found here: http:/
/
www.redbooks.ibm.com/redbooks/pdfs/sg247940.pdf
3.2 Partitioning
Independently from the disk space type (attached by a TDI approach, internal Disks, or shared file system) this
section summarizes the requirements for the partition layout.
Depending on the pre sets of the hardware vendor, the SAP HANA installation (scale-up, scale-out, SAP HANA
System Replication, ...), SLAs the partitioning layout looks differently.
20 P U B L I C

3.2.1 Partitioning Layout for OS root file-system
The partition holding the root filesystem should have at least a size of 60 GB in order to be able to store
snapshots and log messages over a period of time.
The default file system for the root file system in SLES 15 for SAP Applications is btrfs and should not be
changed in order to benefit from the zero downtime approach of SLE15.
In contrast to SAP Note 1597355 - Swap-space recommendation for Linux (which is mainly for SAP
NetWeaver) you should configure a smaller size for swap space, for example 2 GiB.
3.2.2 Partitioning Layout for SAP HANA
For a scale-up SAP HANA single-host system three file systems are required, which need to be reflected in the
partition layout. There is one file system for each of the following files:
● SAP HANA executables
● SAP HANA data
● SAP HANA log
There are two options available by today:
● Certified appliances
● TDI (Tailored Datacenter Integration) certified storage
The SAP HANA data and log file system must meet the performance KPIs for SAP HANA HWCCT tool (see SAP
Note 1943937 - Hardware Configuration Check Tool - Central Note ) and must reside on TDI certified storage
systems.
It is recommended to provide at least 10 GiB for the /usr/sap location in the system. SAP HANA and other
SAP software that supports SAP HANA stores data in this directory per default. The SAP HANA software is
installed into /hana/shared. In scale-out installations, the directory should be a shared file system.
For more information, see Create the Partitions for SAP HANA [page 35] in this guide.
3.2.3 Sample Partition Layout for /, /usr/sap and swap
In this example we use a separate file system for /usr/sap. This means we need at least 112 GiB (60 GiB+50 GiB
+2 GiB) for the OS drive and /usr/sap mount point without SLA (service-level agreement) considerations such
as mirroring. For SAP HANA shared, SAP HANA data and SAP HANA log separate disks will be used.

1. The suggested Partitioning could look like this:
2. You can modify the proposed partitioning layout with these methods:
○ Guided Setup
○ Expert Partitioner
It is possible to define directly the dedicated /usr/sap partition at this point. Depending on your disk
layout the steps may differ from this example. For this example the following steps were performed.
1. Choose Expert Partitioner Start with current Proposal
2. Select the 2nd disk.
3. Add a partition with Mount Point /usr/sap
4. Choose xfs as filesystem.
5. Accept the changes.
22 P U B L I C

This result in a partition layout like this:

3.3 Clock and Time Zone Selection
1.
Select the clock and time zone to use in your system.
2. To adjust the time manually or to configure an NTP server for time synchronization, choose Other Settings.
 Note
For Power-based platforms, see Time Synchronization with NTP in the SLES 15 Administration
Guide .
3. Proceed with Next.
In this example, we use the german pool of public NTP-Servers in Germany.
24 P U B L I C

3.4 Password for the System Administrator “root”
1. Type a password for the system administrator account (called root) and repeat the password under
Confirm Password.
Use the text box Test Keyboard Layout to make sure that all special characters appear correctly.
For more information, see Password for the System Administrator root .
2. Proceed with Next.
 Caution
IMPORTANT: Do Not Forget the root Password!
The user root has the permission to carry out all administrative tasks. Without this password, you cannot
log in to the system as root.
After you have entered the root password here, it cannot be retrieved again.
26 P U B L I C

3.5 Software selection
1.
On the screen Installation Settings, you can review and, if necessary, change several proposed installation
settings. Each setting is shown alongside its current configuration. To change parts of the configuration,
choose the appropriate headline or other underlined items. It is also possible to navigate without the
mouse using the TAB key and ENTER.
Firewall Configuration and SSH
Firewall and SSH The software firewall of SLES for SAP is enabled by default. However, often, the ports your
SAP product requires to be open are not opened automatically. There may be network issues until you
open the required ports manually. In addition, you might also need to enable the SSH service and port.
Kdump
Kdump is disabled in our example. Choose Kdump, then disable. Choose Next to return to the screen
Installation Settings. Consult your hardware partner recommendations regarding the Kdump settings. Keep
in mind to adjust the size of your filesystem capacity and or the settings for Kdump where the dumps are
saved. Depending on the amount of RAM, you need the corresponding disk space somewhere for saving
the files.
For information, see KDUMP and FADUMP .
Default systemd target
If the graphical environment is not mandatory needed for your purpose, we suggest changing the mode to
Text mode.

2.
For SAP HANA, we must change the default software selection. Choose Software.
28 P U B L I C

3.
If you choose Details, you see a more granular package / patterns selection. Check the Security and
Hardening Guide for SAP HANA to reduce the footprint of the default installation.
For SAP HANA, we must install the libopenssl1_0_0 and libssh2-1 package. Choose Search and
select the package after it is shown in the right column. Accept the package selection and click Continue to
perform the automatic changes.

4.
When you are satisfied with the system configuration, Choose Install to start the installation.
Depending on your software selection, you probably must agree to further license agreements before you
are asked to confirm that you want to start the installation process.
30 P U B L I C

5.
 Caution
WARNING: Deletion of Data
Starting the installation process means that information on the disk you are installing on is fully or
partly deleted.

In the installation confirmation box, choose Install. Now the installation is performed:
32 P U B L I C

6.
Depending on the settings, the logon screen looks different as in this example.
3.6 Initial Setup
The system is now ready for the first login and can be modified to fit into the existing IT infrastructure. Check
and modify the following settings to your company rules. There are multiple ways to configure the system.
Below we will mostly use the command line. The official documentation can be found here: https:/
/
www.suse.com/documentation/sles-15/singlehtml/book_sle_admin/
book_sle_admin.html#sec.network.nameres
You perform the following steps:
● Change the Hostname (IP, DNS, gateway, NTP, firewall)
● Adapt the Network
● Set up Logging and Monitoring
● Enter Performance Settings for SAP HANA
● Updates and Patches (patches, subscription)

3.6.1 Change the Hostname
Change the hostname with the following commands:
# yast dns edit hostname=<xxxxx>
# yast dns edit nameserver1=<IP address>
3.6.2 Adapt the Network
Manual configuration of the network software should be the last alternative. Using YaST is recommended.
# yast lan
Do not forget to verify the settings on all pages (Global Options | Overview | Hostname/DNS | Routing).
Overview is the landing page.
For scripting you may use commands like the following:
# yast lan edit id=0 bootproto=static ip=<ip address> netmask=<netmask>
Display the network devices and their configuration:
# yast lan list
Display the network summary:
# wicked show all
3.6.3 Set up Logging and Monitoring
With SLES for SAP Applications, the default syslog implementation is done by the traditional rsyslog.
Journal is backward compatible with rsyslog and can be enabled to forward all events to rsyslog. Another
way would be to make the journal persistent.
Linux comes with several tools for system analysis and monitoring. See the System Analysis and Tuning Guide
chapter System Monitoring Utilities for a selection of the most important ones used in system
diagnostics.
34 P U B L I C

3.6.4 Enter Performance Settings for SAP HANA
The system tuning application saptune allows you to tune your system automatically and comprehensively as
recommended by SAP. The following SAP Note contains a detailed description: SAP Note 1275776 - Linux:
Preparing SLES for SAP environments .
# saptune solution apply HANA
For more information, see Tweak the Default System Settings for SAP HANA [page 45].
3.6.5 Updates and Patches
If you have not used the update option during the deployment or your system was registered later on, make
sure to get the newest updates in order to have the latest versions of the resource agents and other packages.
A prerequisite is a valid subscription for SAP Applications. There are multiple ways to get updates like SUSE
Manager, SMT / RMT or directly connected to SAP DB Control Center (SUSE Costumer Center).
Depending on your company or customer rules, use zypper update or zypper patch.
A manual software update must be triggered from each node.
zypper patch installs all available needed patches.
# zypper patch
zypper update updates all or specified installed packages with newer versions, if possible.
# zypper update
3.7 Create the Partitions for SAP HANA
Look at the disks and partitions of SAP HANA itself. Where the size of the partitions depends on the amount of
main memory (SAP Sizing), the size can vary based on backup/snapshot configuration, and the desired SLAs.
In the SAP HANA TDI – Storage Requirements Guide , you find the following statements:
● The I/O performance requirements that have to be fulfilled by the storage subsystem mainly rely on the
scenario or the SAP HANA database.
● The filesystem must be compliant with the SAP documentation (dominant are XFS, NFS4 and Spectrum
Scale/GPFS).
● Storage systems used for SAP HANA must fulfill a certain set of KPIs for minimum data throughput and
maximum latency time. In the course of both the SAP HANA appliance and the SAP HANA Enterprise
Storage certification the fulfillment of those KPIs is checked using the SAP HANA Hardware Configuration
Check Tool (HWCCT). All KPIs must be met for each SAP HANA compute node connected to a given
storage system. Each individual deployment must be revalidated.

● Note: Just fulfilling the KPIs does not mean that the I/O capabilities are sufficient for all workloads!
Therefore we cannot provide a detailed setup of a production system within this document, but we will show
the general way and what to do for two scenarios, a multipath example with an SAP Ariba Network attached
storage and a scenario with local disks.
Each hardware partner with a certified storage system or appliance will have a dedicated documentation for
their own specific setup to reach the SAP HANA KPIs.
For more flexibility to change the size and number of drives these volumes should be created as logical volumes
using the logical volume manager (LVM).
An LVM volume group organizes the Linux LVM partitions into a logical pool of space. You can carve out logical
volumes from the available space in the group. The Linux LVM partitions in a group can be on the same or
different disks. You can add LVM partitions from the same or different disks to expand the size of the group.
You can use the YaST2 Expert Partitioner to create and manage file systems and RAID devices. For more
information, see Expert Partitioner in the SUSE Linux Enterprise Server 15 Deployment Guide for the used
service pack.
Depending on the disk attachment and storage solution (for example internal disks or SAN), the preparation
involves different tasks.
In the following sections, multipath and internal disk options are described. The mount point and file system
creation are the same for both. Depending on the server vendor, different file systems are supported to operate
SAP HANA. The example in the following sections is focusing on XFS only, which is the default of additional
partitions to be created.
3.7.1 Example Multipath Disk Attachment
To create an XFS file system in a multipath environment, the following tasks have to be performed. Ensure to
match sizes, names, and so on, to the individual SAP HANA deployment.
Tuning LVM File System settings and Disk Layout for Multipathing
Using XFS with multipathing and LVM striping provides options to optimize the I/O performance. This section
explains how fiber channel connectivity, zoning and multipathing affect the LUN layout planning.
To optimize the usage of all available I/O paths for better performance, we recommend that the logical volumes
of the SAP HANA log, data, and shared file systems should be striped over a number of LUNs that are a
multiple of the active paths (for example four active paths, logical volumes should be striped over a minimum
of four LUNs).
 Note
The minimum number of paths, volumes, and disks determined in the sizing process is the absolute
minimum, even if in the following planning process less might be sufficient.
Prefer to use storage-based redundancy over LVM options, to make support, management, and operations
much easier. One example is IBM Spectrum Virtualize (SVC) providing to the OS an already mirrored and
striped single device.
36 P U B L I C

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

/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/3600507680185000d38000000000004e3 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

rr_min_io_rq 1
max_fds "max"
rr_weight "uniform"
queue_without_daemon "no"
flush_on_last_del "no"
# when using aliases instead wwpn set user_friendly_names to yes and
add list of wwpn aliases into multipath.conf
user_friendly_names "no"
fast_io_fail_tmo 5
bindings_file "/etc/multipath/bindings"
wwids_file /etc/multipath/wwids
log_checker_err always
retain_attached_hw_handler no
detect_prio no
force_sync no
strict_timing no
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^(td|hd)[a-z]"
devnode "^dcssblk[0-9]*"
devnode "^nvme.*"
device {
vendor "IBM"
product "Universal Xport"
}
device {
vendor "(NETAPP|LSI|ENGENIO)"
product "Universal Xport"
}
}
blacklist_exceptions {
property "(SCSI_IDENT_.*|ID_WWN)"
}
device {
#IBM Spectrum Virtualize (SVC)
##########################
vendor "IBM"
product "2145"
path_grouping_policy "group_by_prio"
prio "alua"
path_checker "tur"
failback "immediate"
#no queueing especially for scale-out Auto Host Failover
environments enable no_path_retry = fail to not hinder the take over
no_path_retry "fail"
#bigger values rr_min_io_rq >32 can improve throughput, at
the same time deeper queues have a bigger impakt on failure recovery. in this
case also consider to increas:
# Increase the queue depth of devices/(e.g. echo 64 >
cat /sys/bus/scsi/devices/<device>/queue_depth)
# Increase /sys/block/<device>/queue/nr_requests if the
default (128) results in blocked I/O submission. This will indirectly help to
optimize the blocking inside SAP HANA.
rr_min_io_rq 16
#tmo values handle takover when paths/devices fail
fast_io_fail_tmo is related to dev_loss_tmo and queue_if_no_path
dev_loss_tmo 120
fast_io_fail_tmo 5
# service time 0 is latency optimization
path_selector "service-time 0"
}
}
● After configuring the multipath, verify the bootlist. Show the existing bootlist:
bootlist -m normal -o
sdat

# bootlist -m normal -r
/vdevice/vfc-client@30000002/disk@500507680c326db2
● Find the rootdevice:
pvs | grep system
PV VG Fmt Attr
PSize PFree
/dev/mapper/360050768018087c52000000000000d68-part2 system lvm2 a--
49.99g 4.00m
/dev/mapper/360050768018087c52000000000000d6f hn_lg_vg lvm2 a--
32.00g 0
# bootlist -m normal -o sdat sdet sddb
sdat
sddv
sddb
● Identify paths available to the rootdevice using multipath -ll:
# multipath -ll
360050768018087c52000000000000d6f dm-2 IBM,2145
| |- 1:0:0:3 sdc 8:32 active ready running
| |- 1:0:12:3 sddg 70:224 active ready running
| |- 1:0:4:3 sdaf 65:240 active ready running
| |- 1:0:8:3 sdbt 68:112 active ready running
| |- 2:0:0:3 sds 65:32 active ready running
| |- 2:0:12:3 sdej 128:176 active ready running
| |- 2:0:4:3 sdbg 67:160 active ready running
| `- 2:0:8:3 sdcv 70:48 active ready running
|- 1:0:10:3 sdcm 69:160 active ready running
|- 1:0:14:3 sdea 128:32 active ready running
|- 1:0:2:3 sdm 8:192 active ready running
|- 1:0:6:3 sdaz 67:48 active ready running
|- 2:0:10:3 sddo 71:96 active ready running
|- 2:0:14:3 sdew 129:128 active ready running
|- 2:0:2:3 sdam 66:96 active ready running
`- 2:0:6:3 sdcb 68:240 active ready running
360050768018087c52000000000000d68 dm-9 IBM,2145
| |- 1:0:1:0 sdj 8:144 active ready running
| |- 1:0:13:0 sddv 71:208 active ready running
| |- 1:0:5:0 sdat 66:208 active ready running
| |- 1:0:9:0 sdcg 69:64 active ready running
| |- 2:0:1:0 sdag 66:0 active ready running
| |- 2:0:13:0 sdet 129:80 active ready running
| |- 2:0:5:0 sdbv 68:144 active ready running
| `- 2:0:9:0 sddi 71:0 active ready running
|- 1:0:11:0 sddb 70:144 active ready running
|- 1:0:15:0 sdeo 129:0 active ready running
|- 1:0:3:0 sdz 65:144 active ready running
|- 1:0:7:0 sdbn 68:16 active ready running
|- 2:0:11:0 sded 128:80 active ready running
|- 2:0:15:0 sdfd 129:240 active ready running
|- 2:0:3:0 sdba 67:64 active ready running
`- 2:0:7:0 sdcp 69:208 active ready running
40 P U B L I C

● Localize available path and add redundancy if necessary:
360050768018087c52000000000000d68 dm-9 IBM,2145
| |- 1:0:1:0 sdj 8:144 active ready running
| |- 1:0:13:0 sddv 71:208 active ready running
| |- 1:0:5:0 sdat 66:208 active ready running
| |- 1:0:9:0 sdcg 69:64 active ready running
| |- 2:0:1:0 sdag 66:0 active ready running
| |- 2:0:13:0 sdet 129:80 active ready running
| |- 2:0:5:0 sdbv 68:144 active ready running
| `- 2:0:9:0 sddi 71:0 active ready running
|- 1:0:11:0 sddb 70:144 active ready running
|- 1:0:15:0 sdeo 129:0 active ready running
|- 1:0:3:0 sdz 65:144 active ready running
|- 1:0:7:0 sdbn 68:16 active ready running
|- 2:0:11:0 sded 128:80 active ready running
|- 2:0:15:0 sdfd 129:240 active ready running
|- 2:0:3:0 sdba 67:64 active ready running
`- 2:0:7:0 sdcp 69:208 active ready running
# bootlist -m normal -o sdat sdet sddb
sdat
sddv
sddb
3.7.2 Example Internal Disks
The following example shows how to use the command-line interface for the storage setup. You can also
perform these tasks using YaST2.
This example with internal disks, should be backed by a RAID 5 array which provides three disks to the OS. The
RAID setup depends on the hardware vendor machine type and disk drives been used and should provide
enough spindles to fulfill the SAP HANA requirements.
Check for Empty Devices
Enter the following command:
# lsblk -f
In our example, we have these drives:
/dev/sda 160 GiB
/dev/sdb 300 GiB
/dev/sdc 100 GiB
In this case /dev/sda is used for the OS (as the initial section has shown).

Create a Disk Partition Table
The disks /dev/sdb and /dev/sdc are the free devices for the SAP HANA data volumes and SAP HANA log
volumes. First create the partition table and afterwards create your partitions. Finally change the partition type
to Linux LVM.
If you have less than 2-TB free space on the disk, use fdisk:
# fdisk /dev/sdb
# g (create a new empty GPT partition table)
# n (create new partition)
# t (change partition type)
# w (write table to disk and exit)
If you have disks larger than 2-TB, UEFI Secure Boot enabled or more than four primary partitions, use the
command parted and the GPT label:
# parted /dev/sdb mklabel gpt
# parted /dev/sdb mkpart vg-hana-data 1 100%
# parted /dev/sdb set 1 lvm on
Perform the same tasks for /dev/sdc:
# parted /dev/sdc mklabel gpt
# parted /dev/sdc mkpart vg-hana-log 1 100%
# parted /dev/sdc set 1 lvm on
Create the LVM Physical Volume
pvcreate initializes a device for use by LVM as a physical volume. If there is any file system on the specified
device, a warning appears. Bear in mind that pvcreate checks for existing file systems only if blkid is
installed (which is done by default):
# pvcreate /dev/sdb1
Perform the same tasks for /dev/sdc1.
Create the LVM Volume Group
vgcreate creates a volume group, using the physical devices.
If the physical device was not previously configured for LVM with pvcreate, the device is initialized with the
same default values used for pvcreate:
# vgcreate vg00 /dev/sdb1
Add an additional volume group for the different SAP HANA volumes:
# vgcreate vg01 /dev/sdc1
42 P U B L I C

Check the New Volume Groups
The actual physical volumes can be displayed with:
# pvs
Information about volume groups can be displayed with:
# vgs
Create Logical Volumes for the SAP HANA Instance According to Your Sizing
lvcreate creates a new logical volume in an existing volume group. Depending on your storage setup you may
use different parameter to create the logical volumes. Think about stripping for example to increase the
performance. More detailed information can be found in the Storage Administration Guide for SLES 15.
The values used here, are examples. Check the SAP HANA documentation to choose the right values.
As the directory /usr/sap in our example is not shared with the operating system disk and we have enough
disk space here, we create a separate logical volume within the volume group system which was created
through YaST2 during the installation:
# lvcreate -L 50G -n lv_usr_sap system
Because we have three drives in our example, we can distribute the volumes SAP HANA data and SAP HANA
log into different volume groups and logical volumes. The SAP HANA shared volume is added to the system
volume group:
# lvcreate -L 96G -n lv_hana_shared system
# lvcreate -L 288G -n lv_hana_data vg00
# lvcreate -L 96G -n lv_hana_log vg01
For more information about sizing SAP HANA, see Sizing SAP HANA in the SAP HANA Master Guide.
3.8 Create filesystems
SUSE Linux Enterprise Server offers a variety of file systems from which to choose for different workloads. SAP
HANA needs certain criteria (files bigger than 2 GiB, fast file system with large files) which must be fulfilled. A
list of all supported filesystems can be found in the SAP Note 405827 - Linux: Recommended file systems .
In our example, we chose XFS for the file system.
The idea behind XFS was to create a high-performance 64-bit journaling file system to meet extreme
computing challenges. XFS is very good at manipulating large files and performs well on high-end hardware.
SUSE supports and includes XFS since SLES 8 as the default filesystem for partitions other than root.
More details are discussed in the SUSE Linux Enterprise Server Documentation section Storage administration
.

Many XFS tuning guides are outdated and designed for benchmarks rather than actual workloads. XFS can
determine the underlying geometry, it auto-tunes itself automatically. Linux MD, and most RAID controllers,
provide the proper information.
To create an XFS file system, use the mkfs.xfs command. The difference between multipath environments
and local disks is the default path.
3.8.1 File System for SAP HANA log
As local disk we have typically:
# mkfs -t xfs /dev/vg01/lv_hana_log
For the multipath example the command would look as follows:
# mkfs –t xfs /dev/mapper/hn1logvg-hn1log
3.8.2 File system for SAP HANA shared
Create for all logical volumes the file system, for example:
# mkfs.xfs /dev/system/lv_hana_shared
3.8.3 File system for SAP HANA data
# mkfs.xfs /dev/vg00/lv_hana_data
3.8.4 File system for /usr/sap/
# mkfs.xfs /dev/system/lv_usr_sap
44 P U B L I C

3.9 Create Mount Points
In order to use our logical volumes (independently if they were created based on internal disks or on multipath
devices), we must create mount points within the root file system.
Create the mount points:
# mkdir -p /hana/{shared,data,log}
# mkdir -p /usr/sap
The next step varies depending on your SAP HANA deployment. For a scale-up system, the file systems can be
mounted during the system boot. Edit /etc/fstab to add the mount commands or append it from the
command line to the file.
echo “/dev/system/lv_usr_sap /usr/sap xfs defaults 1 2” >> /etc/fstab
echo “/dev/system/lv_hana_shared /hana/shared xfs defaults 1 2”>> /etc/fstab
echo “/dev/vg00/lv_hana_data /hana/data xfs defaults 1 2” >> /etc/fstab
echo “/dev/vg01/lv_hana_log /hana/log xfs defaults 1 2” >> /etc/fstab
For the multipath example, adapt the names. It is mandatory to use unique and persistent identifier such as
aliases for UUIDs or the UUIDs themselves. The dm-x identifiers can change based on adding new disks,
changing paths etc.
Mount all file systems from /etc/fstab unless SAP HANA Auto Host Failover is implemented. For details see
SAP HANA Host Auto-Failover .
Mount all file systems from /etc/fstab :
# mount -av
3.10 Tweak the Default System Settings for SAP HANA
SAP HANA needs some special configuration settings in order to use all the performance the hardware offers.
The SUSE default configuration settings are not set for an SAP HANA workload, therefore you must adapt
some of the settings.
Starting with SLES4SAP12 SP2 we added the tool saptune. Check the referenced SAP Note for all last
updated settings. About the details how to use saptune check SAP Note 1275776 - Linux: Preparing SLES for
SAP environments .
To tune a system, first find a tuning profile using saptune as shown:
# saptune solution list
saptune knows the following profiles:
● SAP BusinessObjects Profile for servers hosting an SAP SAP BusinessObjects application.
● SAP HANA Profile for servers hosting an SAP HANA database.

● MAXDB Profile for servers hosting a MaxDB database.
● NETWEAVER Profile for servers hosting an SAP NetWeaver application.
● S4HANA-APPSERVER Profile for servers hosting an SAP S/4HANA application.
● S4HANA-DBSERVER Profile for servers hosting the SAP HANA database of an SAP S/4HANA installation.
● SAP-ASE Profile for servers hosting an SAP Sybase database.
Keep in mind that profile parameters can be changed over the time and profiles which have similar settings
could be combined. This process ends with fewer profiles. Also solutions can be removed, added, or combined
over time due to the ongoing development of SAP products.
Alternatively, you can tune the computer according to recommendations from specific SAP Notes. A list of
notes that you can tune for is available via:
# saptune note list
To set up saptune with the preconfigured SAP HANA settings, use:
# saptune solution apply HANA
 Tip
You can freely combine solutions and notes. Combining multiple optimizations never creates conflicts.
Finally, enable the tuned profile saptune and make sure the tuned daemon is active:
# saptune daemon start
In the background, saptune applies a tuned profile also named saptune that is customized according to
selected solutions and notes. Using tuned-adm list, you can also see this profile.
The relevant SAP Notes are:
● SAP Note 2578899 - SUSE Linux Enterprise Server 15: Installation Note
● SAP Note 1056161 - SUSE Priority Support for SAP applications
● SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System Installation
● SAP Note 2235581 - SAP HANA: Supported Operating Systems
● SAP Note 2684254 - SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications
15
● SAP Note 52505 - Support after end of mainstream/extended maintenance
● SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note
46 P U B L I C

4 SAP HANA Installation
This section provides a short overview of the installation of an SAP HANA system.
SAP HANA can be installed in several ways on different architectures. The SAP Server Installation and Update
Guide along with the guides provided by the server vendor reflect these options. Below the installation of a
single-host system is shown.
1. First download the SAP HANA installation media. If you are using the Support Packages & Patches SAP
HANA sources you need in additional the SAP archive tool (SAPCAR) from the SAP Service Marketplace.
2. Create a directory which should hold the SAP HANA installation media, for example:
# mkdir /install
3. ○ Option 1
You have a multi spaned selfextracting RAR archive (xxxxxx.EXE). Change the directory and unar the
archive.
# cd /install
# unar <path_to_the_downloaded_media>_part1.exe
○ Option 2
To have SAPCAR within the path to easily execute it, copy the SAP archiver (SAPCAR) to the personal
bin directory of the root user for example:
# cp <path_to_the_downloaded_installer>/SAPCAR_<xxxxxxxxx> ~/bin
4. Extract the SAP HANA installation media into the created /install directory, for example:
# cd /install
# SAPCAR_<xxxxxxxxx> -xvsf <path_to_the_media_archive>/<yyyyy>.sar
5. Change to the directory where the SAP HANA installation media are located to start the installation or start
the hdblcm tool from the point where you are.
6. Install the SAP HANA system by running the SAP HANA lifecycle management tool (hdblcmgui with
graphical interface, hdblcm as command line tool):
# /hana/media/51053381/DATA_UNITS/HDB_LCM_LINUX_X86_64/hdblcm
SAP HANA Installation P U B L I C 47

5 Installation of Additional Software on
SAP HANA Systems
This section describes the installation of additional software on SAP HANA systems. Check also SAP Note
1730928 - Using external software in a HANA appliance and SAP Note 1730996 - Unrecommended external
software and software versions that the external software did not cause problems in the SAP HANA
appliance.
5.1 High Availability Software
As more and more SAP HANA instances are used in production, cluster vendors have developed together with
SAP cluster solutions for SAP applications to automate the SAP HANA system replication failover.
For information about high availability for SAP HANA, see the guide Introduction: High Availability for SAP
HANA .
As of today there is no certification of high availability for SAP HANA, the high availability vendor need to
support the solution.
Related Information
SUSE Best Practices → SUSE Linux Enterprise Server for SAP
5.2 Antivirus Software
To ensure the secure operation of an SAP HANA system and to fulfill IT compliances and IT policies, you need
to use antivirus software in your SAP HANA appliance.
The SAP Note 1730930 - Using antivirus software in an SAP HANA appliance provides more information
regarding the setup and solutions.
48 P U B L I C
Installation of Additional Software on SAP HANA Systems

5.3 Backup Solutions
SAP HANA provides an API (“Backint for SAP HANA”) via which third-party backup tools can be connected.
See SAP Note 1730932 - Using backup tools with Backint for HANA for more information.
A list of BACKINT certified solutions can be found on SCN.
Besides BACKINT, SAP HANA allows other mechanisms to be used. They are typically file system or storage-
based features such as FlashCopy/snapshot technology or backup tools performing a file system backup of the
relevant data.
Installation of Additional Software on SAP HANA Systems P U B L I C 49

6 Automated Installation with AutoYast2
AutoYaST2 is used to install automatically SUSE Linux Enterprise Server.
Configuration information is stored in an XML configuration file called an Autoyast profile. The installer reads
the profile and installs the system based on the options given. Using AutoYaST2, multiple systems sharing the
same environment and similar but not necessarily identical hardware and performing similar tasks, can easily
be installed in parallel and quickly. A configuration file, referred to as AutoYaST profile, is created using existing
configuration resources. The profile file can be easily tailored for any specific environment.
The smallest and simplest Autoyast file would be this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://
www.suse.com/1.0/configns">
<users config:type="list">
<user>
<encrypted config:type="boolean">false</encrypted>
<user_password>linux</user_password>
<username>root</username>
</user>
</users>
</profile>
In order to create the control file for one or more hosts, a YaST2 module is provided. This system depends on
the existing YaST2 modules which are usually used to configure a host in regular operation mode.
For more information, see the SUSE Linux Enterprise Server Deployment Guide and the AutoYaST2
description.
50 P U B L I C
Automated Installation with AutoYast2

7 Tips for Remote Installation
SUSE Linux Enterprise Server can be installed in several different ways.
As well as the usual media installation through DVD, ISO or USB, you can choose from various network-based
approaches like NFS, FTP, HTTP, CIFS/SMB together with VNC or SSH or even take a completely hands-off
approach (AutoYaST2) to the installation of SUSE Linux Enterprise.
For more information, see the SUSE Linux Enterprise Server Deployment Guide .
Tips for Remote Installation P U B L I C 51

8 Appendix
The appendix provides additional information.
8.1 Package List
Check the recommended package list for SAP HANA.
SAP recommends the installation of the SLES 15 base pattern as the basis to run a SAP HANA system on. To
guarantee optimal performance and the highest stability, SAP appliance hardware and technology partners
may deliver SAP HANA systems with settings that deviate from that standard. Customers and partners are
advised to document all changes to the standard pattern so that SAP support can more efficiently identify the
root cause of problems.
Required packages, not included in SLES for SAP Applications 15 default selection:
● libssh2-1
● libopenssl1_0_0 (from SLE-Module-Legacy15)
8.2 Networking ports
For information about networking ports, see the SAP HANA Security Guide.
8.3 Configure a PXE Server
When using a PXE boot server in conjunction with, AutoYaST you can have a fully automated installation of
SUSE Enterprise Linux.
For more information, see Remote Installation in the SUSE Linux Enterprise Server Deployment Guide .
8.4 Installation in a Virtual Machine
SAP HANA can be installed on bare metal or based on certified virtualization.
52 P U B L I C
Appendix

The following SAP Notes are relevant for PowerVM:
● SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host
● SAP Note 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware
Have a look at the best practice documents from VMware and the VMware relevant SAP Notes:
● SAP Note 2161991 - VMware vSphere configuration guidelines
● SAP Note 2315348 - SAP HANA on VMware vSphere 6 in production
● SAP Note 2393917 - SAP HANA on VMware vSphere 6.5 and 6.7 in production
● SAP Note 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments
● SAP Note 2024433 - Multiple SAP HANA VMs on VMware vSphere in production VMWare Best Practices
on SAP HANA
● Best Practices and Recommendations for Scale-up Deployments of SAP HANA on VMware vSphere
● SAP and VMware (see Solutions Overviews and White Papers and Technical Resources)
In general the following requirements need to be fulfilled for VMWare:
● The underlying hardware must be certified by SAP's ICC for SAP HANA.
● Do not use memory compression techniques like KSM.
● The maximum memory reserved for the virtual machines should not exceed 90% of the physical memory
of the hypervisor.
● SAP HANA needs the full instruction set of the host CPU(s). Adjust the settings for the VM accordingly.
● For monitoring and system management purposes, VMware Tools must be installed and running as well.
● For performance reasons, the SAP HANA file systems should reside on separate VMDK files.
● For tuning the operating environment, have a look at the sections above in this guide.
Appendix P U B L I C 53

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
54 P U B L I C
Important Disclaimers and Legal Information

Important Disclaimers and Legal Information P U B L I C 55

www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https:/
/www.sap.com/about/legal/trademark.html for
additional trademark information and notices.
THE BEST RUN

Suse linux enterprise_server_15_x_for_sap_applications_configuration_guide_for_sap_hana_en

More Related Content

What's hot (20)

Similar to Suse linux enterprise_server_15_x_for_sap_applications_configuration_guide_for_sap_hana_en (20)

More from Jaleel Ahmed Gulammohiddin (6)

Recently uploaded (20)

Suse linux enterprise_server_15_x_for_sap_applications_configuration_guide_for_sap_hana_en