Storage Configuration Best Practices for SAP HANA TDI and EMC ScaleIO Converged Infrastructure

White Paper

EMC Solutions

Abstract

This white paper presents a new way to overcome the limitations of traditional SAP HANA appliance-based deployments. It shows how to configure a Tailored Data Center Integration (TDI) solution for HANA based on EMC® ScaleIO® converged storage. This solution provides standard server-based storage for HANA with new levels of flexibility and scalability.

December 2014

STORAGE CONFIGURATION BEST PRACTICES FOR SAP HANA TAILORED DATA CENTER INTEGRATION AND EMC® SCALEIO® CONVERGED INFRASTRUCTURE

Storage Configuration Best Practices for SAP HANA Tailored Data Center Integration and EMC ScaleIO Converged Infrastructure

White Paper

2

Copyright © 2014 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All trademarks used herein are the property of their respective owners.

Part Number H13731

3 Storage Configuration Best Practices for SAP HANA Tailored Data Center Integration and EMC ScaleIO Converged Infrastructure

White Paper

Table of contents

Executive summary ............................................................................................................................... 5 Business case .................................................................................................................................. 5

EMC ScaleIO for HANA TDI ........................................................................................................... 6 EMC and VCE testing ................................................................................................................... 7

Purpose ........................................................................................................................................... 7 Scope .............................................................................................................................................. 7 Audience ......................................................................................................................................... 7

EMC ScaleIO test environment.............................................................................................................. 8 Platform components ....................................................................................................................... 8

Compute ..................................................................................................................................... 8 Network ....................................................................................................................................... 8 Storage ....................................................................................................................................... 9

ScaleIO nodes .................................................................................................................................. 9 Disk types for HANA ......................................................................................................................... 9 HANA persistence volumes .............................................................................................................. 9 HANA shared file system .................................................................................................................. 9 Scale-up and scale-out .................................................................................................................. 10 Scale-up configuration ................................................................................................................... 10 Scale-out configuration .................................................................................................................. 10

Configuration details and recommendations ...................................................................................... 12 Prerequisites .................................................................................................................................. 12 Network configuration .................................................................................................................... 13

VLANs ....................................................................................................................................... 14 Bonding .................................................................................................................................... 15

Installing ScaleIO components ....................................................................................................... 17 Installation procedure ............................................................................................................... 17

Configuring storage ........................................................................................................................ 18 Setting up the ScaleIO cluster ........................................................................................................ 19

Login using SCLI ........................................................................................................................ 19 Install ScaleIO license on MDM cluster ...................................................................................... 19 Prepare the MDM ....................................................................................................................... 19 Create capacity .......................................................................................................................... 20

Tuning the ScaleIO cluster.............................................................................................................. 22 Cache settings ........................................................................................................................... 22 XtremSF PCIe flash card settings................................................................................................ 23 LSI controller and SAS HDD settings .......................................................................................... 24 ScaleIO storage pool configuration ............................................................................................ 26


White Paper

4

Accessing ScaleIO storage from SAP HANA nodes .............................................................................. 31 Enable support for native Linux multipathing in ScaleIO ................................................................ 31 Enable native Linux multipathing on HANA nodes .......................................................................... 31 Format block devices using XFS file system .................................................................................... 32 Mount block devices ...................................................................................................................... 32

Data protection and business continuity ............................................................................................ 33

Conclusion ......................................................................................................................................... 34 Summary ....................................................................................................................................... 34

References.......................................................................................................................................... 35 EMC documentation ....................................................................................................................... 35 SAP documentation ....................................................................................................................... 35

Web resources .......................................................................................................................... 35 Notes: Deployment options ....................................................................................................... 35 Notes: Virtualization .................................................................................................................. 35

Appendix ............................................................................................................................................ 36


White Paper

Executive summary SAP HANA provides organizations with tremendous opportunities to exploit Big Data for competitive advantage. With its massive in-memory processing capabilities, HANA enables applications and analytics to run in real time, accelerating business intelligence and complex computations.

While traditionally deployed only as an appliance, with pre-integrated server, storage, and networking, SAP also has defined an alternative deployment option called Tailored Data Center Integration (TDI). TDI provides organizations with more flexibility to choose the hardware components running HANA.

EMC® ScaleIO® software offers a high-performance, scalable, and cost-effective storage solution for TDI implementations of HANA. ScaleIO enables organizations to use the internal storage on industry-standard servers and create a storage area network (SAN) that provides HANA with shared block storage. Offering flexible deployment options, ScaleIO may be installed on existing application servers in a fully converged manner or on dedicated servers.

With ScaleIO, organizations have much greater flexibility to start with a small HANA implementation and grow as the business requires. ScaleIO also eliminates the need for a large up-front investment in a traditional HANA appliance, and it avoids vendor lock-in over the long term.

EMC and VCE collaborated to test ScaleIO with SAP HANA. These tests were designed to prove that ScaleIO could meet SAP's performance benchmarks. The tests also enabled EMC and VCE to optimize configuration options for the ScaleIO infrastructure and share them with other organizations planning similar implementations.

This white paper describes the test environment we built along with detailed configuration recommendations and best practices for other organizations tasked with deploying ScaleIO for HANA. In addition, this paper includes guidance on how to enable SAP HANA to access ScaleIO storage.

By following the guidance and recommendations in this paper, organizations of all sizes will be well prepared to successfully deploy ScaleIO as a TDI solution for SAP HANA.

SAP HANA is a powerful, in-memory database and application platform that enables breakthrough capabilities for online transactions, predictive analytics, spatial processing, and more.

Traditionally, SAP required HANA to be deployed in an appliance model in which certified compute, storage, and network components are provided in an integrated package. This appliance model, however, locks in organizations to specific vendor hardware and prevents them from using existing resources in their data centers, limiting flexibility and often increasing the cost of HANA adoption.

In response, SAP defined the TDI model for HANA deployment. With TDI, organizations can deploy HANA on SAP-certified servers and on their choice of storage and network devices as long as those devices are supported by SAP.

Business case


White Paper

6

The TDI model enables faster HANA deployment, provides more flexibility to deploy HANA in smaller environments and scale as needed, and eliminates vendor lock-in. This helps organizations reduce time-to-value, lower risk, and trim both capital and operating expenses for HANA.

EMC ScaleIO for HANA TDI

EMC ScaleIO provides an ideal TDI solution for SAP HANA. ScaleIO is a software-only storage area network (SAN) that transforms internal storage on industry-standard servers into global, shared block storage.

ScaleIO provides a single-layer, elastic compute and storage architecture that delivers linear scalability for both SAP and non-SAP applications. As shown in Figure 1, this allows organizations to start with a handful of servers and a few terabytes of capacity and scale the environment up to thousands of servers and multiple petabytes while maintaining consistent performance. In addition, ScaleIO can scale up and scale out using the same underlying architecture to grow SAP HANA in line with an organization's individual needs.

Figure 1. EMC ScaleIO grows in line with your business needs

With ScaleIO, organizations gain all of the performance and capacity they need for SAP HANA. Key advantages include:

• Software-only solution –Delivers the flexibility to grow in line with your business needs

• Hardware agnostic–Provides organizations with choice to select from a list of SAP-certified servers for HANA and modify internal disks as needed

• Deployment flexibility–Installs easily in existing infrastructures or as a greenfield deployment in either physical or virtual environments

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html


White Paper

• Self-managing–Rebalances capacity automatically when servers are added or removed, and self-heals to automatically recover from server or disk failures

EMC and VCE testing

EMC and VCE conducted extensive testing of ScaleIO as a TDI solution for SAP HANA. Based on our tests, we determined the optimal system configurations to meet the key performance indicators (KPIs) that SAP has set for HANA. We used the SAP hardware configuration check tool (HWCCT) to validate these results.

This paper shares the procedures we followed and configurations we tested to demonstrate ScaleIO as a viable TDI solution for HANA. It also includes tips and best practices for other organizations to consider when planning their own deployments. This guidance will help teams deploying ScaleIO to avoid problems and achieve the results they desire.

The purpose of this solution is to demonstrate that EMC ScaleIO converged storage provides a viable alternative to traditional appliance-based SAP HANA deployments. Based on testing conducted by EMC and VCE, the paper presents evidence that ScaleIO offers a highly flexible, scalable, and cost-effective Tailored Data Center Integration (TDI) solution that meets KPIs required by SAP.

In addition, this paper provides detailed configuration information and deployment recommendations intended to help organizations implement ScaleIO successfully as a TDI solution for their SAP HANA environments.

This paper covers the following information:

• Introduces the key solution technologies

• Describes the overall test environment that EMC and VCE built to evaluate ScaleIO with SAP HANA

• Provides detailed configuration information and best practices to set up and fine-tune the ScaleIO environment for HANA

• Offers recommendations on how to access EMC ScaleIO storage from the SAP HANA nodes

• Includes resources for further details

The audience for this paper includes system integrators, systems or storage administrators, customers, partners, and members of EMC Global Services who need to configure EMC ScaleIO in a TDI environment for SAP HANA.

Purpose

Scope

Audience


White Paper

8

EMC ScaleIO test environment EMC and VCE built a test environment for ScaleIO and SAP HANA in a laboratory setting to thoroughly explore the best configurations for meeting the performance required by SAP HANA's unique workload characteristics. The I/O workload on SAP HANA has two major components:

• Random I/O on the data volume

• Sequential I/O on the log volume

In addition, SAP HANA uses different block sizes for log volumes and data volumes. I/O for log volumes uses 4 KB, 16 KB, and 1 MB block sizes. I/O for data volumes uses 4 KB, 16 KB, 64 KB, 1 MB, 16 MB, and 64 MB block sizes.

To simulate the specific SAP HANA I/O workload for these tests, EMC and VCE used the SAP HANA hardware configuration check tool (HWCCT). This tool from SAP verifies that the test results meet the KPIs that SAP set for SAP HANA.

The test environment consisted of Cisco Unified Computing System (UCS) servers with internal storage running HANA and ScaleIO in a Linux operating environment, along with Cisco networking and EMC storage.

EMC and VCE used the following specific components and recommend that organizations adopt these configurations as a best practice for their own tests using ScaleIO for SAP HANA.

Compute

• 4 x Cisco UCS C460 M4 Rack Servers (HANA nodes)1

1 TB RAM

3 x Cisco UCS Virtual Interface Card (VIC) 1225T (10 Gbps dual port PCIe network card)

• 2 x Cisco UCS C240 Rack Servers (ScaleIO management nodes)

96 GB RAM

2 x UCS VIC 1225T 10 Gbps dual port PCIe network card

• Operating environment

SUSE Linux Enterprise Server (SLES) 11 SP3 running on bare metal servers (first build)

Red Hat Enterprise Linux (RHEL) 6.5 running on bare metal (second build)

Network

• 2 x Cisco Nexus 3064-T

1 This document covers tests conducted on physical servers. EMC and VCE plan to conduct additional tests in a VMware virtualized environment.

Platform components

http://service.sap.com/sap/support/notes/1943937


White Paper

Storage

• 8 x 1.2 TB 10K SAS drives per C460 server, with optional 2 x EMC XtremSF™ multi-level cell (MLC) PCIe flash cards

Up to 24 x 1.2 TB 10K SAS drives per C240 server may be used

• Optional VNXe 3300 for central boot volumes, HANA share, backup

ScaleIO requires a minimum of three nodes to accommodate the Metadata Manager (MDM), ScaleIO Data Server (SDS), ScaleIO Data Client (SDC), and a Tie-Breaker (TB). The ScaleIO nodes were configured as follows:

• Node1–MDM, SDS, SDC

• Node2–MDM, SDS, SDC

• Node3–TB, SDS, SDC

Offering flexible deployment options, ScaleIO can be installed on existing application servers in a fully converged manner or on dedicated servers.

EMC and VCE used the following disk configuration for the test ScaleIO environment and recommend this configuration for Scale IO for SAP HANA:

• 10,000 RPM (or faster) SAS disks

• Optional: EMC XtremSF MLC PCIe flash cards to maximize performance by providing a separate disk pool for log volumes

Each SAP HANA worker node requires two volumes to enable database persistence, a data volume, and a log volume. The size of the volumes depends on the RAM size of the HANA node. The SAP HANA Storage Requirements White Paper provides a formula for calculating the appropriate volume (file system) size.

EMC and VCE followed SAP recommended formulas as follows:

• Data size = RAM size * 1

• Log size = RAM size * 1

For high availability, ScaleIO holds two physically separate copies of each volume. EMC and VCE recommend setting aside spare capacity equal to the capacity of a single server (assuming all servers are configured identically). That way, you can automatically rebuild volumes from the copies if a server or disk fails.

The SAP HANA database binaries must be installed on a highly available shared file system. There are several options for building this shared file system, including:

• Deploy a clustered file system (OCFS2) on top of a shared ScaleIO block device

• Configure two ScaleIO nodes as a highly available clustered NFS

• Export an NFS share on an existing storage array

ScaleIO nodes

Disk types for HANA

HANA persistence volumes

HANA shared file system

https://hcp.sap.com/content/dam/website/saphana/en_us/Technology%20Documents/Storage%20Whitepaper%202%204.pdf


White Paper

10

In the test environment, EMC and VCE configured the HANA shared file system as an NFS export on an existing storage array. To size the shared file system, we recommend using the following formula:

# of HANA nodes * RAM size of a single node

EMC and VCE conducted the ScaleIO validation tests in both scale-up and scale-out configurations.

The first test was performed in a single-node scale-up configuration with one terabyte of memory, as shown in Figure 2.

Figure 2. Scale-up configuration used for ScaleIO validation testing

EMC and VCE calculated total disk capacity for this configuration using the following formula:

(1 x 1 TB for data + 1 x 1 TB for log + 1 x 1 TB for shared FS + 0.1 TB for others) x 2 + 15% = 7.13 TB

For this configuration, we set the spare value at 15 percent. Each organization should adjust this setting based on their individual configuration requirements.

The second test was performed in a four-node scale-out configuration with four times one terabyte of memory, as shown in Figure 3.

Scale-up and scale-out

Scale-up configuration

Scale-out configuration


White Paper

Figure 3. Scale-out configuration used for ScaleIO validation testing

EMC and VCE calculated total disk capacity for the scale-out configuration using the following formula:

4 x (1 x 1 TB for data + 1 x 1 TB for log + 1 x 1 TB for shared FS + 0.1 TB for others) x 2 + 15% = 28.52 TB

We set the spare value at 15 percent. Each organization should adjust this setting based on their individual configuration requirements.


White Paper

12

Configuration details and recommendations This section provides configuration details for how EMC and VCE built the ScaleIO test environment. We ran tests using a variety of different configurations for each component to identify which configuration yielded the best overall results.

EMC and VCE determined that the following configurations provide optimal levels of performance, scalability, high availability, and cost for SAP HANA environments. We recommend that other IT organizations use these same configurations for their own HANA TDI environments.

Prior to configuring specific settings for each component, the following tasks should be completed:

• Build the physical cluster

• Install and configure the Linux operating environment (SLES/RHEL) on all nodes in the cluster

• Establish the following network configurations:

10 gigabit network connectivity between all components

Acceptable network bandwidth and latency between all nodes

Ethernet switch that supports bandwidth between network nodes

Consistent maximum transmission unit (MTU) settings across all servers and switches. For jumbo frame support, set the MTU to 9000 bytes for servers, switches, and v-switches.

Open ports in the local firewall of the server:

o MDM—6611 and 9011

o SDS—7072

o Tie-breaker—9011

Implement SAP Note 401162 to avoid problems caused by TCP/IP port conflicts

Note: ScaleIO requires a minimum of three SDS servers, with a combined free capacity of at least 300 gigabytes. These minimum values are true per system and per storage pool. The storage pool must contain devices from at least three different SDS servers to create a volume.

Prerequisites


White Paper

EMC and VCE built a fully configured network between all servers. The network connections were balanced across two Cisco 3064T switches, as shown in Figure 4.

Figure 4. Network configuration used for the ScaleIO build

We installed three UCS VIC 1225T network cards on each UCS C460 server, with each VIC 1225T providing two 10 Gbps interfaces, as shown in Figure 5. In addition, we installed two UCS VIC 1225T cards in each UCS C240 server.

Figure 5. C460 network interfaces

Network configuration


White Paper

14

VLANs

EMC and VCE configured several VLANs in the network for testing:

• VLAN a–Management connection via the Cisco Integrated Management Controller (CIMC)

• VLAN b–Internal HANA traffic (HANA internode)

• VLAN c–Internal ScaleIO traffic (ScaleIO internode)

• VLAN d–Production/customer network

• VLAN e –Core and interconnection Inter-Switch Links (ISLs)

ScaleIO uses VLAN c to communicate between servers in the ScaleIO cluster. The type of information passing between servers includes both management and data traffic. This data is broken into chunks and always written to two physically separate devices on different servers, as shown in Figure 6.

Following an initial test, EMC and VCE added multiple IPs/VLANs to ScaleIO, represented by the red solid lines and green dashed lines.

Figure 6. VLANs


White Paper

We typed the following commands to add and remove additional IPs using the ScaleIO command line interface (SCLI):

scli --add_sds_ip --sds_name StorageN1 --new_sds_ip 172.24.11.40 scli --remove_sds_ip --sds_name SAP_HANA_NODE2 --sds_ip_to_remove 172.24.11.70

The SCLI also makes it easy to view assigned IPs, as shown in Figure 7.

Figure 7. Using the scli command to view assigned IPs

By adding a second IP range to ScaleIO, we reduced the latency (μs) figures for data devices and some other throughput numbers decreased too. Despite the slight decrease, the throughput results were still above the KPIs required by SAP.

Bonding

To maximize bandwidth and high availability for each server, EMC and VCE bonded each interface. Bonding creates a logical interface, usually BONDx, that is linked to two physical interfaces. We tested bonding within both the SLES and RHEL operating environments.

We ran the following commands to bond the interfaces in SLES. The difference between bonding in SLES and RHEL is the syntax of the configuration files.

First, we bonded six Ethernet interfaces available in each C460 server into three different bonds: Bond0, Bond1, and Bond2. This requires knowing which interfaces are connected to which ports on the switch. We then grouped the correct interfaces into pairs, as shown in Figure 6.

In this setup, as shown in Figure 8, each bond had one physical interface connected to switch A, and a second interface connected to switch B. The two physical interfaces are known as slaves.

Figure 8. Slave configuration file in SLES

Each component, including the logical Bond, has its own configuration file in SLES, as shown in Figure 9.


White Paper

16

Figure 9. Bond configuration file in SLES

Network configuration files for SLES are located in /etc/sysconfig/network.

As an example, we created the following configuration files for Bond0:

/etc/sysconfig/network/ifcfg-bond0

/etc/sysconfig/network/ifcfg-eth4

/etc/sysconfig/network/ifcfg-eth5

Figure 9 shows the configuration file for one of the physical slaves.

BONDING_MODULE_OPTS are referenced when the driver for Bond0 is loaded. (See Figure 9.) The miimon=100 value tells the driver to use mii monitoring, watching every 100 milliseconds for a link failure. The mode parameter specifies one of four bonding policies.

Possible mode values include:

• 0 Round-robin policy (default) —Transmit in a sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

• 1 Active-backup policy—Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond’s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance.

• 2 XOR policy—Transmit based on [(source MAC address XOR'd with destination MAC address) module slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.

• 3 Broadcast policy—Transmits everything on all slave interfaces. This mode provides fault tolerance.

EMC and VCE ran tests and measured bandwidth for all of the above options. The default, round-robin configuration provided the best performance.


White Paper

We also used the MTU option, which was set to 9000.

The following ScaleIO components must be installed:

• Meta Data Manager–MDM Configures and monitors the ScaleIO system. Install the MDM in cluster mode, using a primary and secondary MDM, and a tie-breaker on three separate servers. Cluster mode supports redundancy.

• ScaleIO Data Server–SDS Installed on all servers that will contribute storage devices to the ScaleIO system.

• ScaleIO Data Client–SDC Installed on every server that will present ScaleIO volumes to the HANA application running on it.

• Lightweight Installation Agent–LIA (optional) Simplifies future upgrades and enables access to the get-info operation without requiring the operating system passwords of every node.

EMC and VCE set up the lab environment as a six-node cluster with two nodes acting as management nodes (sio-mgmt1, sio-mgmt2) and four nodes running SAP HANA (sio-hana1, sio-hana2, sio-hana3, sio-hana4).

The MDM, SDS, SDC, and tie-breaker components were installed on the following nodes:

• MDM–management nodes sio-mgmt1 (MIP1) and sio-mgmt2 (MIP2). Note that the MDM cluster IP is <IP_CLUSTER>, which is a virtual IP for the MDM.

• SDS–sio-mgmt1 (MIP1), sio-mgmt2 (MIP2), and sio-nodes 1-4

• SDC–sio-nodes 1-4

• Tie-breaker–sio-node1 (IP1)

Installation procedure

The following steps provide a general guideline for installing ScaleIO. We recommend also referring to the complete ScaleIO User Guide on EMC Online Support.

To install ScaleIO:

1. Install the first MDM on a management server.

For example: rpm -i EMC-ScaleIO-mdm-1.30-0.InstallationManager.el6.x86_64.rpm

2. Install the second MDM on a different management server and then install the tie-breaker on a third server.

For example:

rpm –i EMC-ScaleIO-tb-1.30-0.InstallationManager.el6.x86_64.rpm

Installing ScaleIO components

https://support.emc.com/


White Paper

18

3. Install the SDS component on every server that will contribute storage drives to the ScaleIO system.

For example:

rpm –i EMC-ScaleIO-sds-1.30-0.InstallationManager.el6.x86_64.rpm

4. Install the SDC component on every server where the storage volumes need to be presented to the application.

For example:

MDM_IP=<MDM-IP> rpm –i EMC-ScaleIO-sdc-1.30-0.InstallationManager.el6.x86_64.rpm

5. Install the LIA component on every node (optional).

For example:

rpm –i EMC-ScaleIO-lia-1.30-0.InstallationManager.el6.x86_64.rpm

6. Install the GUI where needed.

For example:

rpm -U scaleio-gui-1.30.0-InstallationManager.noarch.rpm

ScaleIO works with any free disk capacity whether internal or direct-attached storage (DAS), including SAS hard disk drives (HDD) or flash-based devices such as solid state drives (SSD) and PCIe cards.

We recommend configuring the raw storage as stand-alone devices (RAID 0) because ScaleIO provides its own meshed-mirroring protection scheme and any additional RAID configuration would negatively impact performance.

If the server has a RAID controller, we encourage using the controller’s caching abilities for better performance. For write caching, the RAID controller must have battery backup to avoid risk of data corruption. For HDD devices, we recommend enabling RAID-controller caching. Configurations vary for flash devices depending on the device behavior. For example, EMC XtremSF MLC PCIe cards require onboard cache for better performance.

When new nodes are added, ScaleIO redistributes data across the nodes to improve network performance. When ScaleIO detects a failure in the storage or network, it creates a new copy of the data in a different location to ensure data integrity.

We recommend using the SCLI to provision and maintain ScaleIO. For configuring and monitoring internal DAS storage, use the vendor-provided tools. The ScaleIO dashboard provides easy management and monitoring of the overall environment, as shown in Figure 10.

Configuring storage


White Paper

Figure 10. ScaleIO dashboard

After installing the ScaleIO components (MDM, SDS, SDC, Tie-breaker), set up the ScaleIO cluster as follows:

• Login using CLI

• Install ScaleIO license on the MDM cluster

• Prepare the MDM

• Create capacity

Login using SCLI

Log in to the management system before performing SCLI commands:

scli --login --username <username> [--password <password>]

The default user password is admin.

Note: For a more secured process, we recommend not adding the password parameter, but instead submitting the command with just the username and letting the system ask for the password. The password will not be displayed and will not be logged in the command history.

Install ScaleIO license on MDM cluster

Using the CLI, type the following command:

scli --query_license scli --set_license --license_file <license_file>

Prepare the MDM

Type the following commands to prepare the MDM:

Setting up the ScaleIO cluster


White Paper

20

1. Define the primary MDM on Management Node 1 (MIP1):

scli --add_primary_mdm --primary_mdm_ip <MIP1> --virtual_IP <MIP_CLUSTER>

2. Define the secondary MDM on Management Node 2 (MIP2:

scli --add_secondary_mdm --mdm_ip <MIP_CLUSTER> --secondary_mdm_ip <MIP2>

3. Define the Tie-breaker on Application Node 1 (IP1):

scli --add_tb tb_ip IP1 --mdm_ip <MIP_CLUSTER>

4. Switch to cluster mode:

scli --switch_to_cluster_mode --mdm_ip <MIP_CLUSTER>

Note: In our lab environment, we set up MDMs on dedicated management servers. MDMs also can run on HANA servers.

Create capacity

Do the following when configuring capacity in ScaleIO. All administration tasks are carried out using SCLI commands performed by the primary MDM.

Capacity configuration sequence

The following descriptions provide guidance for performing each step in creating capacity. For more information, refer to the ScaleIO User Guide.

Add protection domain A protection domain is a subset of SDSs. Create a protection domain named SAP_HANA_PROD1 by typing the following command:

scli --add_protection_domain --mdm_ip <IP_CLUSTER> --protection_domain_name SAP_HANA_PROD1

Add storage pool A storage pool is a subset of SDSs inside a given protection domain. A data volume is allocated across the devices that comprise a storage pool.

Note: Do not mix different disk types such as SAS and SSD in the same storage pool.


White Paper

Create storage pools for the HANA application by typing the following command:

scli --mdm_ip <IP_CLUSTER> --add_storage_pool --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1

Next, add an SDS and its devices to the SAP_HANA_PROD1 storage pool SAP_HANA_SAS1 by typing the following commands:

scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-MGMT1 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1

scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-MGMT2 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1 scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-HANA1 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1 scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-HANA2 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1 scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-HANA3 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1 scli --add_sds --mdm_ip <IP_CLUSTER> --sds_ip IP1 --device_name </dev/d1>,</dev/d2>,</dev/d3>,</dev/d4> --sds_name SIO-HANA4 --storage_pool_name SP_HANA_SAS1 --protection_domain_name SAP_HANA_PROD1

Type the following command to add more devices to a storage pool for an SDS at a later time:

scli --add_sds_device --sds_ip <IP1> --protection_domain_name SAP_HANA_PROD1 --storage_pool_name SP_HANA_SAS1 --device_name /dev/d5

Type the following command to remove devices from a storage pool for an SDS:

scli --remove_sds_device --sds_ip <IP1> --protection_domain_name SAP_HANA_PROD1 --storage_pool_name SP_HANA_SAS1 --device_name /dev/d4

Create and map volumes to SDC With ScaleIO, users can easily define volumes and share them between many SDCs by simply designating which SDCs can access the given volumes. This does the following:


White Paper

22

• Exposes access control per volume

• Explicitly maps volumes to HANA nodes in the cluster

After a volume is mapped to an SDC, it immediately gets access to the volume and exposes it locally to the applications as either a standard block device or as an iSCSI device for VMware configurations. The devices appear as /dev/sciniX where X is a letter, such as /dev/scinia or /dev/scinib.

The following steps provide guidance for creating and mapping volumes.

1. Define a 1024 GB volume and name it HANA_VOL_DATA1 by typing the following command:

scli --add_volume --mdm_ip <IP_CLUSTER> --size_gb 1024--volume_name HANA_VOL_DATA1 --storage_pool_name SP_HANA_SAS1 --protection_domain_name HANA_PROD

2. Map HANA_VOL_DATA1 to the SDC on IP1, by typing the following command:

scli --map_volume_to_sdc --mdm_ip <IP_CLUSTER> --volume_name HANA_VOL_DATA1 --sdc_ip <SDC_IP1>

The same volume can be mapped to multiple SDCs, but only one SDC can use this volume at a time due to potential data corruption.

Volumes can be unmapped and removed from and SDC by typing the following commands if needed:

scli --unmap_volume_from_sdc --sdc_ip <SDC_IP1> --volume_name HANA_VOL_DATA1 scli --remove_volume --volume_name HANA_VOL_DATA1

Adding multiple IPs to SDS SDS supports up to eight IP addresses, which boosts performance and provides redundancy in case of a link failure. To configure SDS nodes with more than one IP, type the following command:

scli --mdm_ip 172.24.12.250 --add_sds_ip --sds_name SIP_HANA1 --new_sds_ip 172.24.11.10

Detect the volume ScaleIO periodically scans the system to detect new volumes mapped to an SDC. For the most up-to-date status on a particular SDC node, you can also initiate a scan.

After the ScaleIO cluster was set up, EMC and VCE fine-tuned the cluster as follows. Other IT organizations also can use this information as a guide to optimize ScaleIO cluster performance in their HANA environments.

Cache settings

The SAS drive configuration used in our ScaleIO test environment met the SAP KPIs for productive HANA systems. To boost performance even higher, organizations can

Tuning the ScaleIO cluster


White Paper

add pools for log volumes using EMC XtremSF MLC PCIe flash cards or SSDs. We successfully optimized these disk types by using the following settings.

• XtremSF write cache setting:

The write cache setting internal to the P320h (SLC) and P420m (MLC) can be enabled or disabled on the P320h only using RealSSD Manager. It is important to be aware that unexpected power loss may cause data loss in the write cache if this setting is enabled. The internal drive setting on the P420m is enabled by default and cannot be changed. The P420m supports power holdup protection, which protects data during an unexpected power loss.

• ScaleIO SSD configuration optimization:

To improve SSD performance, type the following settings into the /opt/scaleio/ecs/sds/cfg/conf.txt file on each SDS node:

tgt_net__recv_buffer=4096 tgt_net__send_buffer=4096 tgt_cache__size_mult=3 tgt_thread__ini_io=500 tgt_thread__tgt_io_main=500 tgt_umt_num=1200 tgt_umt_os_thrd=6 tgt_net__worker_thread=6 tgt_asyncio_max_req_per_file=400

Restart the SDS by typing the following command on each node:

# pkill sds

XtremSF PCIe flash card settings

We used Micron Technology's RealSSD Manager utility to fine-tune settings on each XtremeSF PCIe flash card, as shown in Figure 11.

To launch the RealSSDManager, type the following command. The tool must first be downloaded and installed from the Micron Technology website.

/opt/MicronTechnology/RealSSDManager #java –jar RealSSDManager.jar


White Paper

24

Figure 11. XtremeSF summary screen using RealSSD Manager utility

We achieved the best results and lowest latency when using the XtremeSF MLC cards as LOG volumes in SLES and the ScaleIO storage configuration. After testing all the options in Device > Interrupt Coalescing, we were able to optimize latency by selecting the Latency Sensitive value instead of the default High IOPs setting, as shown in Figure 12.

Figure 12. Interrupt coalescing

LSI controller and SAS HDD settings

For the SAS HDD storage, we fine-tuned the environment with the following settings:

• Server–C460 M4

• Controller –LSI MegaRAID 9361-8i

• Drives–1.2 TB 6 Gb SAS 10K RPM SFF HDD

The 9361-8i RAID controller card features a low-profile PCI express form factor with one GB of cache, with 16 MB of flash ROM for firmware and 32 KB of non-volatile random-access memory (NVSRAM) for storing RAID configurations.


White Paper

There are a number of tools available to configure the LSI controller2, such as a WebBIOS configuration tool, a command line tool, or a storage manager graphical utility.3 We used the following command line tool to look through the values and chose the default settings as the best option.

#/opt/MegaRAID/MegaCli/MegaCli64 –AdpAllinfo –aALL | more

Note: The Appendix provides more information about the LSI 9361-81 settings.

We installed eight SAS drives (HDD) per C460 M4, which is the maximum supported with the LSI controller. Other than the Boot HDD and associated Mirror HDD, we did not configure any other RAID type using the LSI controller.

We configured a number of optimization settings on the HDDs and applied those settings to all drives in the ScaleIO build. EMC and VCE determined that it is critical for all HDDs in ScaleIO to be identically configured. An incorrectly configured HDD will affect the performance of the entire ScaleIO storage pool.

We used the following storcli commands to change the cache settings relating to read and write cache from RWBD to HRWTD.

#./storcli64 /c0/v6 set wrcache=wb #./storcli64 /c0/v6 set rdcache=RA

The specific changes included:

Original Revised

NR–No Read Ahead RW–ReadWrite

WT–Write Through B–Blocked

D–Direct D–Direct

Type the following storcli command to display the controller and drive settings:

#/opt/MegaRAID/storcli

We found that making these changes to the settings provided the best performance during testing.4 Figure 13 displays storcli commands before typing this command and Figure 14 displays storcli commands after running the command.

2 Refer to the LSI 9361-8i MegaRAID Manual 3 MegaRAID SAS Software User Guide provides further details on how to administer the Controller and HDDs. 4 All LSI commands were run in SLES


White Paper

26

Figure 13. Storcli commands (before)

Figure 14. Storcli commands (after)

ScaleIO storage pool configuration

EMC and VCE tested various pool configurations using the SAP HWCCT. We evaluated different pool sizes, numbers of pools, HDD settings, and number of HDDs, among other configurations. Our objective was to find the optimum configuration for meeting SAP's KPIs, and to provide guidance for the wider community on best-practice ScaleIO configurations.


White Paper

We performed tests that used internal SAS drives exclusively (SAS HDD configuration), as well as tests combining SAS storage pools with XtremSF (SSD and SAS configuration).

All SAS HDD configuration For tests running on internal SAS drives exclusively, we used the following configuration, as shown in Figure 15:

• 4 x C460 M4 servers, 1TB RAM

• HANA 3+15 scale-out build

• DATA and LOG volumes on SAS HDDs

• One ScaleIO Storage Pool

Figure 15. All-SAS drive configuration

We used the following formula to size HANA in this configuration:

• DATA device 1 x RAM

• LOG device 1 x RAM

We built a single storage pool with six SAS HDDs from each C460 M4. We also built three sets of DATA and LOG volumes as this use case was based on a 3+1 HANA scale-out configuration. Each server had a DATA volume and a LOG volume assigned and mounted from the ScaleIO pool (hana1, hana2 and hana3). Figure 16 displays details.

5 3+1 consists of a HANA Standby Server, even though for ScaleIO it is fully functional.


White Paper

28

Figure 16. SDS View/List

We configured four SDSs within ScaleIO using C460 Cisco servers. You can add multiple IP backbones to the ScaleIO SDSs to help balance ScaleIO traffic and increase performance.

For this use case, we found the best configuration was a single IP address/backbone for ScaleIO traffic, as shown in Figure 16. When adding an additional IP backbone to ScaleIO, tests resulted in lower latency on LOG volumes, but also decreased KPIs such as read throughput on both DATA and LOG volumes.

To achieve the required KPIs, we provided at least one additional server in the ScaleIO cluster to run ScaleIO-related operations exclusively. For example, if six HANA servers/nodes are required, use seven servers instead. This model fits perfectly in a scale-out HANA build where the additional server can function as a HANA standby server. The standby in HANA will not have a DATA or LOG volume mounted until there is a failure and HANA high availability is required.

If greater performance is required, you can expand the ScaleIO storage pool with additional HDDs. Another option is to add servers, such as the C240 management servers, as shown in Figure 17. Adding servers helps improve throughput and IOPS by increasing the number of available HDDs in the storage pool, as well as the number of servers in the storage pool and ScaleIO cluster.

Note: The performance in any given storage pool is only as fast as the slowest component and mixing drive types, or adding drives from faster and slower servers, may not achieve the desired results.


White Paper

Figure 17. Adding an additional SDS and expanding the storage pool

If an additional server is added, an SDS should be installed on it. Type the following command to add the SDS:

#scli --add_sds --sds_ip 172.24.12.90 --protection_domain_name SAP_HANA --device_name /dev/sde --storage_pool_name SAP_HANA_SP_SAS --sds_name NODE4 –force_clean

SSD (XtremSF) and SAS drive configuration For the tests using internal SAS drives with XtremSF flash drives, we used the following configuration:

• 4 x C460 M4 servers, 1 TB RAM

• HANA 3+16 scale-out build

• DATA volumes on SAS HDDs

• LOG volumes on XtremeSF PCIe cards

• 1 x ScaleIO "SAS" Pool for SAS HDDs

• 1 x ScaleIO SSD Pool for XtremSF PCIe cards

We used the following sizing formula for HANA:

• DATA device 1 x RAM

• LOG device 1 x RAM

To achieve higher performance with very low latencies for the LOG volumes, we could have used either SSDs or PCIe flash cards. The disadvantage of using SAS-based

6 3+1 consists of a standby server, the +1 (HANA).


White Paper

30

SSDs is that they use HDD positions, and the C460 M4 is limited to eight HDDs from the LSI controller. As a result, we selected a PCIe-based solution.

The C460 M4 by default is equipped with a single carrier and five PCIe slots. For additional slots, purchase a second inexpensive carrier for a total of ten PCIe slots. We added two XtremSF cards to each of the four C460 servers.

For this ScaleIO cluster, we used two storage pools, one consisting of SAS HDDs to hold the DATA volumes and the other consisting of the XtremSF PCIe cards to hold the LOG volumes, as shown in Figure 18. The storage pool using the PCIe cards yielded much lower latency.

Figure 18. SAS and XtremSF configuration

We tested both SLC-based and MLC-based cards. Both passed the SAP benchmarks, where latency for LOG volumes is a prime KPI. The SLC-based XtremSF cards were faster than the MLC-based cards, but the cost of SLC versus MLC is also greater.


White Paper

Accessing ScaleIO storage from SAP HANA nodes In this section, EMC and VCE provide guidance on how to enable SAP HANA nodes to access ScaleIO storage. To be successful, all ScaleIO volumes must be mapped to all HANA nodes in the cluster as described in the previous sections.

ScaleIO must first be configured to support native Linux multipathing. Type the following entries in the /etc/udev/rules.d/20-scini.rules file:

KERNEL=="scini*[!0-9]", SUBSYSTEM=="block", PROGRAM="/bin/emc/scaleio/drv_cfg --query_block_device_id --block_device $tempnode", SYMLINK+="disk/by-id/emc-vol-%c", ENV{ID_BUS}="scsi", ENV{ID_SERIAL}="%c" KERNEL=="scini*[!0-9]", SUBSYSTEM=="block", PROGRAM="/bin/emc/scaleio/drv_cfg --query_block_device_id --block_device $tempnode", SYMLINK+="disk/by-id/scsi-%c", ENV{ID_BUS}="scsi", ENV{ID_SERIAL}="%c" ACTION=="add", DEVPATH=="*scini*[!0-9]", RUN+="/bin/sh -c 'echo noop > /sys$DEVPATH/queue/scheduler'" ACTION=="add", DEVPATH=="*scini*[!0-9]", RUN+="/bin/sh -c 'echo 1024 > /sys$DEVPATH/queue/max_sectors_kb'" ACTION=="add", DEVPATH=="*scini*[!0-9]", RUN+="/bin/sh -c 'echo 512 > /sys$DEVPATH/queue/nr_requests'

Next, enable native Linux multipathing on the HANA nodes so they can access the block device volumes on ScaleIO. Use the following procedure and commands to enable native Linux multipathing on a HANA node:

1. Create an /etc/multipath.conf file. Use the following example for ScaleIO volumes:

defaults { user_friendly_names no

}

2. After creating the configuration file, restart the multipath daemon to activate the settings and rescan the new devices:

# rescan-scsi-bus.sh # service multipathd stop # service scini restart # service multipathd start

The HANA persistence device should now be visible.

Type the following commands and ensure that all ScaleIO devices are visible:

# ls -l /dev/mapper/* # ls -l /dev/dm-* # cat /proc/partitions, # dmsetup table –v

Enable support for native Linux multipathing in ScaleIO

Enable native Linux multipathing on HANA nodes


White Paper

32

3. Type the following command to verify that all multipath devices are present:

server01:~ # multipath –ll

The following output displays the status of the devices:

25e8b72d4664fcaeceb8c222800000007 dm-7 , size=500G features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active `- #:#:#:# scinia 251:0 active ready running 25e8b72d4664fcaeceb8c222600000006 dm-9 , size=600G features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active `- #:#:#:# scinib 251:16 active ready running

To list only ScaleIO multipath devices, type the following command:

# multipath -ll|grep scini -B 4

Note: The Linux storage administration guide provides additional details on how to enable DM-MPIO on a HANA node.

EMC strongly recommends using XFS as the file system for the HANA block devices. To format a ScaleIO block device with the XFS file system, type the following command on the HANA node:

$ mkfs.xfs /dev/mapper/25e8b72d4664fcaeceb8c222800000007

Note: Run this command for all HANA application volumes in a ScaleIO cluster.

In a HANA scale-out environment with worker and standby nodes, the SAP HANA Storage Connector API for Fibre Channel (fcClient.py) mounts and unmounts the devices to the HANA nodes.

In addition to mounting the devices, the Storage Connector API also writes SCSI-3 PGR reservations to the devices using the Linux sg_persist command. This is called I/O fencing and ensures that only one HANA node at a time can access a set of DATA and LOG devices.

The Storage Connector API is controlled in the storage section of the SAP HANA global.ini file. The following is an example of a global.ini file:

[persistence] basepath_datavolumes=/hana/data/ANA basepath_logvolumes=/hana/log/ANA use_mountpoints = yes

[storage] ha_provider = hdb_ha.fcClient partition_*_*__prType = 5 partition_*_data__mountOptions = -o relatime,inode64 partition_*_log__mountOptions = -o relatime,inode64,nobarrier partition_1_data__wwid = 25e8b72d4664fcaeceb8c222300000003 partition_1_log__wwid = 25e8b72d4664fcaeceb8c222600000006 partition_2_data__wwid = 25e8b72d4664fcaeceb8c222400000004

Format block devices using XFS file system

Mount block devices


White Paper

partition_2_log__wwid = 25e8b72d4664fcaeceb8c222800000007 partition_3_data__wwid = 25e8b72d4664fcaeceb8c222400000005 partition_3_log__wwid = 25e8b72d4664fcaeceb8c222800000008

The storage section of the global.ini file contains entries for the block devices with optional mount options. For the XFS devices, use the following mount options:

• Relatime

• nobarrier (approved from SAP) only for Log devices

• inode64

Data protection and business continuity You can use several options to protect data in a ScaleIO cluster for SAP HANA,. One option is to use standard SAP tools and procedures (such as HANA Studio) to save data on a shared backup file system or on EMC Data Domain® deduplication storage systems.

For the strongest protection and greatest efficiency, EMC recommends backing up HANA using EMC Networker® with backup integration and EMC Data Domain and Data Domain Boost software.

To enable high availability, EMC ScaleIO 1.3 supports SAP HANA Host Autofailover for physical servers.

SAP HANA System Replication provides disaster tolerance.


White Paper

34

Conclusion

Using EMC ScaleIO for a TDI deployment of SAP HANA provides many benefits, including reduced hardware and operational costs, lower risks, and increased hardware vendor flexibility for applications from SAP as well as other vendors.

The tests conducted by EMC and VCE showed how ScaleIO delivers high performance and fulfills SAP's KPIs for HANA TDI implementations. With ScaleIO as a HANA TDI solution, you can start small and scale in line with your business needs.

EMC ScaleIO is also extremely versatile. You can choose from a broad list of SAP certified servers for HANA, configure physical as well as virtual systems, and run scale-up and scale-out HANA environments all using the same architecture. In addition, ScaleIO can be installed directly in an existing infrastructure, as well as in greenfield environments.

When configured according to the recommendations and best practices presented in this paper, ScaleIO makes it easy to adopt SAP HANA in a TDI configuration. For additional expertise, EMC Global Services provides a comprehensive range of consulting, installation, and support capabilities to minimize risk and maximize return on investment from this solution.

With ScaleIO, organizations have a flexible, cost-effective solution to get the most value from SAP HANA.

Summary


White Paper

References

Find these additional resources on EMC Online Support:

• EMC ScaleIO user guide, release notes, FAQs

The following documentation is available from SAP:

• SAP HANA Server Installation Guide

Web resources

• SAP HANA Platform

• Overview - SAP HANA tailored data center integration

Note: The following documentation requires an SAP username and password.

Notes: Deployment options

• Note 800326—Certified EMC solutions for Linux environments

Notes: Virtualization

• Note 1788665—SAP HANA running on VMware vSphere VMs

EMC documentation

SAP documentation

https://support.emc.com/

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

http://help.sap.com/hana_appliance

http://www.saphana.com/docs/DOC-3633

http://service.sap.com/sap/support/notes/800326

https://service.sap.com/sap/support/notes/1788665


White Paper

36

Appendix LSI MegaRAID 9361-8i RAID Controller settings

Settings

Predictive Fail Poll Interval : 300sec

Interrupt Throttle Active Count : 16

Interrupt Throttle Completion : 50us

Rebuild Rate : 30%

PR Rate : 30%

BGI Rate : 30%

Check Consistency Rate : 30%

Reconstruction Rate : 30%

Cache Flush Interval : 4s

Max Drives to Spinup at One Time : 2

Delay Among Spinup Groups : 12s

Physical Drive Coercion Mode : 1GB

Cluster Mode : Disabled

Alarm : Enabled

Auto Rebuild : Enabled

Battery Warning : Enabled

Ecc Bucket Size : 15

Ecc Bucket Leak Rate : 1440 Minutes

Restore HotSpare on Insertion : Disabled

Expose Enclosure Devices : Enabled

Maintain PD Fail History : Disabled

Host Request Reordering : Enabled

Auto Detect BackPlane Enabled : SGPIO/i2c SEP

Load Balance Mode : Auto

Use FDE Only : Yes

Security Key Assigned : No

Security Key Failed : No

Security Key Not Backedup : No

Default LD PowerSave Policy : Controller Defined

Maximum number of direct attached drives to spin up in 1 min : 10

Auto Enhanced Import : Yes


White Paper

Any Offline VD Cache Preserved : No

Allow Boot with Preserved Cache : No

Disable Online Controller Reset : No

PFK in NVRAM : No

Use disk activity for locate : No

POST delay : 90 seconds

BIOS Error Handling : Ignore Errors

Current Boot Mode :Normal

Capabilities

================

RAID Level Supported : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span

Supported Drives : SAS, SATA

Limitations

================

Max Arms Per VD : 32

Max Spans Per VD : 8

Max Arrays : 128

Max Number of VDs : 64

Max Parallel Commands : 928

Max SGE Count : 60

Max Data Transfer Size : 8192 sectors

Max Strips PerIO : 42

Max LD per array : 64

Min Strip Size : 64 KB

Max Strip Size : 1.0 MB

Max Configurable CacheCade Size: 0 GB

Current Size of CacheCade : 0 GB

Current Size of FW Cache : 837 MB

Supported Adapter Operations

================

Rebuild Rate : Yes


White Paper

38

CC Rate : Yes

BGI Rate : Yes

Reconstruct Rate : Yes

Patrol Read Rate : Yes

Alarm Control : Yes

Cluster Support : No

BBU : Yes

Spanning : Yes

Dedicated Hot Spare : Yes

Revertible Hot Spares : Yes

Foreign Config Import : Yes

Self Diagnostic : Yes

Allow Mixed Redundancy on Array : No

Global Hot Spares : Yes

Deny SCSI Passthrough : No

Deny SMP Passthrough : No

Deny STP Passthrough : No

Support Security : Yes

Snapshot Enabled : No

Support the OCE without adding drives : Yes

Support PFK : Yes

Support PI : Yes

Support Boot Time PFK Change : No

Disable Online PFK Change : No

Support LDPI Type1 : No



PFK TrailTime Remaining : 0 days 0 hours

Support Shield State : Yes

Block SSD Write Disk Cache Change: Yes

Support Online FW Update : Yes

Supported VD Operations

================


White Paper

Read Policy : Yes

Write Policy : Yes

IO Policy : Yes

Access Policy : Yes

Disk Cache Policy : Yes

Reconstruction : Yes

Deny Locate : No

Deny CC : No

Allow Ctrl Encryption: No

Enable LDBBM : No

Support Breakmirror : No

Power Savings : No

Default Settings

================

Phy Polarity : 0

Phy PolaritySplit : 0

Background Rate : 30

Strip Size : 64kB

Flush Time : 4 seconds

Write Policy : WT

Read Policy : None

Cache When BBU Bad : Disabled

Cached IO : No

SMART Mode : Mode 6

Alarm Disable : Yes

Coercion Mode : 1GB

ZCR Config : Unknown

Dirty LED Shows Drive Activity : No

BIOS Continue on Error : 2

Spin Down Mode : None

Allowed Device Type : SAS/SATA Mix

Allow Mix in Enclosure : Yes

Allow HDD SAS/SATA Mix in VD : Yes


White Paper

40

Allow SSD SAS/SATA Mix in VD : Yes

Allow HDD/SSD Mix in VD : No

Allow SATA in Cluster : No

Max Chained Enclosures : 16

Disable Ctrl-R : No

Enable Web BIOS : No

Direct PD Mapping : No

BIOS Enumerate VDs : Yes

Restore Hot Spare on Insertion : No

Expose Enclosure Devices : Yes

Maintain PD Fail History : No

Disable Puncturing : No

Zero Based Enclosure Enumeration : No

PreBoot CLI Enabled : No

LED Show Drive Activity : No

Cluster Disable : Yes

SAS Disable : No

Auto Detect BackPlane Enable : SGPIO/i2c SEP

Use FDE Only : Yes

Enable Led Header : No

Delay during POST : 0

EnableCrashDump : No

Disable Online Controller Reset : No

EnableLDBBM : No

Un-Certified Hard Disk Drives : Allow

Treat Single span R1E as R10 : No

Max LD per array : 64

Power Saving option : Don't Auto spin down Configured Drives

Max power savings option is not allowed for LDs. Only T10 power conditions are to be used.

Default spin down time in minutes: 30

Enable JBOD : Yes

TTY Log In Flash : Yes

Auto Enhanced Import : Yes

BreakMirror RAID Support : No


White Paper

Disable Join Mirror : Yes

Enable Shield State : Yes

Time taken to detect CME : 60s

Storage Configuration Best Practices for SAP HANA TDI and EMC ScaleIO Converged Infrastructure

Documents

Transcript of Storage Configuration Best Practices for SAP HANA TDI and EMC ScaleIO Converged Infrastructure