Home > Workload Solutions > SAP > Guides > SAP HANA TDI Guides > Dell Validated Design for SAP HANA TDI with Dell PowerMax 2500 and 8500 Storage Arrays > Installing the SAP HANA scale-out cluster
Before you run the installation script, prepare the following configuration files:
This section describes the required settings in the SAP HANA global.ini file for an SAP HANA scale-out installation on PowerMax arrays.
Deploying an SAP HANA multinode scale-out cluster on FC-connected systems requires the SAP HANA storage connector fcClient or fcClientMpath. The storage connector is responsible for mounting and unmounting the persistence (data and log) to the SAP HANA worker nodes.
The storage connector also writes SCSI-3 persistent reservations (PRs) to the devices. The Linux sg_persist or mpathpersist command starts an operation known as I/O fencing, which ensures that only one SAP HANA worker host has simultaneous access to a set of data and log devices.
With SAP HANA SP05 Rev 53, SAP released a newer version of the storage connector fcClientMpath. The new version uses the command mpathpersist rather than sg_persist. The mpathpersist command puts the reservations on the devices, enabling device paths to be added while the mount process is ongoing, whereas sg_persist puts the reservations on the device paths when mounting the devices. Paths cannot be added during the mount process, and a remount is necessary. When new device paths are added, SRDF/Metro can be fully supported for SAP HANA scale-out deployments in physical environments with SAP auto-host failover.
To use the fcClientMpath connector:
The keys are added during the mount process to /etc/multipath/prkeys.
The installation uses the global.ini file to describe the SAP HANA storage partitions and the storage connector. The SAP HANA certified Dell storage platforms use fcClient, which is part of the SAP software distribution.
Follow these steps:
Do not alter the name of the global.ini file.
Note: Larger SAP HANA scale-out installations require additional partition entries.
SAP HANA SPS 07 introduced the SAP HANA Database Lifecycle Manager to provide the efficiency of installing all components at one time while automating the installation and providing further flexibility to customers. Our example uses hdblcm to install our SAP HANA 3+1 scale-out cluster.
Follow these steps:
cd /<installation media>/DATA_UNITS/HDB_LCM_LINUX_X86_64
./hdblcm --action=install --dump_configfile_template=PMX_install.cfg
Directory root to search for components
component_root=/SAPShare/software/SAP_HANA2SPS06IM/
Components ( Valid values: all | client | es | ets | lcapps | server | smartda | streaming | rdsync | xs | studio | afl | pos | sal | sca | sop | trd | udf )
components=server,client
Installation Path ( Default: /hana/shared )
sapmnt=/hana/shared
Local Host Name ( Default: server06 )
hostname=hana01
Directory containing a storage configuration
storage_cfg=/hana/shared/PMX_cfg
Note: The storage_cfg parameter points to the directory where you have placed the customized global.ini file.
SAP HANA System ID
sid=PMX
Instance Number
number=00
# System Administrator User ID
userid=1001
ID of User Group (sapsys)
groupid=79
Action to be performed ( Default: exit; Valid values: install | update | extract_components )
action=install
Additional Hosts
addhosts=hana02:storage_partition=2:role=worker,hana03:storage_partition=3:role=worker,hana04:role=standby
Note: The Additional Hosts parameter describes the additional hosts and their roles in the scale-out installation.
You can also use encrypted passwords. For more information, see the SAP HANA Studio Installation and Update Guide.
The hdblcm installation procedure prompts you for any missing passwords or parameters.
After you have created and customized the global.ini file and the installation parameters file, start the installation by running the following command:
./hdblcm --action=install –-configfile=PMX_Install.cfg