IBM Spectrum Scale customization for HANA
This chapter describes how to customize your IBM Spectrum Scale for HANA, including the file system and VDisk layout.
This chapter includes the following topics:
5.1 Overview
The following levels of changes are needed to configure an optimized environment for SAP HANA workloads:
Adjust the IBM Elastic Storage Server (ESS)’s default VDisk configuration by creating at least three file systems.
Because of the different IO workload behaviors of SAP HANA, we create one file system for the log workload and one file system for data workload.
During the tests (which are eligible for any customer environment), you can share data and log file system among many security identifiers (SIDs).
Optionally, you can consider creating file sets to separate the SIDs from each other.
A third file system for the SAP named shared includes no special recommendations and can be created without any special recommendations.
For more information about creating a shared file system, see Appendix E, “Side aware configuration examples” on page 43.
After setting up the file system and ESS adjusted VDisk layout, you must set some specific parameters in your cluster configuration.
The minimum normally required settings are not described further here because they are set by the default deployment procedure. This document focuses only on the parameters that you need to change for an optimized SAP HANA environment.
5.2 File system and VDisk layout
During the installation and setup of your HANA environment, you can customize your file system and IBM Spectrum Scale device names to your own naming conventions (see Figure 5-1). for more information about how to set up and configure your IBM Spectrum Scale file systems, see the Recommended File System Layout page of the SAP website.
Figure 5-1 File system layout
5.2.1 Internal VDisks
Now adjust a pre-configured ESS (default deployment) for an SAP HANA workload. Depending on the chosen model, you can proceed with the default settings, which are deployed by using the default deployment procedure. With the default settings, you cannot scale enough to exceed more than four HANA databases in parallel. If you want to exceed this limit, you must increase the size of the VDisk loghome to 100 GB (the default is 20 GB).
Increasing the size of VDisk loghome is not possible and the loghome VDisk cannot be re-created if any other customer VDisks are available. A prepared sample file is found in the common /usr/lpp/mmfs/samples/vdisk directory.
Rename the sample and edit the file according to the example that is shown in Example 5-1.
Example 5-1 Edited file
[root@is38san1a vdisk]# cat vdisk.stanza.ini
# Recovery group hanaL
# NVR
%vdisk: vdiskName=hanaL_ltip rg=hanaL da=NVR size=48m blocksize=2m raidCode=2WayReplication diskUsage=vdiskLogTip
# SSD
# create log tip backlup vdisk on a single SSD
%vdisk: vdiskName=hanaL_ltbackup rg=hanaL da=SSD size=48m blocksize=2m raidCode=Unreplicated
diskUsage=vdiskLogTipBackup
# DA1
%vdisk: vdiskName=hanaL_lhome rg=hanaL da=DA1 size=100g blocksize=2m raidCode=4WayReplication diskUsage=vdiskLog longTermEventLogSize=4m shortTermEventLogSize=4m fastWriteLogPct=90 diskUsage=vdiskLog
# Recovery group hanaR
%vdisk: vdiskName=hanaR_ltip rg=hanaR da=NVR size=48m blocksize=2m raidCode=2WayReplication
diskUsage=vdiskLogTip
%vdisk: vdiskName=hanaR_ltbackup rg=hanaR da=SSD size=48m blocksize=2m raidCode=Unreplicated
diskUsage=vdiskLogTipBackup %vdisk: vdiskName=hanaR_lhome rg=hanaR da=DA1 size=100g blocksize=2m raidCode=4WayReplication diskUsage=vdiskLog
A larger loghome is always good to use for better performance. The more loghome that is available, the more pagepool is need. If your loghome is configured to “large” in terms of existing pagepool and buffer sizes, it is not fully used.
 
Tip: Because increasing loghome results in wiping out all VDisks, reconfigure your ESS for HANA workloads before the first file systems get created.
Create your VDisks for the ESS Building block by using the mmcrvdisk -F yourfilename command. The Spectrum Scale daemons must be running to create the VDisk.
Blocksizes for SAP HANA file systems for IBM Spectrum Scale V4.x
The block size in the IBM Spectrum Scale file system is an unchangeable value. Therefore, select the block size from the beginning. SAP HANA has three core file systems with different needs:
* /hana/shared: This file system holds all the executable and Log/Trace-Files of an SAP HANA database. It needs to be highly available to ensure continuous operations. Before IBM Spectrum Scale 5.x, the block size had a direct allocation effect when updating the HANA executable files using hdblcm. The preferred Blocksize is 4M.
* /hana/data: This is the persistence layer that an SAP HANA database is started from. Read performance is essential because it directly affects the startup time of an SAP HANA database. The typical Block size range for an SAP HANA database is from 64K - 64M. The preferred Blocksize is 16M.
* /hana/log: This file system holds the change logs. On write intensive loads, this file system must manage 4 - 16K blocks written to the file system. The preferred Blocksize is 16M.
5.2.2 Log file system
As described in 5.2.1, “Internal VDisks” on page 27, create a VDisk stanza file and edit it according to your naming conventions (see Example 5-2). If you are creating a highly available or site aware configuration, add a failureGroup (fg) identifier for each VDisk in the file. The fg must be the same within a building block when you want to use IBM Spectrum Scale replication later on and mirror your data between two ESS building blocks. If you have more than one building block per site, the failure group identifier must be the same over all of the ESSs in the same site. For more information about a highly available scenario configuration example, see Appendix E, “Side aware configuration examples” on page 43.
Example 5-2 Create and edit a VDisk stanza file
[root@is38san1a vdisk]# cat vdisk.stanza.logfs
%vdisk: vdiskName=hanaLM1 rg=hanaL da=DA1 blocksize=1m size=50g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=hanaLD1 rg=hanaL da=DA1 blocksize=1m size=200g raidCode=8+2p diskUsage=dataOnly pool=datapool
 
%vdisk: vdiskName=hanaRM1 rg=hanaR da=DA1 blocksize=1m size=50g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=hanaRD1 rg=hanaR da=DA1 blocksize=1m size=200g raidCode=8+2p diskUsage=dataOnly pool=datapool
 
[root@is38san1a vdisk]#
Create the VDisk by using the mmcrvdisk command. Create the NSDs by using the mmcrnsd command.
Next, create the file system with the parameters that are shown in Example 5-3 (in this example, without IBM Spectrum Scale replication enabled by default).
Example 5-3 Creating the file system
mmcrfs hanalog -F vdisk.stanza.logfs -B 1M --metadata-block-size 1M -M 2 -R 2
-m 1 -r 1 -L 256M -T /hana/log -E no -j scatter -S relatime
For more information about a replicated scenario, see Appendix E, “Side aware configuration examples” on page 43.
5.2.3 Data file system
As described in 5.2.2, “Log file system” on page 28, create the data file system (see Example 5-4).
Example 5-4 Creating the data file system
[root@is38san1a vdisk]# cat vdisk.stanza.datafs
%vdisk: vdiskName=hanaLDFT2M1 rg=hanaL da=DA1 blocksize=1m size=200g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=hanaLDFT2D1 rg=hanaL da=DA1 blocksize=16m size=500g raidCode=8+2p diskUsage=dataOnly pool=datapool
#
%vdisk: vdiskName=hanaRDFT2M1 rg=hanaR da=DA1 blocksize=1m size=200g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=hanaRDFT2D1 rg=hanaR da=DA1 blocksize=16m size=500g raidCode=8+2p diskUsage=dataOnly pool=datapool
Create the VDisk by using the mmcrvdisk command. Create the databases by using the mmcrnsd command.
Create the file system with the parameters that are shown in Example 5-5 (in this example, without IBM Spectrum Scale replication enabled by default).
Example 5-5 Creating the file system
mmcrfs hanadata -F vdisk.stanza.datafs -B 16M --metadata-block-size 1M -M 2
-R 2 -m 1 -r 1 -L 256M -T /hana/data -E no -j scatter -S relatime
For more information about a replicated scenario, see Appendix E, “Side aware configuration examples” on page 43.
5.2.4 Shared file system
As described in 5.2.3, “Data file system” on page 28, create a VDisk stanza file (see Example 5-6).
Example 5-6 Creating a VDisk stanza
[root@ems1 vdisk]# cat vdisk.stanza.sharedfs
%vdisk: vdiskName=rg_gssioS1M1 rg=rg_gssio1 da=DA1 blocksize=1m size=5g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=rg_gssioS1D1 rg=rg_gssio1 da=DA1 blocksize=4m size=100g raidCode=8+2p diskUsage=dataOnly pool=datapool
 
%vdisk: vdiskName=rg_gssioS2M1 rg=rg_gssio2 da=DA1 blocksize=1m size=5g raidCode=4WayReplication diskUsage=metadataOnly
%vdisk: vdiskName=rg_gssioS2D1 rg=rg_gssio2 da=DA1 blocksize=4m size=100g raidCode=8+2p diskUsage=dataOnly pool=datapool
 
[root@ems1 vdisk]#
Next, create the file system with the parameters that are shown in Example 5-7 (without IBM Spectrum Scale replication enabled by default).
Example 5-7 Creating the file system
[root@ems1 vdisk]# mmcrfs hanashared -F vdisk.stanza.sharedfs -B 4M --metadata-block-size
1M -M 2 -R 2 -m 1 -r 1 -L 256M -T /hana/shared -E no -j scatter -S relatime
For more information about a replicated scenario, see Appendix E, “Side aware configuration examples” on page 43.
5.2.5 Creating file sets
You can create an own set of file systems (log, home, and shared) for each SAP instance (SID). You also can operate in an environment with multiple SIDs sharing systems. If you plan to use multiple SIDs, create file sets for each SID.
During the SAP verification and certification, 12 productive SIDs within the same IBM Spectrum Scale file system in parallel were tested successfully in our example.
 
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.216.96.94