Transcript
SAP HANA Tailored Datacenter Integration with Hitachi Virtual Storage Platform Gx00 using 1.5 TB and 2 TB Nodes
Reference Architecture Guide By Milind Pathak
March 2016
Feedback Hitachi Data Systems welcomes your feedback. Please share your thoughts by sending an email message to
[email protected]. To assist the routing of this message, use the paper number in the subject and the title of this white paper in the text.
Contents Solution Overview................................................................................................................ 2 Key Solution Elements......................................................................................................... 3 Hardware Elements......................................................................................................................... 3 Software Elements .......................................................................................................................... 6
Solution Design...................................................................................................................... 7 Fibre Channel Architecture ............................................................................................................. 7 Storage Architecture ....................................................................................................................... 9 Hitachi NAS Platform 4060 Architecture....................................................................................... 29 Network File System Design for Shared Binaries ......................................................................... 30 SAP Storage Connector API Fibre Channel Client ....................................................................... 33
Engineering Validation ...................................................................................................... 35 Sample Files ......................................................................................................................... 36 global.ini ........................................................................................................................................ 36 multipath.conf ............................................................................................................................... 37
Comparison of the Different Hitachi Virtual Storage Platform Models in a SAP TDI Implementation .................................................................................................................. 39 Hitachi Virtual Storage Platform G1000 ........................................................................................ 42 Hitachi Virtual Storage Platform G200 .......................................................................................... 42
1
SAP HANA Tailored Datacenter Integration with Hitachi Virtual Storage Platform Gx00 using 1.5 TB and 2 TB Nodes Reference Architecture Guide This reference architecture guide helps you implement SAP HANA using Tailored Datacenter Integration (TDI) with the following for storage, using either 1.5 TB or 2 TB SAP HANA platform nodes:
Hitachi Virtual Storage Platform G400 (VSP G400)
Hitachi Virtual Storage Platform G600 (VSP G600)
Hitachi Virtual Storage Platform G800 (VSP G800)
This architecture uses two Hitachi NAS Platform 4060 (HNAS) servers in the configuration. Unlike an appliance for the SAP HANA platform, where all hardware components are pre-configured for you, a SAP HANA TDI deployment uses customized solutions. You use products from certified SAP HANA server vendors and from certified SAP HANA enterprise storage vendors to implement SAP HANA. This provides you an opportunity to leverage existing hardware to reduce your total cost of ownership (TCO). Refer to the SAP HANA Tailored Data Center Integration FAQ for more details about TDI. When following this reference architecture guide, use certified server hardware from any vendor in the SAP Certified and Supported SAP HANA Hardware Directory. When looking for a server in a TDI implementation, SAP only allows using the same server hardware from a single hardware partner . If SAP certifies only a specific operating system for use on specific hardware in a TDI implementation, you must use that operating system only. Using the Virtual Storage Platform family of enterprise storage products with SAP HANA has the following benefits:
Increased performance when loading data into SAP HANA
Scalable deployments of SAP HANA
Disaster recovery with minimal performance impact to the production instance
This technical paper assumes you have familiarity with the following:
Storage area network (SAN) based storage systems
Network attached storage (NAS) systems
General storage concepts
General network knowledge
SAP HANA platform
Common IT storage practices Note — Testing of this configuration was performed in a lab environment. Many things affect production environments beyond prediction or duplication in a lab environment. Follow the recommended practice of conducting proof-of-concept testing for acceptable results in a non-production, isolated test environment that matches your production environment before your production implementation of this solution.
1
2
Solution Overview This reference architecture guide provides an example configuration of the storage layout for the SAP HANA platform using nodes with 1.5 TB ad 2 TB of main memory. Testing is within the Hitachi Data Systems lab environment. This configuration uses the following storage components:
Hitachi Virtual Storage Platform Gx00 models — These scale for all data types, flexibly adapting for performance, capacity, and multi-vendor storage. Hitachi NAS Platform — Network-attached storage solution used for file sharing, file server consolidation, data protection, and business-critical NAS workloads.
Figure 1 shows the server-to-storage configuration of this solution using Hitachi Virtual Storage Platform G800. You can use a similar architecture for Virtual Storage Platform G600 and Virtual Storage Platform G400. The maximum number of nodes supported with Virtual Storage Platform G600 and Virtual Storage Platform G400 is listed in Table 5, “Maximum SAP HANA Platform Nodes Supported on Hitachi Virtual Storage Platform Gx00 Models,” on page 9.
Figure 1
2
3
Key Solution Elements These are the key hardware and software elements used in this reference architecture.
Hardware Elements Table 1 describes the key hardware elements needed to deploy a configuration with 16 active nodes and 3 standby nodes with Hitachi Virtual Storage Platform G800. With modification, your implementation can use Virtual Storage Platform G600 or Virtual Storage Platform G400 for storage. Table 1. Hardware Elements Hardware
Quantity
Configuration
Role
Hitachi Virtual Storage Platform G800
1
Block storage for SAP HANA platform nodes and Hitachi NAS Platform
Hitachi NAS Platform 4060
2
For each NAS Platform server:
System management unit 1
Quanta Cloud Technology 1 QuantaPlex T41S-2U4N server
Single frame
2 cluster ports
2 × 10 GbE ports
2 Fibre Channel ports
Provide NFS shared file system for the SAP HANA platform binaries, and cluster-wide configuration files.
2 Ethernet ports 2 Intel Core 2 Duo E7500 processor, 2.93 GHz CPU, 4 GB RAM
NAS Platform cluster management
2.5 inch bay chassis
Management server runs the following:
T41S server node
3 Server Filler
2 Intel Xeon E5-2620 v3 processor, 6C, 2.4 GHz, 85 W 1 heat sink CPU0 and CPU1
NTP
Hitachi Command Suite
Hi-Track Remote Monitoring system
SAP HANA Studio
2 × 16 GB DDR4 2,133 MHz memory module 2 × 500 GB, 7200 RPM, 2.5 inch (6 Gb) SATA HDD 1 dual port 10 GbE Intel 82599ES SFP+ OCP mezzanine card 1 dual port 1 GbE Base-T Intel i350 mezzanine card 1 Emulex dual port 8 Gb/sec Fibre Channel HBA
3
4 Table 1. Hardware Elements (Continued) Hardware
Quantity
Configuration
Role
Rack servers and server 19 blade chassis certified for SAP HANA using certified configurations from Find Certified Appliances
1.5 TB or 2 TB of main memory nodes
SAP HANA configuration for 1.5 TB node or 2 TB node
Brocade VDX 6740 switch 4
Two switches with distinct VLANs, each dedicated to NFS and SAP HANA inter-cluster network
10 GbE NFS and inter-cluster network
Brocade ICX 6430-48 port switch
1
Brocade ICX6430-24 port 1 switch
10 GbE client network
Two switches with one VLAN to provide uplink network to customer network infrastructure 1 GbE
1 GbE Management Network
48 ports 1 GbE
NAS Platform private network
24 ports
Table 1 lists all the hardware elements used for the validation of this reference architecture, but this guide only explains the storage architecture. For details about the design of server and network configuration, see Hitachi Unified Compute Platform for the SAP HANA Platform using 1.5 TB SAP HANA Nodes in a Scale-Out 24 TB Configuration and 2 TB SAP HANA Nodes in a Scale-out 32 TB Configuration of 16 Active Nodes and 3 Standby Nodes with Hitachi Compute Blade 2500 Chassis, 520X B2 Server Blades, and Hitachi Virtual Storage Platform G800 Reference Architecture Guide (AS-437-02 or later, PDF).
Hitachi Virtual Storage Platform Gx00 Models Hitachi Virtual Storage Platform Gx00 models are based on industry-leading enterprise storage technology. With flash-optimized performance, these systems provide advanced capabilities previously available only in high-end storage arrays. With the Virtual Storage Platform Gx00 models, you can build a high performance, software-defined infrastructure to transform data into valuable information. Hitachi Storage Virtualization Operating System provides storage virtualization, high availability, superior performance, and advanced data protection for all Virtual Storage Platform Gx00 models. This proven, mature software provides common features to consolidate assets, reclaim space, extend life, and reduce migration effort. New management software improves ease of use to save time and reduce complexity. The infrastructure of Storage Virtualization Operating System creates a management framework for improved IT response to business demands. This solution uses Virtual Storage Platform G400, Virtual Storage Platform G600, or Virtual Storage Platform G600. For more information, see “Comparison of the Different Hitachi Virtual Storage Platform Models in a SAP TDI Implementation” on page 39.
4
5 Hitachi NAS Platform 4060 Hitachi NAS Platform is an advanced and integrated network attached storage (NAS) solution. It provides a powerful tool for file sharing, file server consolidation, data protection, and business-critical NAS workloads.
Powerful hardware-accelerated file system with multi-protocol file services, dynamic provisioning, intelligent tiering, virtualization, and cloud infrastructure Seamless integration with Hitachi SAN storage, Hitachi Command Suite, and Hitachi Data Discovery Suite for advanced search and index Integration with Hitachi Content Platform for active archiving, regulatory compliance, and large object storage for cloud infrastructure
This solution uses NAS Platform 4060 file system modules for file system sharing of the binaries, configuration, and trace files of SAP HANA. There are two NAS Platform 4060 servers. The system management unit provides front-end server administration and monitoring tools for NAS Platform. It supports clustering and acts as a quorum device in a cluster.
Quanta Cloud Technology QuantaPlex T41S-2U Chassis with a single node (Optional) Quanta Cloud Technology QuantaPlex T41S-2U is an ultra-dense design equipped with four independent nodes. It creates the flexibility to set up different workloads independently in one 2U shared infrastructure, providing optimal data center performance per dollar. This solution uses one node of a four node Quanta Cloud Technology QuantaPlex T41S-2U chassis for the management server. The management server acts as a central device for managing the SAP HANA platform. Manage the following from the management server:
Brocade ICX 6430 — 48 port switch
Brocade VDX 6740 switches
System management unit
SAP HANA nodes
Hitachi NAS Platform 4060 servers
Hitachi Virtual Storage Platform Gx00 and server blades
NTP configuration
Hi-Track Remote Monitoring system from Hitachi Data Systems
Hitachi Command Suite and management of the server blades
SAP HANA Studio
5
6 Software
Elements
Table 2 describes the software products used to deploy the 16 active node and 3 standby node configuration. Table 2. Software Elements Software
Version
SUSE Linux Enterprise Server for SAP Applications
11 SP3
SAP HANA platform
1.0 SPS09, Rev. 97 or later
Hitachi Storage Navigator Modular 2
Microcode dependent
Hitachi Command Suite
8.1.2 or later
Hitachi Virtual Storage Platform Gx00 Microcode
83-03-01-40/00
Hitachi NAS Platform firmware
12.5.4038.xx
System management unit software
12.5.4038.xx
System management unit operating system
CentOS-6.2
Microsoft® Windows Server® 2012 R2
Standard Edition
For Quanta Cloud Technology QuantaPlex 2U4N server
SAP HANA SAP HANA converges database and application platform capabilities in-memory to transform transactions, analytics, text analysis, predictive and spatial processing so businesses can operate in real-time. This combines database, data processing, and application platform capabilities in a single in-memory platform. Also, the platform provides libraries for predictive, planning, text processing, spatial, and business analytics — all on the same architecture. By eliminating the divide between transactions and analytics, SAP HANA allows you to answer any business question anywhere in real time.
6
7
Solution Design This is the detailed solution design for a SAP HANA TDI integration with Hitachi Virtual Storage Platform Gx00. This reference architecture guide uses a 19 nodes scale-out configuration (16 active nodes +3 standby nodes) on Virtual Storage Platform G800 to explain storage design and architecture. With modification, your solution may use Virtual Storage Platform G400 or Virtual Storage Platform G600.
Fibre Channel Architecture Each SAP HANA node needs to support two dedicated 8 Gb/sec or 16 Gb/sec Fibre Channel ports. Connect the SAP HANA nodes directly to the designated Hitachi Virtual Storage Platform Gx00 target port. Hitachi NAS Platform is direct attached to Hitachi Virtual Storage Platform G800 for hosting the /hana/shared binaries and configuration files of the SAP HANA platform installation. Table 3 shows the storage port mapping. Table 3. Storage Port Mapping SAP HANA Platform Node
Fibre Channel Port
Hitachi Virtual Storage Platform G800 Ports
Node001
Port 0
1C
Node001
Port 1
2C
Node002
Port 0
3C
Node002
Port 1
4C
Node003
Port 0
5C
Node003
Port 1
6C
Node004
Port 0
7C
Node004
Port 1
8C
Node005
Port 0
1D
Node005
Port 1
2D
Node006
Port 0
3D
Node006
Port 1
4D
Node007
Port 0
5D
Node007
Port 1
6D
Node008
Port 0
7D
Node008
Port 1
8D
Node009
Port 0
1E
Node009
Port 1
2E
Node010
Port 0
3E
Node010
Port 1
4E
Node011
Port 0
5E
Node011
Port 1
6E
Node012
Port 0
7E
Node012
Port 1
8E
Node013
Port 0
1F
7
8 Table 3. Storage Port Mapping (Continued) SAP HANA Platform Node
Fibre Channel Port
Hitachi Virtual Storage Platform G800 Ports
Node013
Port 1
2F
Node014
Port 0
3F
Node014
Port 1
4F
Node015
Port 0
5F
Node015
Port 1
6F
Node016
Port 0
7F
Node016
Port 1
8F
Node017
Port 0
3A
Node017
Port 1
4A
Node018
Port 0
5A
Node018
Port 1
6A
Node019
Port 0
7A
Node019
Port 1
8A
HNAS
Hitachi NAS Platform Server 1, FC 1
1A
HNAS
Hitachi NAS Platform Server 1, FC 3
2A
HNAS
Hitachi NAS Platform Server 2, FC 1
1B
HNAS
Hitachi NAS Platform Server 2, FC 3
2B
When using a direct connection between the SAP HANA servers and Hitachi Virtual Storage Platform G800, use the port properties in Table 4. Also enable host mode 100 for all the storage ports used. Table 4. Port Properties for Direct Connection For This
Use This
Port Security
Disable
Port Speed
Auto (8 Gbps)
Fabric
Off
Connection Type
FC-AL
8
9 Storage
Architecture
Table 5 shows the maximum number of nodes for Hitachi Virtual Storage Platform Gx00 models used in this reference architecture guide. Table 5. Maximum SAP HANA Platform Nodes Supported on Hitachi Virtual Storage Platform Gx00 Models Hitachi Virtual Storage Platform Model
Maximum Number of Supported Active SAP HANA Platform Nodes
Virtual Storage Platform G800
16
Virtual Storage Platform G600
8
Virtual Storage Platform G400
6
This reference architecture guide uses the scale-out solution for SAP HANA with 16 active and 3 standby nodes with Virtual Storage Platform G800 to illustrate the storage architecture. If you use different storage, change the nodes as follows:
Virtual Storage Platform G400 uses six scale-up nodes on a single storage array.
Virtual Storage Platform G600 uses eight scale-up nodes on a single storage array.
For further details, see Tailored Datacenter Integration Implementation of Multiple SAP HANA Scale-up HSW Appliances on Hitachi Virtual Storage Platform G400 and [Hitachi Virtual Storage Platform] G600 Reference Architecture Guide (AS-392-00, PDF) The central storage system for the whole SAP HANA platform cluster is Hitachi Virtual Storage Platform G800. Several usage aspects divide the space provided by Virtual Storage Platform G800, as follows:
Operating system (OS) LUN provisioning for SAP HANA platform nodes
Log device provisioning for SAP HANA platform database
Data device provisioning for SAP HANA platform database
Block storage provisioning for Hitachi NAS Platform shared file system to store the SAP HANA binaries and cluster-wide configuration files.
For Virtual Storage Platform G800, provision the parity groups shown in one of the following figures:
Figure 2 on page 12. This shows the RAID group configuration for the of 1.5 TB SAP HANA node configuration, with four active nodes and one standby node. Figure 3 on page 13. This shows the RAID group configuration for the 2 TB SAP HANA node configuration, with four active nodes and one standby node.
9
10 design follows a four-node storage building block approach for the SAP HANA data volume and the SAP HANA log The volume, as well as the SAP HANA shared volume.
Operating System Boot LUN The installation of SUSE Linux Enterprise Server for SAP Applications or Red Hat Enterprise Linux is on the boot LUN.
Each node has its own 100 GB LUN for the operating system volumes. A single parity group configured as RAID-6 (6D + 2P) on 8 × 600 GB drives provisions the operating system boot LUN for SAP HANA node 1 to SAP HANA node 19.
From this parity group, create 19 LDEVs, each with a capacity of 100 GB.
Map each LDEV exclusively to the corresponding SAP HANA node as follows: LUN number 00.
For Hitachi NAS Platform 4060 Block Storage in a 1.5 TB SAP HANA node configuration This is to store the shared binaries and configuration files of the SAP HANA database.
The block storage for Hitachi NAS Platform has two parity groups, configured as RAID-6 (6D+2P) on 16 × 600 GB drives. In each of the two parity groups, create two LDEVs of 1600 GB each. Create a dynamic provisioning pool named HNAS_HDP_pool. Assign all the created Hitachi NAS Platform LDEVs to this pool. This allows the use of all the disks concurrently on the NAS Platform for better performance. For a four node building block, create 4 virtual volumes, each with 1600 GB in HNAS_HDP_pool. Complete the LUN path assignment for these virtual volumes to the ports listed in Table 3, “Storage Port Mapping,” on page 7 that are connected to Hitachi NAS Platform.
For Hitachi NAS Platform 4060 Block Storage in a 2 TB SAP HANA node configuration This is to store the shared binaries and configuration files of the SAP HANA database.
For less than five active nodes, Hitachi NAS Platform has one parity group, configured as RAID-6 (6D+2P) on 8 × 600 GB drives. From 5 to 12 active nodes, Hitachi NAS Platform has two parity groups, configured as RAID-6 (6D+2P) on 16 × 600 GB drives. From 13 up to 16 active nodes, Hitachi NAS Platform has three parity groups, configured as RAID-6 (6D+2P) on 24 × 600 GB drives. Each parity group has 4 × 800 GB LDEVs. Create a dynamic provisioning pool named HNAS_HDP_pool. Assign all the created LDEVs for Hitachi NAS Platform to this pool. This allows the use of all disks concurrently on NAS Platform, for better performance. Create virtual volumes in HNAS_HDP_pool and complete the LUN path assignment for these virtual volumes to the ports listed in Table 3, “Storage Port Mapping,” on page 7 that are connected to Hitachi NAS Platform.
Up to four nodes, create 4 × 800 GB virtual volumes.
From 5 to 12 nodes, create 8 × 800 GB virtual volumes.
From 13 to 16 nodes, create 12 × 800 GB virtual volumes.
10
11 SAP HANA Log Volumes
For the SAP HANA log volumes, first create two parity groups configured as RAID-6 (6D+2P) on 16 × 600 GB drives.
In each of the two parity groups, create two LDEVs at 600 GB each.
Map each SAP HANA log volume to all SAP HANA nodes at each port with the LUN ID of the specified host.
SAP HANA Data Volumes
For a 1.5 TB SAP HANA node configuration
Create three parity groups configured as RAID-6 (14D+2P) on 48 × 600 GB drives. Create four LDEVs with a capacity of 1800 GB per each parity group. Table 6, “Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes and SAP HANA Platform Data Volumes for 1.5 TB SAP HANA Node Configuration,” on page 14 shows the parity groups and LDEVs created for data volumes. Assign three LDEVs for use as data volumes to each SAP HANA node, as shown in Table 3, “Storage Port Mapping,” on page 7.
For a 2 TB SAP HANA node configuration
Create four parity groups configured as RAID-6 (14D+2P) on 64 × 600 GB drives. Create four LDEVs with a capacity of 1800 GB per each parity group. Table 7, “Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration,” on page 17 shows the parity groups and LDEVs created for data volumes. Assign four LDEVs for use as data volumes to each SAP HANA node, as shown in Table 3, “Storage Port Mapping,” on page 7.
11
12
Figure 2
12
13
Figure 3 For a 1.5 TB SAP HANA node configuration, Table 6, “Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes and SAP HANA Platform Data Volumes for 1.5 TB SAP HANA Node Configuration,” on page 14 lists the parity groups and LDEV assignment for the following:
Operating system volumes
NAS Platform volumes
SAP HANA platform log volumes
SAP HANA data volumes
For a 2 TB SAP HANA node configuration, Table 7, “Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration,” on page 17 lists the parity groups and LDEV assignment for the following:
Operating system volumes
NAS Platform volumes
SAP HANA platform log volumes
SAP HANA data volumes
13
14 Table 6. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes and SAP HANA Platform Data Volumes for 1.5 TB SAP HANA Node Configuration Parity Group ID
Parity Group RAID Level and disks
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
1
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:01:00
HANA_OS_LUN_N1
100 GB
MPU-10
00:02:00
HANA_OS_LUN_N2
100 GB
MPU-11
00:03:00
HANA_OS_LUN_N3
100 GB
MPU-20
00:04:00
HANA_OS_LUN_N4
100 GB
MPU-21
00:05:00
HANA_OS_LUN_N5
100 GB
MPU-10
00:06:00
HANA_OS_LUN_N6
100 GB
MPU-11
00:07:00
HANA_OS_LUN_N7
100 GB
MPU-20
00:08:00
HANA_OS_LUN_N8
100 GB
MPU-21
00:09:00
HANA_OS_LUN_N9
100 GB
MPU-10
00:10:00
HANA_OS_LUN_N10
100 GB
MPU-11
00:11:00
HANA_OS_LUN_N11
100 GB
MPU-20
00:12:00
HANA_OS_LUN_N12
100 GB
MPU-21
00:13:00
HANA_OS_LUN_N13
100 GB
MPU-10
00:14:00
HANA_OS_LUN_N14
100 GB
MPU-11
00:15:00
HANA_OS_LUN_N15
100 GB
MPU-20
00:16:00
HANA_OS_LUN_N16
100 GB
MPU-21
00:17:00
HANA_OS_LUN_N17
100 GB
MPU-10
00:18:00
HANA_OS_LUN_N18
100 GB
MPU-11
00:19:00
HANA_OS_LUN_N19
100 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:01
HNAS_VOL_1
1600 GB
MPU-10
00:00:02
HNAS_VOL_2
1600 GB
MPU-11
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:03
HNAS_VOL_3
1600 GB
MPU-20
00:00:04
HNAS_VOL_4
1600 GB
MPU-21
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:05
HNAS_VOL_5
1600 GB
MPU-10
00:00:06
HNAS_VOL_6
1600 GB
MPU-11
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:07
HNAS_VOL_7
1600 GB
MPU-20
00:00:08
HNAS_VOL_8
1600 GB
MPU-21
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:09
HNAS_VOL_9
1600 GB
MPU-10
00:00:10
HNAS_VOL_10
1600 GB
MPU-11
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:11
HNAS_VOL_11
1600 GB
MPU-20
00:00:12
HNAS_VOL_12
1600 GB
MPU-21
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:13
HNAS_VOL_13
1600 GB
MPU-10
00:00:14
HNAS_VOL_14
1600 GB
MPU-11
2
3
4
5
6
7
8
14
15 Table 6. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes and SAP HANA Platform Data Volumes for 1.5 TB SAP HANA Node Configuration (Continued) Parity Group ID
Parity Group RAID Level and disks
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
9
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:00:15
HNAS_VOL_15
1600 GB
MPU-20
00:00:16
HNAS_VOL_16
1600 GB
MPU-21
RAID-6 (6D+2P) on 900 600 GB 10k RPM SAS drives
00:01:01
HANA_LOG_N1
600 GB
MPU-21
00:02:01
HANA_LOG_N2
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:03:01
HANA_LOG_N3
600 GB
MPU-11
00:04:01
HANA_LOG_N4
600 GB
MPU-10
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:05:01
HANA_LOG_N5
600 GB
MPU-21
00:06:01
HANA_LOG_N6
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:07:01
HANA_LOG_N7
600 GB
MPU-11
00:08:01
HANA_LOG_N8
600 GB
MPU-10
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:09:01
HANA_LOG_N9
600 GB
MPU-21
00:10:01
HANA_LOG_N10
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:11:01
HANA_LOG_N11
600 GB
MPU-11
00:12:01
HANA_LOG_N12
600 GB
MPU-10
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:13:01
HANA_LOG_N13
600 GB
MPU-21
00:14:01
HANA_LOG_N14
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:15:01
HANA_LOG_N15
600 GB
MPU-11
00:16:01
HANA_LOG_N16
600 GB
MPU-10
RAID-6 (14D+2P) on 00:01:02 600 GB 10k RPM 00:02:02 SAS drives 00:03:02
HANA_DATA_N1_01
1800 GB
MPU-10
HANA_DATA_N2_01
1800 GB
MPU-21
HANA_DATA_N3_01
1800 GB
MPU-20
00:04:02
HANA_DATA_N4_01
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:01:03 600 GB 10k RPM 00:02:03 SAS drives 00:03:03
HANA_DATA_N1_02
1800 GB
MPU-11
HANA_DATA_N2_02
1800 GB
MPU-10
HANA_DATA_N3_02
1800 GB
MPU-21
00:04:03
HANA_DATA_N4_02
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:01:04 600 GB 10k RPM 00:02:04 SAS drives 00:03:04
HANA_DATA_N1_03
1800 GB
MPU-20
HANA_DATA_N2_03
1800 GB
MPU-11
HANA_DATA_N3_03
1800 GB
MPU-10
00:04:04
HANA_DATA_N4_03
1800 GB
MPU-21
10
11
12
13
14
15
16
17
18
19
20
15
16 Table 6. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes and SAP HANA Platform Data Volumes for 1.5 TB SAP HANA Node Configuration (Continued) Parity Group ID
Parity Group RAID Level and disks
22
23
24
26
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
RAID-6 (14D+2P) on 00:05:05 600 GB 10k RPM 00:06:05 SAS drives 00:07:05
HANA_DATA_N5_01
1800 GB
MPU-10
HANA_DATA_N6_01
1800 GB
MPU-21
HANA_DATA_N7_01
1800 GB
MPU-20
00:08:05
HANA_DATA_N8_01
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:05:06 600 GB 10k RPM 00:06:06 SAS drives 00:07:06
HANA_DATA_N5_02
1800 GB
MPU-11
HANA_DATA_N6_02
1800 GB
MPU-10
HANA_DATA_N7_02
1800 GB
MPU-21
00:08:06
HANA_DATA_N8_02
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:05:07 600 GB 10k RPM 00:06:07 SAS drives 00:07:07
HANA_DATA_N5_03
1800 GB
MPU-20
HANA_DATA_N6_03
1800 GB
MPU-11
HANA_DATA_N7_03
1800 GB
MPU-10
00:08:07
HANA_DATA_N8_03
1800 GB
MPU-21
RAID-6 (14D+2P) on 00:09:08 600 GB 10k RPM 00:10:08 SAS drives 00:11:08
HANA_DATA_N9_01
1800 GB
MPU-10
HANA_DATA_N10_01
1800 GB
MPU-21
HANA_DATA_N11_01
1800 GB
MPU-20
HANA_DATA_N12_01
1800 GB
MPU-11
HANA_DATA_N9_02
1800 GB
MPU-11
HANA_DATA_N10_02
1800 GB
MPU-10
HANA_DATA_N11_02
1800 GB
MPU-21
HANA_DATA_N12_02
1800 GB
MPU-20
HANA_DATA_N9_03
1800 GB
MPU-20
HANA_DATA_N10_03
1800 GB
MPU-11
HANA_DATA_N11_03
1800 GB
MPU-10
00:12:10
HANA_DATA_N12_03
1800 GB
MPU-21
RAID-6 (14D+2P) on 00:13:11 600 GB 10k RPM 00:14:11 SAS drives 00:15:11
HANA_DATA_N13_01
1800 GB
MPU-10
HANA_DATA_N14_01
1800 GB
MPU-21
HANA_DATA_N15_01
1800 GB
MPU-20
00:16:11
HANA_DATA_N16_01
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:13:12 600 GB 10k RPM 00:14:12 SAS drives 00:15:12
HANA_DATA_N13_02
1800 GB
MPU-11
HANA_DATA_N14_02
1800 GB
MPU-10
HANA_DATA_N15_02
1800 GB
MPU-21
00:16:12
HANA_DATA_N16_02
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:13:13 600 GB 10k RPM 00:14:13 SAS drives 00:15:13
HANA_DATA_N13_03
1800 GB
MPU-20
HANA_DATA_N14_03
1800 GB
MPU-11
HANA_DATA_N15_03
1800 GB
MPU-10
00:16:13
HANA_DATA_N16_03
1800 GB
MPU-21
00:12:08 27
RAID-6 (14D+2P) on 00:09:09 600 GB 10k RPM 00:10:09 SAS drives 00:11:09 00:12:09
28
30
31
32
RAID-6 (14D+2P) on 00:09:10 600 GB 10k RPM 00:10:10 SAS drives 00:11:10
16
17 Table 7. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration Parity Group ID
Parity Group RAID Level and disks
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
1
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:01:00
HANA_Boot_LUN_N1
100 GB
MPU-21
00:02:00
HANA_Boot_LUN_N2
100 GB
MPU-10
00:03:00
HANA_Boot_LUN_N3
100 GB
MPU-11
00:04:00
HANA_Boot_LUN_N4
100 GB
MPU-20
00:05:00
HANA_Boot_LUN_N5
100 GB
MPU-21
00:06:00
HANA_Boot_LUN_N6
100 GB
MPU-10
00:07:00
HANA_Boot_LUN_N7
100 GB
MPU-11
00:08:00
HANA_Boot_LUN_N8
100 GB
MPU-20
00:09:00
HANA_Boot_LUN_N9
100 GB
MPU-21
00:10:00
HANA_Boot_LUN_N10
100 GB
MPU-10
00:11:00
HANA_Boot_LUN_N11
100 GB
MPU-11
00:12:00
HANA_Boot_LUN_N12
100 GB
MPU-20
00:13:00
HANA_Boot_LUN_N13
100 GB
MPU-21
00:14:00
HANA_Boot_LUN_N14
100 GB
MPU-10
00:15:00
HANA_Boot_LUN_N15
100 GB
MPU-11
00:16:00
HANA_Boot_LUN_N16
100 GB
MPU-20
00:17:00
HANA_Boot_LUN_N17
100 GB
MPU-21
00:18:00
HANA_Boot_LUN_N18
100 GB
MPU-10
00:19:00
HANA_Boot_LUN_N19
100 GB
MPU-11
00:00:01
HNAS_VOL_1
800 GB
MPU-20
00:00:02
HNAS_VOL_2
800 GB
MPU-21
00:00:03
HNAS_VOL_3
800 GB
MPU-10
00:00:04
HNAS_VOL_4
800 GB
MPU-11
00:00:05
HNAS_VOL_5
800 GB
MPU-20
00:00:06
HNAS_VOL_6
800 GB
MPU-21
00:00:07
HNAS_VOL_7
800 GB
MPU-10
00:00:08
HNAS_VOL_8
800 GB
MPU-11
00:00:09
HNAS_VOL_9
800 GB
MPU-20
00:00:10
HNAS_VOL_10
800 GB
MPU-21
00:00:11
HNAS_VOL_11
800 GB
MPU-10
00:00:12
HNAS_VOL_12
800 GB
MPU-11
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:01:01
HANA_LOG_N1
600 GB
MPU-11
00:02:01
HANA_LOG_N2
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:03:01
HANA_LOG_N3
600 GB
MPU-21
00:04:01
HANA_LOG_N4
600 GB
MPU-10
2
3
4
5
6
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
17
18 Table 7. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration (Continued) Parity Group ID
Parity Group RAID Level and disks
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
7
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:05:01
HANA_LOG_N5
600 GB
MPU-11
00:06:01
HANA_LOG_N6
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:07:01
HANA_LOG_N7
600 GB
MPU-21
00:08:01
HANA_LOG_N8
600 GB
MPU-10
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:09:01
HANA_LOG_N9
600 GB
MPU-11
00:10:01
HANA_LOG_N10
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:11:01
HANA_LOG_N11
600 GB
MPU-21
00:12:01
HANA_LOG_N12
600 GB
MPU-10
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:13:01
HANA_LOG_N13
600 GB
MPU-11
00:14:01
HANA_LOG_N14
600 GB
MPU-20
RAID-6 (6D+2P) on 600 GB 10k RPM SAS drives
00:15:01
HANA_LOG_N15
600 GB
MPU-21
00:16:01
HANA_LOG_N16
600 GB
MPU-10
RAID-6 (14D+2P) on 00:01:02 600 GB 10k RPM 00:02:02 SAS drives 00:03:02
HANA_DATA_N1_01
1800 GB
MPU-10
HANA_DATA_N2_01
1800 GB
MPU-11
HANA_DATA_N3_01
1800 GB
MPU-20
00:04:02
HANA_DATA_N4_01
1800 GB
MPU-21
RAID-6 (14D+2P) on 00:01:03 600 GB 10k RPM 00:02:03 SAS drives 00:03:03
HANA_DATA_N1_02
1800 GB
MPU-11
HANA_DATA_N2_02
1800 GB
MPU-20
HANA_DATA_N3_02
1800 GB
MPU-21
00:04:03
HANA_DATA_N4_02
1800 GB
MPU-10
RAID-6 (14D+2P) on 00:01:04 600 GB 10k RPM 00:02:04 SAS drives 00:03:04
HANA_DATA_N1_03
1800 GB
MPU-20
HANA_DATA_N2_03
1800 GB
MPU-21
HANA_DATA_N3_03
1800 GB
MPU-10
00:04:04
HANA_DATA_N4_03
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:01:05 600 GB 10k RPM 00:02:05 SAS drives 00:03:05
HANA_DATA_N1_04
1800 GB
MPU-21
HANA_DATA_N2_04
1800 GB
MPU-10
HANA_DATA_N3_04
1800 GB
MPU-11
00:04:05
HANA_DATA_N4_04
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:05:02 600 GB 10k RPM 00:06:02 SAS drives 00:07:02
HANA_DATA_N5_01
1800 GB
MPU-10
HANA_DATA_N6_01
1800 GB
MPU-11
HANA_DATA_N7_01
1800 GB
MPU-20
00:08:02
HANA_DATA_N8_01
1800 GB
MPU-21
8
9
10
11
12
13
14
15
16
17
18
19 Table 7. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration (Continued) Parity Group ID
Parity Group RAID Level and disks
18
19
20
21
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
RAID-6 (14D+2P) on 00:05:03 600 GB 10k RPM 00:06:03 SAS drives 00:07:03
HANA_DATA_N5_02
1800 GB
MPU-11
HANA_DATA_N6_02
1800 GB
MPU-20
HANA_DATA_N7_02
1800 GB
MPU-21
00:08:03
HANA_DATA_N8_02
1800 GB
MPU-10
RAID-6 (14D+2P) on 00:05:04 600 GB 10k RPM 00:06:04 SAS drives 00:07:04
HANA_DATA_N5_03
1800 GB
MPU-20
HANA_DATA_N6_03
1800 GB
MPU-21
HANA_DATA_N7_03
1800 GB
MPU-10
00:08:04
HANA_DATA_N8_03
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:05:05 600 GB 10k RPM 00:06:05 SAS drives 00:07:05
HANA_DATA_N5_04
1800 GB
MPU-21
HANA_DATA_N6_04
1800 GB
MPU-10
HANA_DATA_N7_04
1800 GB
MPU-11
00:08:05
HANA_DATA_N8_04
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:09:02 600 GB 10k RPM 00:10:02 SAS drives 00:11:02
HANA_DATA_N9_01
1800 GB
MPU-10
HANA_DATA_N10_01
1800 GB
MPU-11
HANA_DATA_N11_01
1800 GB
MPU-20
HANA_DATA_N12_01
1800 GB
MPU-21
HANA_DATA_N9_02
1800 GB
MPU-11
HANA_DATA_N10_02
1800 GB
MPU-20
HANA_DATA_N11_02
1800 GB
MPU-21
HANA_DATA_N12_02
1800 GB
MPU-10
HANA_DATA_N9_03
1800 GB
MPU-20
HANA_DATA_N10_03
1800 GB
MPU-21
HANA_DATA_N11_03
1800 GB
MPU-10
HANA_DATA_N12_03
1800 GB
MPU-11
HANA_DATA_N9_04
1800 GB
MPU-21
HANA_DATA_N10_04
1800 GB
MPU-10
HANA_DATA_N11_04
1800 GB
MPU-11
00:12:05
HANA_DATA_N12_04
1800 GB
MPU-20
RAID-6 (14D+2P) on 00:13:02 600 GB 10k RPM 00:14:02 SAS drives 00:15:02
HANA_DATA_N13_01
1800 GB
MPU-10
HANA_DATA_N14_01
1800 GB
MPU-11
HANA_DATA_N15_01
1800 GB
MPU-20
00:16:02
HANA_DATA_N16_01
1800 GB
MPU-21
RAID-6 (14D+2P) on 00:13:03 600 GB 10k RPM 00:14:03 SAS drives 00:15:03
HANA_DATA_N13_02
1800 GB
MPU-11
HANA_DATA_N14_02
1800 GB
MPU-20
HANA_DATA_N15_02
1800 GB
MPU-21
00:16:03
HANA_DATA_N16_02
1800 GB
MPU-10
00:12:02 22
RAID-6 (14D+2P) on 00:09:03 600 GB 10k RPM 00:10:03 SAS drives 00:11:03 00:12:03
23
RAID-6 (14D+2P) on 00:09:04 600 GB 10k RPM 00:10:04 SAS drives 00:11:04 00:12:04
24
25
26
RAID-6 (14D+2P) on 00:09:05 600 GB 10k RPM 00:10:05 SAS drives 00:11:05
19
20 Table 7. Parity Groups and LDEV Assignment for Operating System, Hitachi NAS Platform, SAP HANA Platform Log Volumes, and SAP HANA Platform Data Volumes for 2 TB SAP HANA Node Configuration (Continued) Parity Group ID
Parity Group RAID Level and disks
27
28
LDEV ID
LDEV Name
LDEV Size
MPU Assignment
RAID-6 (14D+2P) on 00:13:04 600 GB 10k RPM 00:14:04 SAS drives 00:15:04
HANA_DATA_N13_03
1800 GB
MPU-20
HANA_DATA_N14_03
1800 GB
MPU-21
HANA_DATA_N15_03
1800 GB
MPU-10
00:16:04
HANA_DATA_N16_03
1800 GB
MPU-11
RAID-6 (14D+2P) on 00:13:05 600 GB 10k RPM 00:14:05 SAS drives 00:15:05
HANA_DATA_N13_04
1800 GB
MPU-21
HANA_DATA_N14_04
1800 GB
MPU-10
HANA_DATA_N15_04
1800 GB
MPU-11
00:16:05
HANA_DATA_N16_04
1800 GB
MPU-20
Build the storage system with RAID groups, disk storage, and Virtual Storage Platform G800 components using a four-node building block approach. See the following tables for RAID Groups, drives, and LUN details for the following:
1.5 TB nodes
Table 8, “Drives and RAID Groups for 1.5 TB HANA Node Configuration for Hitachi Virtual Storage Platform G800,” on page 21 Table 9, “Disk Storage based on 4-node Storage Building Blocks for 1.5 TB SAP HANA Node Configuration,” on page 21
2 TB nodes
Table 10, “Drives and RAID Groups for 2 TB HANA Node Configuration for Hitachi Virtual Storage Platform G800,” on page 22 Table 11, “Disk Storage for a 4-Node Storage Building Block for 2 TB HANA Node Configuration,” on page 22
Note — 1.5 TB HANA node configuration uses the 1 × memory formula for each active node for SAP HANA shared. From SAP HANA SPS11, there is a new formula to uses 1 × memory for a 4 node building block for SAP HANA shared. The new formula is used in this reference architecture by 2 TB SAP HANA node configuration, but not the 1.5 TB SAP HANA node configuration.
20
21 Table 8. Drives and RAID Groups for 1.5 TB HANA Node Configuration for Hitachi Virtual Storage Platform G800 SAP HANA Node Building Blocks
Operating System Drives, RAID Groups
Log Volume Drives, RAID Groups
Data Volume Drives, RAID Groups
Hitachi NAS Platform Volume Drives, RAID Groups
4
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
16 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
48 × 600 GB 10k RPM SAS drives in 3 groups configured as RAID-6 (14D+2P)
16 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
8
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
32 × 600 GB 10k RPM SAS drives in 4 groups configured as RAID-6 (6D+2P)
96 × 600 GB 10k RPM SAS drives in 6 groups configured as RAID-6 (14D+2P)
32 × 600 GB 10k RPM SAS drives in 4 groups configured as RAID-6 (6D+2P)
12
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
48 × 600 GB 10k RPM SAS drives in 6 groups configured as RAID-6 (6D+2P)
144 × 600 GB 10k RPM SAS drives in 9 groups configured as RAID-6 (14D+2P)
48 × 600 GB 10k RPM SAS drives in 6 groups configured as RAID-6 (6D+2P)
16
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
64 × 600 GB 10k RPM SAS drives in 8 groups configured as RAID-6 (6D+2P)
192 × 600 GB 10k RPM SAS drives in 12 groups configured as RAID-6 (14D+2P)
64 × 600 GB 10k RPM SAS drives in 8 groups configured as RAID-6 (6D+2P)
Table 9. Disk Storage based on 4-node Storage Building Blocks for 1.5 TB SAP HANA Node Configuration SAP HANA Node Building Block
Number of Hitachi NAS Platform Servers
Operating System LUNs
Log LUNs
Data LUNs
Hitachi NAS Platform 4060 LUNs
4
2
19 × 100 GB
4 × 600 GB
12 × 1800 GB
4 × 1600 GB
8
2
19 × 100 GB
8 × 600 GB
24 × 1800 GB
8 × 1600 GB
12
2
19 × 100 GB
12 × 600 GB
36 × 1800 GB
12 × 1600 GB
16
2
19 × 100 GB
16 × 600 GB
48 × 1800 GB
16 × 1600 GB
21
22 Table 10. Drives and RAID Groups for 2 TB HANA Node Configuration for Hitachi Virtual Storage Platform G800 SAP HANA Node Building Blocks
Operating System Drives, RAID Groups
Log Volume Drives, RAID Groups
Data Volume Drives, RAID Groups
Hitachi NAS Platform Volume Drives, RAID Groups
4
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
16 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
64 × 600 GB 10k RPM SAS drives in 4 groups configured as RAID-6 (14D+2P)
8 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
8
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
32 × 600 GB 10k RPM SAS drives in 4 groups configured as RAID-6 (6D+2P)
128 × 600 GB 10k RPM SAS drives in 8 groups configured as RAID-6 (14D+2P)
16 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
12
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
48 × 600 GB 10k RPM SAS drives in 6 groups configured as RAID-6 (6D+2P)
192 × 600 GB 10k RPM SAS drives in 12 groups configured as RAID-6 (14D+2P)
16 × 600 GB 10k RPM SAS drives in 2 groups configured as RAID-6 (6D+2P)
16
8 × 600 GB 10k RPM SAS drives in 1 group configured as RAID-6 (6D+2P)
64 × 600 GB 10k RPM SAS drives in 8 groups configured as RAID-6 (6D+2P)
256 × 600 GB 10k RPM SAS drives in 16 groups configured as RAID-6 (14D+2P)
24 × 600 GB 10k RPM SAS drives in 3 groups configured as RAID-6 (6D+2P)
Table 11. Disk Storage for a 4-Node Storage Building Block for 2 TB HANA Node Configuration SAP HANA Node Building Block
Number of Hitachi NAS Platform Servers
Operating System LUNs
Log LUNs
Data LUNs
Hitachi NAS Platform 4060 LUNs
4
2
19 × 100 GB
4 × 600 GB
16 × 1800 GB
4 × 800 GB
8
2
19 × 100 GB
8 × 600 GB
32 × 1800 GB
8 × 800 GB
12
2
19 × 100 GB
12 × 600 GB
48 × 1800 GB
8 × 800 GB
16
2
19 × 100 GB
16 × 600 GB
64 × 1800 GB
12 × 800 GB
While mapping the LUN path assignment for each node, add the LUNs in the following order: 1. Map the operating system LUN for the specific SAP HANA platform node. 2. Map the log volume and data volume of each SAP HANA platform node. The following tables show an example configuration of the LUN path assignment for Node001. The LUN assignment would be the same for all nodes except for the first LUN, which is the operating system LUN of that specific node.
Table 12, “Example LUN Path Assignment for Node001 for a 1.5 TB SAP HANA Node Configuration,” on page 23 for 1.5 TB nodes Table 13, “Example LUN Path Assignment for Node001 for a 2 TB SAP HANA Node Configuration,” on page 24 for 2 TB nodes
22
23 Table 12. Example LUN Path Assignment for Node001 for a 1.5 TB SAP HANA Node Configuration LUN ID
LDEV ID
LDEV Name
0000
00:01:00
HANA_OS_LUN_N1
0001
00:01:01
HANA_LOG_N1
0002
00:01:02
HANA_DATA_N1_01
0003
00:01:03
HANA_DATA_N1_02
0004
00:01:04
HANA_DATA_N1_03
0005
00:02:01
HANA_LOG_N2
0006
00:02:02
HANA_DATA_N2_01
0007
00:02:03
HANA_DATA_N2_02
0008
00:02:04
HANA_DATA_N2_03
0009
00:03:01
HANA_LOG_N3
0010
00:03:02
HANA_DATA_N3_01
0011
00:03:03
HANA_DATA_N3_02
0012
00:03:04
HANA_DATA_N3_03
0013
00:04:01
HANA_LOG_N4
0014
00:04:02
HANA_DATA_N4_01
0015
00:04:03
HANA_DATA_N4_02
0016
00:04:04
HANA_DATA_N4_03
0017
00:05:01
HANA_LOG_N5
0018
00:05:02
HANA_DATA_N5_01
0019
00:05:03
HANA_DATA_N5_02
0020
00:05:04
HANA_DATA_N5_03
0021
00:06:01
HANA_LOG_N6
0022
00:06:02
HANA_DATA_N6_01
0023
00:06:03
HANA_DATA_N6_02
0024
00:06:04
HANA_DATA_N6_03
0025
00:07:01
HANA_LOG_N7
0026
00:07:02
HANA_DATA_N7_01
0027
00:07:03
HANA_DATA_N7_02
0028
00:07:04
HANA_DATA_N7_03
0029
00:08:01
HANA_LOG_N8
0030
00:08:02
HANA_DATA_N8_01
0031
00:08:03
HANA_DATA_N8_02
0032
00:08:04
HANA_DATA_N8_03
0033
00:09:01
HANA_LOG_N9
0034
00:09:02
HANA_DATA_N9_01
0035
00:09:03
HANA_DATA_N9_02
0036
00:09:04
HANA_DATA_N9_03
23
24 Table 12. Example LUN Path Assignment for Node001 for a 1.5 TB SAP HANA Node Configuration (Continued) LUN ID
LDEV ID
LDEV Name
0037
00:10:01
HANA_LOG_N10
0038
00:10:02
HANA_DATA_N10_01
0039
00:10:03
HANA_DATA_N10_02
0040
00:10:04
HANA_DATA_N10_03
0041
00:11:01
HANA_LOG_N11
0042
00:11:02
HANA_DATA_N11_01
0043
00:11:03
HANA_DATA_N11_02
0044
00:11:04
HANA_DATA_N11_03
0045
00:12:01
HANA_LOG_N12
0046
00:12:02
HANA_DATA_N12_01
0047
00:12:03
HANA_DATA_N12_02
0048
00:12:04
HANA_DATA_N12_03
0049
00:13:01
HANA_LOG_N13
0050
00:13:02
HANA_DATA_N13_01
0051
00:13:03
HANA_DATA_N13_02
0052
00:13:04
HANA_DATA_N13_03
0053
00:14:01
HANA_LOG_N14
0054
00:14:02
HANA_DATA_N14_01
0055
00:14:03
HANA_DATA_N14_02
0056
00:14:04
HANA_DATA_N14_03
0057
00:15:01
HANA_LOG_N15
0058
00:15:02
HANA_DATA_N15_01
0059
00:15:03
HANA_DATA_N15_02
0060
00:15:04
HANA_DATA_N15_03
0061
00:16:01
HANA_LOG_N16
0062
00:16:02
HANA_DATA_N16_01
0063
00:16:03
HANA_DATA_N16_02
0064
00:16:04
HANA_DATA_N16_03
Table 13. Example LUN Path Assignment for Node001 for a 2 TB SAP HANA Node Configuration LUN ID
LDEV ID
LDEV Name
0000
00:01:00
HANA_OS_LUN_N1
0001
00:01:01
HANA_LOG_N1
0002
00:01:02
HANA_DATA_N1_01
0003
00:01:03
HANA_DATA_N1_02
0004
00:01:04
HANA_DATA_N1_03
0005
00:01:05
HANA_DATA_N1_04
24
25 Table 13. Example LUN Path Assignment for Node001 for a 2 TB SAP HANA Node Configuration (Continued) LUN ID
LDEV ID
LDEV Name
0006
00:02:01
HANA_LOG_N2
0007
00:02:02
HANA_DATA_N2_01
0008
00:02:03
HANA_DATA_N2_02
0009
00:02:04
HANA_DATA_N2_03
0010
00:02:05
HANA_DATA_N2_04
0011
00:03:01
HANA_LOG_N3
0012
00:03:02
HANA_DATA_N3_01
0013
00:03:03
HANA_DATA_N3_02
0014
00:03:04
HANA_DATA_N3_03
0015
00:03:05
HANA_DATA_N3_04
0016
00:04:01
HANA_LOG_N4
0017
00:04:02
HANA_DATA_N4_01
0018
00:04:03
HANA_DATA_N4_02
0019
00:04:04
HANA_DATA_N4_03
0020
00:04:05
HANA_DATA_N4_04
0021
00:05:01
HANA_LOG_N5
0022
00:05:02
HANA_DATA_N5_01
0023
00:05:03
HANA_DATA_N5_02
0024
00:05:04
HANA_DATA_N5_03
0025
00:05:05
HANA_DATA_N5_04
0026
00:06:01
HANA_LOG_N6
0027
00:06:02
HANA_DATA_N6_01
0028
00:06:03
HANA_DATA_N6_02
0029
00:06:04
HANA_DATA_N6_03
0030
00:06:05
HANA_DATA_N6_04
0031
00:07:01
HANA_LOG_N7
0032
00:07:02
HANA_DATA_N7_01
0033
00:07:03
HANA_DATA_N7_02
0034
00:07:04
HANA_DATA_N7_03
0035
00:07:05
HANA_DATA_N7_04
0036
00:08:01
HANA_LOG_N8
0037
00:08:02
HANA_DATA_N8_01
0038
00:08:03
HANA_DATA_N8_02
0039
00:08:04
HANA_DATA_N8_03
0040
00:08:05
HANA_DATA_N8_04
0041
00:09:01
HANA_LOG_N9
0042
00:09:02
HANA_DATA_N9_01
0043
00:09:03
HANA_DATA_N9_02
25
26 Table 13. Example LUN Path Assignment for Node001 for a 2 TB SAP HANA Node Configuration (Continued) LUN ID
LDEV ID
LDEV Name
0044
00:09:04
HANA_DATA_N9_03
0045
00:09:05
HANA_DATA_N9_04
0045
00:10:01
HANA_LOG_N10
0046
00:10:02
HANA_DATA_N10_01
0047
00:10:03
HANA_DATA_N10_02
0048
00:10:04
HANA_DATA_N10_03
0049
00:10:05
HANA_DATA_N10_04
0050
00:11:01
HANA_LOG_N11
0051
00:11:02
HANA_DATA_N11_01
0052
00:11:03
HANA_DATA_N11_02
0053
00:11:04
HANA_DATA_N11_03
0054
00:11:05
HANA_DATA_N11_04
0055
00:12:01
HANA_LOG_N12
0056
00:12:02
HANA_DATA_N12_01
0057
00:12:03
HANA_DATA_N12_02
0058
00:12:04
HANA_DATA_N12_03
0059
00:12:05
HANA_DATA_N12_04
0060
00:13:01
HANA_LOG_N13
0061
00:13:02
HANA_DATA_N13_01
0062
00:13:03
HANA_DATA_N13_02
0063
00:13:04
HANA_DATA_N13_03
0064
00:13:05
HANA_DATA_N13_04
0065
00:14:01
HANA_LOG_N14
0066
00:14:02
HANA_DATA_N14_01
0067
00:14:03
HANA_DATA_N14_02
0068
00:14:04
HANA_DATA_N14_03
0069
00:14:05
HANA_DATA_N14_04
0070
00:15:01
HANA_LOG_N15
0071
00:15:02
HANA_DATA_N15_01
0072
00:15:03
HANA_DATA_N15_02
0073
00:15:04
HANA_DATA_N15_03
0074
00:15:05
HANA_DATA_N15_04
0075
00:16:01
HANA_LOG_N16
0076
00:16:02
HANA_DATA_N16_01
0077
00:16:03
HANA_DATA_N16_02
0078
00:16:04
HANA_DATA_N16_03
0079
00:16:05
HANA_DATA_N16_04
26
27 following figures show the LUN and port assignment for SAP HANA server Node001 to Node019 on Hitachi Virtual The Storage Platform G800 for the following:
Figure 4 on page 27 for 1.5 TB nodes
Figure 5 on page 28 for 2 TB nodes
Figure 4
27
28
Figure 5 The following are the minimum spare disks required for different building block configurations:
4 Node — 3 × 600 GB 10k RPM SAS drives
8 Node — 6 × 600 GB 10k RPM SAS drives
12 Node
For 1.5 TB SAP HANA node configuration — 8 × 600 GB 10k RPM SAS drives
For 2 TB SAP HANA node configuration — 9 × 600 GB 10k RPM SAS drives
16 Node — 11 × 600 GB 10k RPM SAS drives
28
29 Hitachi
NAS Platform 4060 Architecture
This architecture uses two Hitachi NAS Platform 4060 servers in the configuration. Use two 10 GbE network links to cluster interconnect the two NAS Platform servers. Connect each NAS Platform server directly to the Hitachi Virtual Storage Platform Gx00 target ports using two Fibre Channel cables from each NAS Platform node.
System Management Unit Web Manager, the graphical user interface of the system management unit, provides front-end server administration and monitoring tools. It supports clustering and acts as a quorum device in a cluster. This solution uses an external system management unit that manages two NAS Platform servers. Use one of the following browsers to run Web Manager:
Microsoft Internet Explorer®: version 9.0, or later
Mozilla Firefox: version 6.0, or later
Private Management Network Connect the private management interfaces of the G2 servers and the system management unit to a dedicated 1 GbE management switch for the private heartbeat network. Devices connected to this private management switch are only accessible through the system management unit.
Public Data Network The public data network consists of the public Ethernet port of the system management unit connected to a 1 GbE management switch.
Storage Subsystem This solution uses Hitachi Virtual Storage Platform G800 as the storage subsystem. Hitachi NAS Platform 4060 has direct-attached Fibre Channel connections with Virtual Storage Platform G800 target ports using two Fibre Channel cables.
Server Connections Figure 6 shows the back of the Hitachi NAS Platform 4060 server.
Figure 6
29
30 C1 and Port C2 are the NAS Platform 4060 cluster ports. To enable clustering, do the following: Port
Connect Port C1 of first NAS Platform server to Port C1 of the second NAS Platform server.
Connect Port C2 of first NAS Platform server to Port C2 of the second NAS Platform server.
Port tg1 and Port tg2 are 10 GbE ports. Link aggregate and connect these ports to the 10 GbE switch for the SAP HANA NFS network connection between the SAP HANA platform nodes and Hitachi NAS Platform. Hitachi recommends the 10 GbE switch to support for jumbo frames, LACP, and the ability to segregate this network traffic from any other VLAN. Connect Fibre Channel Port FC1 and Port FC3 directly to the Hitachi Virtual Storage Platform G800 ports, as shown below:
1A and 2A for the first NAS Platform server
1B and 2B for the second NAS Platform server
Connect Port eth1 of the NAS Platform server to the dedicated 1 GbE management switch for the private heart beat network. For the direct connection between Hitachi NAS Platform and Hitachi Virtual Storage Platform G800, set the port properties as shown in Table 14. Table 14. Hitachi Virtual Storage Platform G800 Port Properties Set This
To This
Port Security
Disable
Port Speed
Auto (8 Gbps)
Fabric
Off
Connection Type
FC-AL
Network File System Design for Shared Binaries This solution requires a network file system to store cluster-wide SAP HANA binaries and configuration files of the in-memory database. Host this shared file system called /hana/shared/
, on Hitachi NAS Platform 4060. Mount this file system on all SAP HANA nodes. “” is the system ID for the SAP HANA production database instance. This solution, 1.5 TB HANA node configuration uses 16 virtual volume LDEVs as listed in; and 2 TB HANA node configuration uses 12 virtual volume LDEVs, as listed in Table 15, “Dynamic Provisioning Pool IDs and Virtual Volume LDEV IDs for 1.5 TB SAP HANA Node Configuration,” on page 32 and Table 16, “Dynamic Provisioning Pool IDs and Virtual Volume LDEV IDs for 2 TB SAP HANA Node Configuration,” on page 32.
Refer to each LDEV as a system drive.
With these system drives, create a single storage pool called HANABIN_.
Configure two EVS on the NAS Platform nodes, as follows:
EVS on NAS Platform node 1 as HNASEVS1
EVS on NAS Platform node 2 as HNASEVS2
30
31 Create the shared file system hana_shared_ using the storage pool HANABIN_ with the following:
Capacity based on the number of HANA nodes
1.5 TB HANA node configuration has
For up to 4 active HANA nodes: 6 TB
For up to 8 active HANA nodes: 12 TB
For up to 12 active HANA nodes: 18 TB
For up to 16 active HANA nodes: 24 TB
2 TB HANA node configuration has:
For up to 4 active HANA nodes: 3 TB
For up to 12 active HANA nodes: 6.2 TB
For up to 16 active HANA nodes: 9 TB
Block size of 32 KB
Allocate on demand to allow automatically expanding to the size limit
Thin provisioning enabled
Mount and then export the file system. Mount the NFS export /hana_shared_ on the file system path /hana/shared/ on all nineteen SAP HANA nodes. Set the MTU size to 9000 on both NAS Platform nodes. Create a dynamic provisioning pool named HNAS_HDP_pool and assign all the above sixteen LDEVs to this pool. For a 1.5 TB node configuration, create 16 virtual volumes, as shown in Table 15 on page 32. Create each virtual volume with 1600 GB. For a 2 TB node configuration, create 12 virtual volumes, as shown in Table 16 on page 32. Create each with virtual volume with 800 GB. Perform the LUN path assignment for these virtual volumes to the ports as shown in Table 3, “Storage Port Mapping,” on page 7.
31
32 Table 15. Dynamic Provisioning Pool IDs and Virtual Volume LDEV IDs for 1.5 TB SAP HANA Node Configuration Dynamic Provisioning Pool ID
Dynamic Provisioning Pool Name
Virtual Volume Names
Virtual Volume LDEV ID for HNAS Shared Binaries
Virtual Volume Size for HNAS Shared Binaries
MPU Assignment
0
HNAS_HDP_Pool
HNAS_HANA_VVOL_1
00:0A:01
1600.00 GB
MPU-10
HNAS_HANA_VVOL_2
00:0A:02
1600.00 GB
MPU-11
HNAS_HANA_VVOL_3
00:0A:03
1600.00 GB
MPU-20
HNAS_HANA_VVOL_4
00:0A:04
1600.00 GB
MPU-21
HNAS_HANA_VVOL_5
00:0A:05
1600.00 GB
MPU-10
HNAS_HANA_VVOL_6
00:0A:06
1600.00 GB
MPU-11
HNAS_HANA_VVOL_7
00:0A:07
1600.00 GB
MPU-20
HNAS_HANA_VVOL_8
00:0A:08
1600.00 GB
MPU-21
HNAS_HANA_VVOL_9
00:0A:09
1600.00 GB
MPU-10
HNAS_HANA_VVOL_10
00:0A:10
1600.00 GB
MPU-11
HNAS_HANA_VVOL_11
00:0A:11
1600.00 GB
MPU-20
HNAS_HANA_VVOL_12
00:0A:12
1600.00 GB
MPU-21
HNAS_HANA_VVOL_13
00:0A:13
1600.00 GB
MPU-10
HNAS_HANA_VVOL_14
00:0A:14
1600.00 GB
MPU-11
HNAS_HANA_VVOL_15
00:0A:15
1600.00 GB
MPU-20
HNAS_HANA_VVOL_16
00:0A:16
1600.00 GB
MPU-21
Table 16. Dynamic Provisioning Pool IDs and Virtual Volume LDEV IDs for 2 TB SAP HANA Node Configuration Dynamic Provisioning Pool ID
Dynamic Provisioning Pool Name
Virtual Volume Names
Virtual Volume LDEV ID for HNAS Shared Binaries
Virtual Volume Size for HNAS Shared Binaries
MPU Assignment
0
HNAS_HDP_Pool
HNAS_HANA_VVOL_1
00:0A:01
800.00 GB
MPU-20
HNAS_HANA_VVOL_2
00:0A:02
800.00 GB
MPU-21
HNAS_HANA_VVOL_3
00:0A:03
800.00 GB
MPU-10
HNAS_HANA_VVOL_4
00:0A:04
800.00 GB
MPU-11
HNAS_HANA_VVOL_5
00:0A:05
800.00 GB
MPU-20
HNAS_HANA_VVOL_6
00:0A:06
800.00 GB
MPU-21
HNAS_HANA_VVOL_7
00:0A:07
800.00 GB
MPU-10
HNAS_HANA_VVOL_8
00:0A:08
800.00 GB
MPU-11
HNAS_HANA_VVOL_9
00:0A:09
800.00 GB
MPU-20
HNAS_HANA_VVOL_10
00:0A:10
800.00 GB
MPU-21
HNAS_HANA_VVOL_11
00:0A:11
800.00 GB
MPU-10
HNAS_HANA_VVOL_12
00:0A:12
800.00 GB
MPU-11
32
33 SAP
Storage Connector API Fibre Channel Client
The SAP HANA Storage Connector API Fibre Channel client defines a set of interface functions called during the following:
Normal SAP HANA platform cluster operation
Failover handling
Storage connector clients implement the functions defined in the Storage Connector API. The scale-out of solution Hitachi Unified Compute Platform for the SAP HANA Platform uses the fcClientLVM implementation. This supports the use of Logical Volume Manager. SAP supports this solution to enable the use of high-performance Fibre Channel devices for a SAP HANA platform installation. The fcClientLVM implementation does the following:
Uses standard Linux commands, such as multipath and sg_persist. Install and configure these commands. Mounts the SAP HANA platform volumes. It also implements a proper fencing mechanism during a failover by means of SCSI-3 persistent reservations.
Configuration of the SAP Storage Connector API is contained within the SAP HANA platform global.ini file that is located at /hana/shared//global/hdb/custom/config.
SAN Operating System Configuration and SUSE Installation This SAP HANA platform configuration uses a SAN boot for each node. Each node has its own 100 GB LUN on Hitachi Virtual Storage Platform G800 for the operating system LUNs. Map the operating system LUNs to each node, following Table 12, “Example LUN Path Assignment for Node001 for a 1.5 TB SAP HANA Node Configuration,” on page 23 or Table 13, “Example LUN Path Assignment for Node001 for a 2 TB SAP HANA Node Configuration,” on page 24. The installation of SUSE Linux Enterprise Server for SAP Applications resides on the operating system LUN. Configure the SUSE operating system to use multipathing for accessing the storage devices. Set the multipath.conf file with options in the sample files in “Sample Files” on page 36.
SAP HANA Platform Data and Log Configuration SAP HANA uses a plain file system to store the contents of the database. The database state is held in data files and log files that are stored in data and log volumes. Each database partition has its own data and log volume with a standard XFS file system. Use Logical Volume Manager to configure the data volume and log volume. Logical Volume Manager creates a single striped volume on which the XFS file system is created to store the data volume and log volume. The striped volumes act as the persistent layer for the SAP HANA servers. Only active SAP HANA nodes need the data volume and log volume. Standby nodes do not require these volumes. However, the LUN paths of all data and log volumes are assigned to the ports of all the nodes for high availability.
33
34 HANA Platform Node Network Configuration SAP Each SAP HANA node has three different networks required, as follows:
SAP HANA platform inter-cluster network — Fully redundant 10 GbE network for node-to-node communication within the SAP HANA system. This is a SAP HANA internal network, not publicly accessible from outside the SAP HANA system.
SAP HANA platform NFS network — Fully redundant 10 GbE network for accessing the SAP HANA shared volume. Every node in the cluster must be able to access this shared resource for SAP HANA platform binaries, configurations, and traces. This share is not meant for public access. It is only accessible by the SAP HANA nodes.
SAP HANA platform client network — Fully redundant 10 GbE network for connection between the SAP HANA platform database and its clients or application servers Configure the SAP HANA, inter-cluster, NFS, and client networks using operating system-level bonding devices. Build up these devices from physical network devices. Set each bonding device using a MTU size of 9000 bytes. Configuration of the 10 GbE network switch must include jumbo frame packets configuration, also.
Management of the operating system (optional) — 1 GbE network This is a 1 GbE operating system management network. This network is a non-redundant network meant for management purposes only. It is not vital to the SAP HANA platform services, making it optional.
34
35
Engineering Validation Engineering validation for this solution was with server blades from Hitachi Data Systems. During validation, the following scenarios were implemented, and storage KPI testing was performed, using the SAP HWCCT tool.
SAP HANA platform installed as one scale-out system with sixteen active nodes and three standby nodes on a single Hitachi Virtual Storage Platform G800
SAP HANA platform installed as eight scale-up systems on a single Hitachi Virtual Storage Platform G600
SAP HANA platform installed as six scale-up systems on a single Hitachi Virtual Storage Platform G400
Refer to SAP Note 1943937 - Hardware Configuration Check Tool - Central Note, for details.
35
36
Sample Files The following sample files are referenced in this document:
“global.ini” on page 36
“multipath.conf” on page 37
global.ini The following is a sample global.ini file for a 16-node configuration: [communication] listeninterface = .global [persistence] basepath_datavolumes = /hana/data/HIT basepath_logvolumes = /hana/log/HIT [storage] ha_provider = hdb_ha.fcClientLVM partition_*_*__prtype = 5 partition_1_data__lvmname = vgHITdata001-lvdata partition_1_log__lvmname = vgHITlog001-lvlog partition_2_data__lvmname = vgHITdata002-lvdata partition_2_log__lvmname = vgHITlog002-lvlog partition_3_data__lvmname = vgHITdata003-lvdata partition_3_log__lvmname = vgHITlog003-lvlog partition_4_data__lvmname = vgHITdata004-lvdata partition_4_log__lvmname = vgHITlog004-lvlog partition_5_data__lvmname = vgHITdata005-lvdata partition_5_log__lvmname = vgHITlog005-lvlog partition_6_data__lvmname = vgHITdata006-lvdata partition_6_log__lvmname = vgHITlog006-lvlog partition_7_data__lvmname = vgHITdata007-lvdata partition_7_log__lvmname = vgHITlog007-lvlog partition_8_data__lvmname = vgHITdata008-lvdata partition_8_log__lvmname = vgHITlog008-lvlog partition_9_data__lvmname = vgHITdata009-lvdata 36
37 partition_9_log__lvmname = vgHITlog009-lvlog partition_10_data__lvmname = vgHITdata010-lvdata partition_10_log__lvmname = vgHITlog010-lvlog partition_11_data__lvmname = vgHITdata011-lvdata partition_11_log__lvmname = vgHITlog011-lvlog partition_12_data__lvmname = vgHITdata012-lvdata partition_12_log__lvmname = vgHITlog012-lvlog partition_13_data__lvmname = vgHITdata013-lvdata partition_13_log__lvmname = vgHITlog013-lvlog partition_14_data__lvmname = vgHITdata014-lvdata partition_14_log__lvmname = vgHITlog014-lvlog partition_15_data__lvmname = vgHITdata015-lvdata partition_15_log__lvmname = vgHITlog015-lvlog partition_16_data__lvmname = vgHITdata016-lvdata partition_16_log__lvmname = vgHITlog016-lvlog [trace] ha_fcclientlvm = info
multipath.conf The following is a sample multipath.conf file: devices { device { vendor "HITACHI" product "*"
user_friendly_names "no" path_checker "directio" path_grouping_policy "multibus" path_selector "queue-length 0" uid_attribute "ID_SERIAL" failback "immediate" rr_weight "uniform"
37
38 rr_min_io_rq "128" features "0" no_path_retry "5" } }
blacklist { devnode "^fio[a-z]" devnode "^(ram|raw|loop|fd|md|sr|scd|st)[0-9]*" devnode "^hd[a-z][0-9]*" devnode "^cciss.c[0-9]d[0-9].*" }
multipaths { multipath { wwid 360060e8007275a000030275a00000100 path_selector "service-time 0" } }
38
39
Comparison of the Different Hitachi Virtual Storage Platform Models in a SAP TDI Implementation There are five members of Hitachi Virtual Storage Platform family:
Virtual Storage Platform G1000
Virtual Storage Platform G800
Virtual Storage Platform G600
Virtual Storage Platform G400
Virtual Storage Platform G200
Validation of this reference architecture was done with SAP HANA nodes on the following Virtual Storage Platform Gx00 models:
Virtual Storage Platform G800
Virtual Storage Platform G600
Virtual Storage Platform G400
These storage platforms have the same high availability features and run on the same microcode as Virtual Storage Platform G1000. When SAP certifies enterprise storage for the SAP HANA platform, that storage meets the TDI storage KPI requirements set by SAP. Testing showed that the storage design of Virtual Storage Platform G800, Virtual Storage Platform G600, and Virtual Storage Platform G400 meets those KPI requirements. It is not mandatory for you to use the same storage design that was used to test for storage KPI testing. Refer to the SAP HANA Tailored Data Center Integration: Frequently Asked Questions for more details about TDI. Figure 7 shows the Hitachi Virtual Storage Platform family in the order of increasing performance and storage capacity.
Figure 7
39
40 Table 17, “Hitachi Virtual Storage Platform Family Feature Comparison,” on page 40 highlights the hardware features of the Hitachi Virtual Storage Platform family. Table 18, “Hitachi Virtual Storage Platform Storage Family Software,” on page 41 highlights the software features of the Hitachi Virtual Storage Platform family. Table 17. Hitachi Virtual Storage Platform Family Feature Comparison Hitachi Virtual Storage Platform G200
Hitachi Virtual Storage Platform G400
Hitachi Virtual Storage Platform G600
Hitachi Virtual Storage Platform G800
Hitachi Virtual Storage Platform G1000
Maximum Raw Internal Capacity
1,058 TB
1,920 TB
2,880 TB
5,760 TB
4,511 TB
Maximum Raw External Capacity
8 PB
16 PB
64 PB
255 PB
Flash Module Drives
1.6 TB, 3.2 TB
Small Form Factor 200 GB, 400 GB solid-state drive (SSD) (SFF) Drives 600 GB, 1.2TB 10k RPM hard disk drive (HDD)
400 GB, 800 GB SSD 600 GB, 1.2 TB 10k RPM HDD
300 GB 15k RPM HDD
300 GB, 600 GB 15k RPM HDD Large Form Factor 4 TB 7200 RPM HDD (LFF) Drives Maximum Drives
252
480
720
1,440
2,304 SFF 1,152 LFF
Disk Expansion Trays
2U: 24 SFF (2.5 inch), 2U: 12 LFF (3.5inch)
16U: 192 SFF (2.5 inch)
2U: 12 flash module drive (FMD)
16U: 96 LFF (3.5 inch),
4U: 60 LFF (3.5 inch) and SFF (2.5 inch)
16U: 96 FMD Block Module 3U Height (with service processor) Block Controllers
2
Host Interfaces (with drives)
16 Fibre Channel: 8 Gb/sec 8 Fibre Channel: 16 Gb/sec
5U
10U
16 32 Fibre Channel: 8 Gb/sec 16 Fibre Channel: 16 Gb/sec 16 iSCSI: 10 Gb/sec
8 iSCSI: 10 Gb/sec
48 Fibre Channel: 8 Gb/sec
192 Fibre Channel: 8 Gb/sec
24 Fibre Channel: 16 Gb/sec
96 Fibre Channel: 16 Gb/sec
24 iSCSI: 10Gb/sec
176 FICON: 8 Gb/sec 192 FCoE: 10 GB/sec
Maximum Cache
64 GB
128 GB
256 GB
512 GB
2,048 GB
40
41 Table 17. Hitachi Virtual Storage Platform Family Feature Comparison (Continued) Hitachi Virtual Storage Platform G200 Maximum LUN Size
Hitachi Virtual Storage Platform G400
Hitachi Virtual Storage Platform G600
Hitachi Virtual Storage Platform G800
Hitachi Virtual Storage Platform G1000
4,096
16,384
65,280
240
480
575
60 TB
Maximum Number 2,048 LUNs RAID Supported
10, 5, 6
Maximum RAID Groups
84
File Module Height 3U per node Nodes per Cluster 1-8 Nodes
1-8 Nodes
File System Size
256 TB pool, single namespace up to maximum capacity
Maximum File Systems
128
Maximum Snapshots
1024 per file system, 1 million clones
Cache per Node
48 GB
Protocols
NFS/SMB/FTP/iSCSI and HTTP to the cloud
Fibre Channel Ports
4 × 8 Gb/sec ports per node
Ethernet Ports
4 × 10 GbE, 6 × 1 GbE per node
108 GB
Table 18. Hitachi Virtual Storage Platform Storage Family Software Name
Description
Hitachi Storage Virtualization Operating System
Hitachi Infrastructure Director
Hitachi Device Manager
Hitachi Dynamic Provisioning
Hitachi Dynamic Link Manager Advanced
Hitachi Universal Volume Manager
Cache partition manager
Storage system-based utilities
File Operating System
CIFS and NFS protocols, high-availability cluster, quick snapshot restore feature, file system rollback feature, virtual server, storage pool, file system audit
Hitachi Data Mobility
Hitachi Dynamic Tiering with active flash, Hitachi Tiered Storage Manager
Hitachi Local Replication
Hitachi ShadowImage Replication, Hitachi Replication Manager, Hitachi Application Protector
Hitachi Remote Replication
Hitachi TrueCopy, Hitachi Universal Replicator
Hitachi File Replication
Hitachi NAS Replication, Hitachi NAS File Clone
41
42 Table 18. Hitachi Virtual Storage Platform Storage Family Software (Continued) Name
Description
Hitachi Performance Analytics
Hitachi Command Director, Hitachi Tuning Manager
Automation
Hitachi Automation Director, Hitachi Data Instance Director
High Availability
Uses global-active device
Encryption
data-at-rest encryption feature
Hitachi Virtual Storage Platform G1000 SAP certifies Hitachi Virtual Storage Platform G1000 for use as enterprise storage for SAP HANA Its architecture is more resilient than the Virtual Storage Platform Gx00 models. See SAP HANA Tailored Datacenter Integration with Hitachi Virtual Storage Platform G1000 using 2 TB SAP HANA Nodes Reference Architecture Guide (AS -348-00, PDF) to create a TDI implementation of SAP HANA using Virtual Storage Platform G1000.
Hitachi Virtual Storage Platform G200 Hitachi Virtual Storage Platform G200 is certified for SAP HANA in a scale-up solution as an appliance. It is not certified for a TDI implementation. See Hitachi Unified Compute Platform for the SAP HANA Platform in a Scale-Up Configuration Using Hitachi Compute Blade 2500 and Hitachi Virtual Storage Platform G200 Reference Architecture Guide (AS-386-02, PDF) for details:
42
For More Information Hitachi Data Systems Global Services offers experienced storage consultants, proven methodologies and a comprehensive services portfolio to assist you in implementing Hitachi products and solutions in your environment. For more information, see the Hitachi Data Systems Global Services website. Live and recorded product demonstrations are available for many Hitachi products. To schedule a live demonstration, contact a sales representative. To view a recorded demonstration, see the Hitachi Data Systems Corporate Resources website. Click the Product Demos tab for a list of available recorded demonstrations. Hitachi Data Systems Academy provides best-in-class training on Hitachi products, technology, solutions and certifications. Hitachi Data Systems Academy delivers on-demand web-based training (WBT), classroom-based instructor-led training (ILT) and virtual instructor-led training (vILT) courses. For more information, see the Hitachi Data Systems Services Education website. For more information about Hitachi products and services, contact your sales representative or channel partner or visit the Hitachi Data Systems website.
1
Corporate Headquarters 2845 Lafayette Street Santa Clara, CA 96050-2639 USA www.HDS.com
community.HDS.com
Regional Contact Information Americas: +1 408 970 1000 or [email protected] Europe, Middle East and Africa: +44 (0) 1753 618000 or [email protected] Asia Pacific: +852 3189 7900 or [email protected]
© Hitachi Data Systems Corporation 2016. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. VSP and Hi-Track are trademarks or registered trademarks of Hitachi Data Systems Corporation. Microsoft, Windows Server, and Internet Explorer are trademarks or registered trademarks of Microsoft Corporation. All other trademarks, service marks, and company names are properties of their respective owners. Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems Corporation. AS-407-01. March 2016.
