Home > Workload Solutions > SAP > Guides > SAP HANA TDI Guides > Dell Validated Solution for SAP HANA TDI Deployments with Dell Metro Node > SAP HANA global.ini file
The storage connector API is controlled in the storage section of the SAP HANA global.ini file, as shown in the following code sample. The storage section of the file contains entries for the block devices. You can run the multipath –ll command on the SAP HANA hosts to determine the worldwide identifiers (WWIDs) of the partition entries.
[communication]
listeninterface = .global
[multidb]
mode = multidb
database_isolation = low
singletenant = yes
[persistence]
basepath_datavolumes = /hana/data/ANA
basepath_logvolumes = /hana/log/ANA
use_mountpoints = yes
[storage]
ha_provider = hdb_ha.fcClient
partition_*_*__prtype = 5
partition_1_data__wwid = 3600601604f804a00a79d565d90f63337
partition_1_log__wwid = 3600601604f804a00f99d565d224bd861
partition_2_data__wwid = 3600601604f804a00a89d565d2fd702d9
partition_2_log__wwid = 3600601604f804a00fa9d565d72e37054
partition_3_data__wwid = 3600601604f804a00a99d565d2e9c1d5b
partition_3_log__wwid = 3600601604f804a00fa9d565d2593cbc1
[trace]
ha_fcclient = info
For more information about the SAP HANA scale-out installation, the storage connector, and the global.ini file, see the following documents on the SAP Help Portal:
Postinstallation configuration
The base layer of SAP HANA provides two file I/O interfaces:
You can configure the SAP HANA file I/O layer to optimize file I/O for a specific file system and storage system.
Note: The Linux XFS file system is used on all Dell storage volumes for the SAP HANA persistence.
SAP HANA 1.0
After the initial SAP HANA installation is complete, set the parameters by running the SAP HANA hdbparam command as <sid>adm in the Linux shell:
su - <sid>adm
hdbparam –p # lists current parameter setting
hdbparam –-paramset fileio [DATA].max_parallel_io_requests=128
hdbparam –-paramset fileio [LOG].max_parallel_io_requests=128
hdbparam –-paramset fileio [DATA].max_submit_batch_size=128
hdbparam –-paramset fileio [LOG]. max_submit_batch_size=128
SAP HANA 2.0
Effective as of SAP HANA 2.0, the hdbparam command-line tool has been deprecated. Instead, the parameters are defined as normal parameters in global.ini > [fileio].
Using the SQL console in the SAP HANA Cockpit or SAP HANA Studio, set the parameters in the global.ini file by running the following commands:
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio','max_parallel_io_requests[DATA]') = '128';
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio','max_parallel_io_requests[LOG]') = '128';
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio','max_submit_batch_size[DATA]') = '128';
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio','max_submit_batch_size[LOG]') = '128';
The following figure shows what the fileio section of the global.ini file looks like in SAP HANA Studio after the parameters are set:
All other parameters are set by default during installation. For more information, see SAP Note 2399079: Elimination of hdbparam in SAP HANA 2 (access requires SAP login credentials).
SAP HANA NSE uses the data volume that the main database is using. While no special configuration steps are necessary for the NSE persistence layer, sizing must consider the additional capacity for the NSE feature.
When you use the SAP HANA NSE feature, a portion of DRAM is used as a buffer cache to dynamically load paged data from the persistence (data volume). By default, the size of this buffer cache is 10 percent of the total main memory of the system. For more information, see the SAP HANA NSE Buffer Cache topic in the SAP HANA Administration Guide.
SAP recommends that you do not exceed a ratio of 1:8 for the total amount of warm data that SAP HANA NSE and the buffer cache will handle. When using SAP HANA NSE, you can store data in the warm tier in the following specific granularities:
Data location handling is built into the SAP HANA Data Definition Language (DDL). Manage the configuration by using the SAP HANA CLI SQL client hdbsql or the SQL editor in SAP HANA Studio.
CREATE T_DELL_NSE (id INT, name VARCHAR(100)) PAGE LOADABLE;
CREATE T_DELL_NSE (id INT PAGE LOADABLE, name VARCHAR(100));
ALTER TABLE T_DELL_NSE PAGE LOADABLE CASCADE
ALTER TABLET_DELL_NSE ALTER (name VARCHAR(100) PAGE LOADABLE);
The SAP HANA NSE Advisor, which is based on real-time statistics from an existing SAP HANA database, provides recommendations for which data to move from the hot (in-memory) tier to the warm (SAP HANA NSE) tier. Use the Advisor information for guidance about the amount of data to move to the warm tier on an existing system. For more information about SAP HANA NSE, SAP HANA NSE Data Sizing, and related topics, see the SAP Help Portal.