PURE STORAGE FOR SAP HANA

Transcription

1 WHITE PAPER PURE STORAGE FOR SAP HANA SETUP AND BEST PRACTICES GUIDE

2 TABLE OF CONTENTS SUMMARY... 3 GOALS AND OBJECTIVES... 4 AUDIENCE... 4 PURE STORAGE INTRODUCTION... 4 FlashArray//X Specifications... 6 Purity Operating Environment... 7 Pure Evergreen Storage... 8 OPERATING SYSTEM... 9 SAP HANA SHARED FILE SYSTEM... 9 SOLUTION ARCHITECTURE (SUGGESTED) Network configuration Pure Storage Configuration LUN Configuration NFSv3 Setup Purity RUN Platform CREATING NFS SHARES ON WFS QOS Always-On QoS Performance Classes Performance Limits Configuration of udev Rules Multipathing Configuration HANA Configuration Files SAP HANA SAP HANA CONCLUSION REFERENCES

3 SUMMARY The SAP HANA database takes advantage of main memory (RAM) and the data processing capabilities of multicore processors to deliver better performance for analytical and transactional applications. It offers a multi-engine query processing environment that allows it to support relational data (with both row- and columnoriented physical representations in a hybrid engine) as well as graph and text processing for semi-structured and unstructured data management within the same system. The SAP HANA database is 100% compliant with atomicity, consistency, isolation, and durability (ACID) requirements. The performance of the underlying infrastructure, and in particular storage performance, is the key issue that can hold back a HANA project. Traditional diskbased storage cannot meet the performance needs of HANA and is inherently too complicated to manage. However, the all-flash Pure Storage FlashArray//X can. It delivers not only the required performance, but also the resiliency and management simplicity required by SAP HANA environments at a cost that is often lower than that of disk-based and hybrid arrays. For more information about SAP HANA, go to the SAP help portal. Enterprises running SAP HANA on the certified Pure Storage platform can benefit in the following ways: High performance storage with sub-millisecond latency Highly efficient data reduction (inline compression and de-duplication) Six 9s high availability with no single points of failure Simplified management with rapid provisioning and replication capabilities There are two ways to implement SAP HANA: An Appliance option, where customers can purchase pre-configured systems for their HANA implementation. These configurations often tend to be less flexible, as they come with fixed server, storage, and network components. The SAP HANA Tailored Datacenter Integration (TDI) option, where customers can choose their server, storage, and network components as long as they are all certified by SAP. Customers often prefer this option, as they can leverage existing server, storage, and networking infrastructure for their SAP HANA implementation. The Pure Storage FlashArray//X10 series has been validated as a certified SAP HANA hardware platform as per SAP s Certified Enterprise Storage: HANA-HWC-ES 1.1 program. Customers can use the Pure Storage FlashArray//X series as a part of their SAP HANA TDI implementation. 3

4 GOALS AND OBJECTIVES The purpose of this document is to describe a test plan and best practices for deploying a high performance SAP HANA environment with a Pure Storage FlashArray//X. This document will serve a guide for customers going through the process of configuring HANA clusters, underlying file systems, and storage area networks for HANA. AUDIENCE This document is intended for database administrators (DBAs), storage administrators, system administrators, and anybody who wants to build an SAP HANA environment on a Pure Storage FlashArray with the best results. This is a technical paper that assumes familiarity with SAP HANA administration as well as basic Linux system and storage administration tasks as required for a typical database installation, i.e., setting up file systems, LUN configuration, etc. PURE STORAGE INTRODUCTION Who knew that moving to all-flash storage could help reduce the cost of IT? FlashArray makes server and workload investments more productive, while also lowering storage spend. With FlashArray, organizations can dramatically reduce the complexity of storage to make IT more agile and efficient, thus accelerating the journey to the cloud. FlashArray s performance can also make your business smarter by unleashing the power of real-time analytics, driving customer loyalty, and creating new, innovative customer experiences that simply weren t possible with disk. FlashArray enables you to transform your data center, cloud, or entire business with an affordable all-flash array capable of consolidating and accelerating all your key applications. Pure Storage FlashArray//X is the world s first enterprise-class, all-nvme flash storage array. It represents a new class of storage shared accelerated storage (which is a term coined by Gartner) that delivers major breakthroughs in performance, simplicity, and consolidation of mixed workloads. With latency as low as 250 μs, the FlashArray//X all-nvme architecture brings new levels of performance to mission-critical business applications. With built-in Purity ActiveCluster, more applications can now benefit from the simple to deploy, always-on business continuity provided via active/active metro stretch clustering. Pure DirectFlash with 100% NVMe also enables unprecedented performance density: //X currently supports ultra-dense 18.3TB DirectFlash modules, for maximum density with full performance. In addition, Purity s QoS features mean you can consolidate radically diverse applications without fear of I/O contention. 100% NVME PERFORMANCE As low as 250 µs latency Up to 600,000 32K IOPS Up to 18.5 GB/s bandwidth 4

5 Up to 2x faster than previous gen AFAs NVMe DirectFlash architecture NVMe-oF-ready EFFICIENT & AFFORDABLE Industry-leading 5:1 data reduction, 10:1 total efficiency Very efficient: consumes ~1kW of power 6 cables All array software included ULTRA-DENSE CONSOLIDATION 3PBs effective in 6U Upgrade controllers and drives to expand performance and/or capacity Proven FlashArray % availability plus always-on QoS ULTIMATE SIMPLICITY Plug-and-go deployment that takes minutes, not days Non-disruptive upgrades and hot-swap everything REST API for cloud orchestration AI-driven management and predictive support FlashArray//X expands upon FlashArray s modular, stateless architecture, which is designed to enable expandability and upgradability for generations. FlashArray leverages a chassis-based design with customizable modules, enabling both capacity and performance to be independently improved over time with advances in compute and flash, to meet your business needs today and tomorrow. Pure Storage FlashArray is ideal for: Accelerating Databases and Applications Speed transactions by up to 10x with consistent low latency, enable online data analytics across wide datasets, and mix production, analytics, dev/test, and backup workloads without fear. Virtualizing and Consolidating Workloads Easily accommodate the most IO-hungry Tier 1 workloads, increase consolidation rates (thereby reducing servers), simplify VI administration, and accelerate common administrative tasks. Delivering the Ultimate Virtual Desktop Experience Support demanding users with better performance than physical desktops, scale without disruption from pilot to >1000s of users, and experience all-flash performance for under $100/desktop. Protecting and Recovering Vital Data Assets Deliver always-on protection for business-critical data, maintain performance even under failure conditions, and recover instantly with Purity Protect. 5

6 Pure Storage FlashArray sets the benchmark for all-flash enterprise storage arrays. It delivers: Consistent Performance FlashArray delivers consistent <1ms average latency. Performance is optimized for realworld applications workloads that are dominated by I/O sizes of 32K or larger, rather than the 4K/8K hero performance benchmarks. Full performance is maintained even during failures and updates. Lower Cost than Disk Inline de-duplication and compression deliver 5 10x space savings across a broad set of workloads, including databases, virtual machines, and virtual desktop infrastructure. Mission-Critical Resiliency FlashArray delivers > % proven availability, as measured across the entire FlashArray installed base, offering non-disruptive operations and rich data services that do not affect performance. Disaster Recovery Built-In FlashArray offers native, fully-integrated, data reduction-optimized backup and disaster recovery at no additional cost. Setup disaster recovery with policy-based automation in minutes. And, recover instantly from local, space-efficient snapshots or remote replicas. Simplicity Built-In FlashArray offers game-changing management simplicity that makes storage installation, configuration, provisioning, and migration a snap. No more managing performance, RAID, tiers, or caching. Achieve optimal application performance without any tuning at any layer. Manage FlashArray the way you like it: web-based GUI, CLI, VMware vcenter, Rest API, or OpenStack. FlashArray//X Specifications CAPACITY CONFIGURATION OPTIONS FlashArray//X controllers are designed to support both all-nvme DirectFlash modules and classic SATA/SAS Flash Modules simultaneously making upgrades and expansion easy. Both the DirectFlash NVMe Shelf and the classic SAS Expansion Shelf can be used with //X. DIRECTFLASH CAPACITY PACKS 2.2 TB DirectFlash Modules 4.5 TB DirectFlash Modules 9.1 TB DirectFlash Modules 18.3 TB DirectFlash Modules IN AN //X CHASSIS (10 MODULES) 22 TB 45 TB 91 TB 183 TB IN A DIRECTFLASH SHELF (14 MODULES) 31TB 63 TB 127 TB 256 TB CLASSIC SATA/SAS CAPACITY PACKS 512 GB Flash Modules 1 TB / 960 GB Flash Modules 2 / 1.9 TB Flash Modules 3.8 TB Flash Modules 7.6 TB Flash Modules IN AN //X CHASSIS (10 MODULES) 5 TB 10 TB 20 TB 38 TB 76 TB IN A SAS SHELF (12 MODULES) 11 TB 22 TB 45 TB 90 TB 6

7 TECHNICAL SPECIFICATIONS* //X10 //X20 //X50 //X70 //X90 DIRECT FLASH SHELF CAPACITY Up to 55 TB / 53.5 TiB effective capacity** Up to 20 TB / 18.6 TiB raw capacity Up to 275 TB / TiB effective capacity** Up to 87 TB / 80.3 TiB raw capacity Up to 650 TB / TiB effective capacity** Up to 183 TB / 171 TiB raw capacity Up to 1.3 PB / TiB effective capacity** Up to 366 TB / TiB raw capacity Up to 3 PB / TiB effective capacity** Up to 878 TB / TiB raw capacity Up to 1.9 PB effective capacity** Up to 512 TB / TiB raw capacity Purity Operating Environment PHYSICAL 3U Watts (nominal peak) 95 lbs (43.1 kg) fully loaded 5.12 x x chassis 3U Watts (nominal peak) 95 lbs (43.1 kg) fully loaded 5.12 x x chassis 3U Watts (nominal peak) 95 lbs (43.1 kg) fully loaded 5.12 x x chassis 3U Watts (nominal peak) 97 lbs (44.0 kg) fully loaded 5.12 x x chassis 3U 6U Watts (nominal peak) 97 lbs (44 kg) fully loaded 5.12 x x chassis 3U Watts (nominal peak) 87.7 lbs (39.8kg) fully loaded 5.12 x x chassis Purity implements advanced data reduction, storage management, and flash management features. All features of Purity are included in the base cost of FlashArray//X. //X CONNECTIVITY Onboard Ports (per controller) 2 x 1/10/25 Gb Ethernet 2 x 1/10/25 Gb Ethernet Replication 2 x 1Gb Management Ports Host I/O Cards (3 slots/controller) 2-port 10GBase-T Ethernet 2-port 1/10/25 Gb Ethernet 2-port 40 Gb Ethernet 2 Port 50Gb Ethernet (NVMe-oF Ready)*** 2-port 16/32 Gb Fibre Channel (NVMe-oF Ready) 4-port 16/32 Gb Fibre Channel (NVMe-oF Ready) * Stated //X specifications are applicable to //X R2 versions, expected availability June, ** Effective capacity assumes HA, RAID, and metadata overhead, GB-to-GiB conversion, and includes the benefit of data reduction with always-on inline deduplication, compression, and pattern removal. Average data reduction is calculated at 5-to-1 and does not include thin provisioning. *** Expected Availability 2H Array accepts Pure Storage DirectFlash Shelf and/or Pure Storage SAS-based expansion shelf. Array accepts Pure Storage SAS-based expansion shelf. Storage Software Built for Flash FlashCare technology virtualizes the entire pool of flash within FlashArray, allowing Purity to extend the life of consumer-grade MLC flash and ensure maximum performance. Granular and Adaptive Purity Core is based upon a 512-byte variable block size metadata layer. This fine-grain metadata enables all of Purity s data and flash management services to operate at the highest efficiency. Best Data Reduction Available Purity Reduce implements five forms of inline and post-process data reduction it s the most comprehensive data reduction in the industry. Data reduction operates at a 512-byte-aligned variable block size to enable effective reduction across a wide range of mixed workloads without tuning. Highly Available and Resilient Purity Assure implements high availability, dual-parity RAID-HA, non-disruptive upgrades, and encryption, all of which are designed to deliver full performance to FlashArray during any failure or maintenance event. 7

8 Backup and Disaster Recovery Built In Purity Protect combines space-saving snapshots, replication, and protection policies into an end-to-end data protection and recovery solution that protects data against loss locally and globally. All Purity Protect services are fully-integrated into FlashArray and leverage Purity s native data reduction capabilities. Pure1 Pure1, our cloud-based management, analytics, and support platform, expands the self-managing, plug-n-play design of Pure all-flash arrays with the machine learning predictive analytics and continuous scanning of Pure1 Meta to enable an effortless, worry-free data platform. PURE1 MANAGE In the Cloud IT operating model, installing and deploying management software is an oxymoron: you simply login. Pure1 Manage is SaaS-based, allowing you to manage your array from any browser or from the Pure1 Mobile App with nothing extra to purchase, deploy, or maintain. From a single dashboard you can manage all your arrays, with full visibility on the health and performance of your storage. PURE1 ANALYZE Pure1 Analyze delivers true performance forecasting giving customers complete visibility into the performance and capacity needs of their arrays now and in the future. Performance forecasting enables intelligent consolidation and unprecedented workload optimization. PURE1 SUPPORT Pure combines an ultra-proactive support team with the predictive intelligence of Pure1 Meta to deliver unrivaled support that s a key component in our proven FlashArray % availability. Customers are often surprised and delighted when we fix issues they did not even know existed. PURE1 META The foundation of Pure1 services, Pure1 Meta is global intelligence built from a massive collection of storage array health and performance data. By continuously scanning call-home telemetry from Pure s installed base, Pure1 Meta uses machine learning predictive analytics to help resolve potential issues and optimize workloads. The result is both a white glove customer support experience and breakthrough capabilities like accurate performance forecasting. Evergreen Storage Customers can deploy storage once and enjoy a subscription to continuous innovation via Pure s Evergreen Storage ownership model: expand and improve performance, capacity, density, and/or features for 10 years or more all without downtime, performance impact, or data migrations. Pure has disrupted the industry s 3-5 year rip-and-replace cycle by engineering compatibility for future technologies right into its products, notably with the NVMe-Ready Guarantee for FlashArray//M and online upgrade from any //M to //X. 8

9 OPERATING SYSTEM SAP HANA supports both Red Hat Enterprise Linux (RHEL) and SUSE Enterprise Linux. SAP HANA was initially only supported by SUSE Enterprise Linux. Red Hat support for SAP HANA came in mid Here are the master SAP Notes for SUSE Linux and RHEL. SAP Note SAP HANA Guidelines for SLES Operating System SAP Note SAP HANA Guidelines for Red Hat Enterprise Linux (RHEL) Operating System SAP HANA SHARED FILE SYSTEM In SAP HANA scale-out implementations, the /hana/shared or sapmnt or installation path is the mount directory that is used for shared files and binaries which need to be accessed by all hosts. Some of the following file system recommendations for /hana/shared can be used: NFS on RHEL operating system (NFSv3, NFSv4) A Network File System (NFS) allows remote hosts to mount file systems over a network and interact with those file systems as though they were mounted locally. This enables /hana/shared to consolidate/share resources from SAP HANA nodes on the network. SAP HANA supports NFSv3 and NFSv4 for RHEL. NFS version 3 (NFSv3) supports safe asynchronous writes. It also supports 64-bit file sizes and offsets, allowing clients to access more than 2 GB of file data. NFSv4 works through firewalls and on the Internet, no longer requires a rpcbind service, supports ACLs, and utilizes stateful operations. RHEL also supports NFS version 4, which provides a number of performance and security enhancements. GPFS GPFS provides high performance by allowing data to be accessed over multiple computers at once. Most existing file systems are designed for a single server environment, and adding more file servers does not improve performance. GPFS provides higher input/output performance by striping blocks of data from individual files over multiple disks, and reading and writing these blocks in parallel. OCFS2 on SUSE linux operating system Oracle Cluster File System 2 (OCFS2) is a general-purpose journaling file system that is fully integrated in the Linux 2.6 kernel and later. OCFS2 allows you to store application binary files, data files, and databases on devices in a SAN. All nodes in a cluster have concurrent read and write access to the file system. A distributed lock manager helps prevent file access conflicts. OCFS2 supports up to 32,000 subdirectories and millions of files in each directory. The O2CB cluster service (a driver) runs on each node to manage the cluster. SAP HANA Data and Log volumes are the only volumes certified to use the XFS file system. 9

10 SOLUTION ARCHITECTURE (SUGGESTED) The SAP HANA SPS11 certification infrastructure uses a 2+1 cluster configuration. Three Cisco UCS B200 M4 blades are used with SUSE 12 SP2 OS, including the High Availability Option and NFSv3 to create the environment. The Pure Storage FlashArray used in this configuration is the FlashArray//X10. There are four 16GB Fibre channel ports from the array attached to the SAN Fabric. Each node has two Fibre channel ports for storage and four 10 GBPS ports for networking. All the servers boot from SAN, with a dedicated drive for their OS-related partitions. All other LUNs are shared across the nodes. The /hana/shared partition is used for storing SAP binaries and is mounted in parallel, simultaneously. HANA clustering controls the DATA and LOG LUNs that are needed by the master and worker nodes. These are mounted in the appropriate node with the role of either master or worker. FIGURE 1. Pure Storage HANA Certification setup 10

11 FIGURE 2. Logical architecture of the Pure Storage HANA setup Network configuration The SAP HANA system communicates using different network channels. It is recommended practice to have a welldefined network topology to control and limit network access to SAP HANA to only those communication channels required for your scenario, and to apply appropriate additional security and performance measures as necessary. Clients require access to the SAP HANA database, and while SAP HANA is an in-memory database which stores and processes its data in memory, the data is also saved in persistent storage locations to provide protection against data loss. In distributed (scale-out) systems, communication must be possible between hosts; in disaster recovery setups, data is replicated over the network to other data centers. The components belonging to SAP HANA communicate over several logical network zones: FIGURE 3. Logical architecture of the Pure Storage HANA setup (network configuration) 11

12 Client Zone Different clients, such as SQL clients on SAP application servers, browser applications using HTTP/S to the SAP HANA XS server, and other data sources (such as BI) need a network communication channel to the SAP HANA database. Inter-Node Zone The internal zone covers the communication between hosts in a distributed SAP HANA system as well as the communication used by SAP HANA system replication between two SAP HANA sites. Storage NFSv3 Zone Although SAP HANA holds the bulk of its data in memory, the data is also saved in persistent storage locations which probably need to be accessed via a network to provide protection against power failures or other events that cause hosts to become unavailable. In addition, this zone will be used for NFSv3 communication in our recommended architecture to deploy /hana/shared. To achieve this, it is recommended to have three Ethernet NICs in each node. Each will have different hostnames and will be part of a different network zone. The /etc/hosts file should look as follows: FIGURE 4. Sample /etc/hosts file Install the SAP HANA scale-out in the following manner: Set up cluster and NFSv3 with one hostname, which uses the private network Set up the SAP HANA system with a different hostname, which uses the private network Set up SAP HANA clients with a third hostname, which uses the public network The global.ini should be configured for inter-node communication or internal communication. Please see the latter part of the document for global.ini configuration. Pure Storage Configuration Pure Storage FlashArray//X10 is used in this configuration. The raw capacity of the array is TB, but with Pure s industry-leading de-duplication and compression capabilities, the usable capacity is significantly higher. 12

13 FIGURE 5. Pure Storage array system dashboard The three Cisco UCS servers used for the HANA configuration are attached to the SAN fabric and zoned to the array. The three nodes are seen in the array, as shown below. FIGURE 6. Hosts zoned to the array LUN Configuration Multiple LUNs are configured in the Pure storage array for use in the HANA setup. There are three boot LUNS, as shown, that are zoned to the individual hosts. All other LUNS are shared between the three nodes. The data and log LUNS are for the HANA database. The hanadatavolume1, hanadatavolume2, hanalogvolume1, and hanalogvolume2 are zoned to all three SAP HANA nodes. However, the volumes hanadatavolume1 and hanalogvolume1 are primarily for the Master node and hanadatavolume2 and hanalogvolume2 are primarily for the Worker node. The hanasharedvolume LUN is for the NFSv3 partition that is always mounted on all the nodes simultaneously and houses the HANA binaries. 13

14 FIGURE 7. Pure Storage LUNS used in the setup NFSv3 Setup Enable SSH for password-less access on all three nodes Setup windows file services on the Purity RUN platform Purity RUN Platform Applications and/or services within Purity RUN can be created by customers or provided by Pure Storage. They are able to run on VMs and/or containers, depending on their deployment model. The apps that are provided by Pure Storage are validated and fully supported by Pure1 Support. Use cases for Purity RUN can be as simple as consolidation of a few servers in a remote office or as demanding as co-locating data-intensive compute jobs closer to the data consumed. INTRODUCING THE NEWEST MEMBER OF PURITY RUN WINDOWS FILE SERVICES Installation and setup of WFS is fully automated. Once the WFS application package is uploaded onto FlashArray, setup can take less than 15 minutes. After the setup completes, the WFS clustered instances will show up as a new host in the Pure Storage GUI, and the health of WFS can be monitored from the Apps subtab. All block storage tasks, such as volume creations, snapshots, replication, monitoring, and reporting, are handled identically to an external host. File administration and configuration is done by leveraging Windows Server management and the Windows API stack. FEATURES AND CAPABILITIES All the rich inherent features of FlashArray, such as high availability, security, and data protection are leveraged by the WFS solution. High availability for data services is achieved through FlashArray s redundant architecture. Security is provided by the data-at-rest encryption (DARE) capabilities native to the array. Data protection services include crash-consistent snapshots and application-level snapshots. Lastly, all data residing on WFS benefits from FlashArray s global data reduction services, which dramatically reduce physical capacity consumption. 14

15 HOW DOES IT WORK? Purity RUN has dedicated system hardware resources that include CPU and memory. This allows apps deployed on Purity RUN to have complete performance isolation from the rest of the FlashArray. The Purity RUN environment is completely virtual and consists of a hypervisor running on each FlashArray controller. Apps are launched either in the form of VMs or containers within VMs. In the case of WFS, each FlashArray controller will launch a separate VM instance of Windows Server 2016, which will form a Windows Failover Cluster. File Servers will then be created within the cluster to serve SMB shares. Each WFS VM is installed on its own separate boot volume. For Windows clustering purposes, a default quorum witness volume is exported to both WFS VMs. Lastly, a default data volume is also created, in which file services data will reside. Subsequent data volumes can be created if additional capacity is required. Data volumes are also exported to both WFS VMs to ensure persistent data across WFS VM failovers. FIGURE 8. Purity RUN logical diagram For high availability, WFS leverages Windows Failover Cluster to manage File Server failovers, which ensure continuous file services uptime. In the event of an unforeseen cluster resource failure, such as a FlashArray controller or VM failure, any File Server running on the failed FlashArray controller or VM will automatically be moved to the surviving VM. Upon recovery of a FlashArray controller or VM, customers can manually move the File Server back to the original VM. Customers also have the option to set an automatic migration of the File Server back to the preferred VM. 15

16 CREATING NFS SHARES ON WFS Creating NFS shares in WFS is simple and can be accomplished in several ways, including the Server Manager GUI or Windows PowerShell. The following steps illustrate a new NFS share creation using the Server Manager GUI. From the Server Manager, navigate to Files and Storage Services, and highlight Shares. Click on TASKS and select New Share FIGURE 9. Server Manager screen Select NFS Share Quick and click Next. FIGURE 10. Profile selection screen Follow the remaining wizard to create the NFS share. Be sure to select the desired HANA shared volume and set permissions accordingly. This will create an NFS share, which can be accessed by all SAP HANA nodes, as seen in the next figure. 16

17 FIGURE 11. NFS share available to all SAP HANA nodes QOS QoS takes care of SAP HANA performance by taking care of noisy neighbors. This ensures SAP HANA performance does not go down when an application which is not mission critical starts to become noisy. Here are three main use cases for QoS: FIGURE 12. Main QoS use cases On the next page, we demonstrate how Pure addresses these use cases via QoS in Purity

18 FIGURE 13. Purity QoS solutions for main use cases Always-On QoS This feature, released in 2016, autonomically protects system workloads against a single workload (usually called a noisy neighbor) consuming all system resources and impacting all tenants. Pure s industry-first solution addresses noisy neighbor problems without requiring a user to define any policies or rules. Below you can see Always-On QoS in action, automatically detecting that Workload 5 is using too much performance in a very short period of time and is responsible for pushing the entire system to performance saturation. FIGURE 14. Always-On QoS automatically detects noisy neighbors and throttles the relevant workload Purity continuously monitors incoming I/O and is able to determine when the array is too busy to deliver sub-ms predictable performance. In that situation, Purity automatically detects which workload is consuming more than its fair share of resources and then throttles that workload to avoid performance degradation on all other workloads. 18

19 Performance Classes Performance Classes are built on top of Always-On QoS and provide you the opportunity to specify a Performance Class (Gold/Silver/Bronze) for a single volume or a workload/tenant. This approach empowers you to consolidate workloads and allocates performance to applications when the system approaches 100% performance utilization. Here s Performance Classes in action: FIGURE 15. Performance Classes throttles less-critical workloads to protect mission-critical workloads This implementation is ideal for consolidating applications and tagging some as mission-critical, permitting throttling of less-critical applications in the event of system performance contention. Performance Limits To complete the story, and for our more sophisticated users, we are also introducing throughput limits on a per volume or workload/tenant basis. This is a hard limit which will determine the max performance a given workload can consume before being throttled. Limits can be used in conjunction with Performance Classes to enable interesting use cases where Service Providers can create a catalog to meet minimums, maximums, and bursts. Performance Classes ensure that if the system reaches performance saturation (and there are enough less important workloads to throttle to satisfy Gold class performance demand), minimums are met for higher class workloads; conversely, when the system is below performance saturation, all workloads are allowed to burst. For this use case, limits can be configured to represent peak value for burst. 19

20 FIGURE 16. Resource consumption comparison with Performance Limits Purity QoS raises the bar in both functionality and simplicity when it comes to one of the most sophisticated features in storage: Always-On QoS is enabled by default. For users who are consolidating workloads that share the same SLA, this functionality delivers fairness of service to all workloads. Performance Classes allows one-click functionality to assure performance protection for mission critical apps. Performance Limits enforce performance expectations for targeted workloads. Configuration of udev Rules The device manager of the kernel needs to be configured as shown below. The most important parameters to be changed are the nr_requests and the scheduler. Please set parameters for Pure Storage in udev/rules.d, as shown below: FIGURE 15. Pure Storage udev Rules 99-PURE-STORAGE.RULES # Recommended settings for Pure Storage FlashArray. # Use noop scheduler for high-performance solid-state storage ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/ scheduler}="noop" # Reduce CPU overhead due to entropy collection ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/add_ random}="0" # Spread CPU load by redirecting completions to originating CPU ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/rq_ affinity}="2" ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/nr_ requests}="1024" 20

21 ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/nomerges}="1" ACTION=="add change", KERNEL=="sd*[!0-9]", SUBSYSTEM=="block", ENV{ID_VENDOR}=="PURE", ATTR{queue/ rotational}="0" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/scheduler}="noop" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/rotational}="0" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/nr_requests}="4096" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/rq_affinity}="2" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/nomerges}="1" ACTION=="add change", ENV{DM_UUID}=="mpath-3624a937?*", ATTR{queue/add_random}="0" ACTION=="add change",kernel=="dm-*", ATTR{queue/scheduler}="noop" ACTION=="add change", KERNEL=="dm-*", ATTR{queue/rotational}="0" ACTION=="add change", KERNEL=="dm-*", ATTR{queue/nr_requests}="4096" ACTION=="add change", KERNEL=="dm-*", ATTR{queue/rq_affinity}="2" ACTION=="add change", KERNEL=="dm-*", ATTR{queue/nomerges}="1" ACTION=="add change", KERNEL=="dm-*", ATTR{queue/add_random}="0" # SCSI timeout in line with Customer Best Practices ACTION=="add", SUBSYSTEM=="scsi", ATTRS{model}=="FlashArray ", RUN+="/bin/sh -c 'echo 60 > /sys$devpath/ timeout'" Multipathing Configuration Multipathing needs to be set up to do round-robin for all PURE LUNs by configuring it in /etc/multipath.conf. Install the sysstat package with Yast2 to get iostat in the servers. It is very important to set the path-selector in multipath configuration to round-robin. The file contents of multipath.conf are shown here: saphananode1:~ # cat /etc/multipath.conf devices { device { vendor "PURE" path_selector "queue-length 0" path_grouping_policy path_checker multibus tur fast_io_fail_tmo 10 dev_loss_tmo 60 no_path_retry 0 } } 21

22 HANA Configuration Files These are the requisite configurations: HANA GLOBAL.INI FILE [system_information] usage=test [communication] listeninterface =.internal internal_network= /24 [internal_hostname_resolution] =saphananode =saphananode =saphananode3 [persistence] basepath_datavolumes=/hana/data/psd basepath_logvolumes=/hana/log/psd use_mountpoints = yes basepath_shared = yes [storage] ha_provider = hdb_ha.fcclient partition_*_* prtype = 5 partition_1_data wwid = 3624a9370c57f15eeeb434b0b000113ef partition_1_log wwid = 3624a9370c57f15eeeb434b0b000113f0 partition_2_data wwid = 3624a9370c57f15eeeb434b0b000113f1 partition_2_log wwid = 3624a9370c57f15eeeb434b0b000113f2 [trace] ha_fcclient = info HWCCT: FSPERF PARAMETERS The following parameters were set for the new performance test tool from SAP HWCCT, fsperf. These settings will change I/O behavior to enhance the database in working with the file system and storage. 22

23 For Data Volumes, use the following hdbparams: async_read_submit=off async_write_submit_blocks=auto max_parallel_io_requests=64 async_write_submit_blocks=new For Log Volumes, use the following hdbparams: async_read_submit=off async_write_submit_blocks=new SAP HANA 1.0 For more information regarding these parameters, please refer to SAP Note In order to use the parameters in SAP HANA, you need to execute the following commands in the Linux shell as <sid>adm user. hdbparam paraset fileio [<path>]. async_write_submit_blocks=new To set async_write_submit_blocks for data persistence: (Check the select query on the view M_VOLUME_IO_ TOTAL_STATISTICS shown below to get the information on the path and trigger ratios.) hdbparam paraset fileio [/hana/data/psd/mnt00001/hdb00003/]. async_write_submit_blocks=new This command returns lines indicating the success of the parameter setting for services like NameServer, Preprocessor, IndexServer, etc. SAP HANA 2.0 Up to HANA1SP12, the hdbparam tool was part of the HANA installation and was used to manage a subset of HANA configuration parameters. With HANA2, the hdbparam tool has been deprecated. It is no longer installed as part of HANA. When upgrading to HANA2 from HANA1, the tool and the binary files storing the configured parameter values will be removed. The parameters managed by hdbparam have been moved to global.ini. All normal rules for Ini-file-parameters apply. 23

24 The parameters managed by hdbparam were: fileio.num_submit_queues fileio.num_completion_queues fileio.size_kernel_io_queue fileio.max_paralle_io_requests fileio.min_submit_batch_size fileio.max_submit_batch_size fileio.async_write_submit_active fileio.async_write_submit_blocks fileio.async_read_submit You can update these parameters directly in global.ini or see the example below; in this case only two parameters exported in step differ from the defaults in global.ini: fileio.max_submit_batch_size = 64 fileio.async_read_submit[data] = off Use ALTER SYSTEM ALTER CONFIGURATION as follows ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio', 'max_submit_batch_size') = '64'; ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('fileio', 'async_read_submit[data]') = 'off'; Add a WITH RECONFIGURE to all or at least the last ALTER SYSTEM ALTER CONFIGURATION command if you want to apply the parameter changes. If you have changed the fileio.size_kernel_io_queue parameter, you will have to restart the database since the parameter change cannot be applied online. 24

25 CONCLUSION Unlike traditional storage architectures, Pure Storage FlashArray does not require customers to compromise on resiliency and simplicity for the sake of performance. Whether you are looking to get started with SAP HANA, or migrating an existing HANA environment, FlashArray is the ideal platform for maximizing your HANA investment. Pure Storage recommends the following guidelines for sizing customer HANA environments. Please consult with your Pure Storage sales team for more detailed information. AFA MODEL SAP HANA NODES //X10 UP TO 14 //X20 UP TO 22 //X50 UP TO 30 //X70 UP TO 38 //X90 UP TO 44 TABLE 3. Sizing Guidelines for Pure Storage FlashArray//X REFERENCES 1. Pure Storage FlashArray Data Sheet 2. Pure Storage FlashArray Webpage 2018 Pure Storage, Inc. All rights reserved. Pure Storage, Pure1, Meta, Evergreen, and the P logo are trademarks or registered trademarks of Pure Storage, Inc. in the U.S. and other countries. SAP and SAP Hana are registered trademarks of SAP in the U.S. and other countries. Oracle is a registered trademark of Oracle Corporation in the U.S. and other countries. All other product and service names mentioned are the trademarks of their respective companies. The Pure Storage product described in this documentation is distributed under a license agreement and may be used only in accordance with the terms of the agreement. The license agreement restricts its use, copying, distribution, decompilation, and reverse engineering. No part of this documentation may be reproduced in any form by any means without prior written authorization from Pure Storage, Inc. and its licensors, if any. THE DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. PURE STORAGE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. ps_wp25p_sap-hana-setup-best-practices_02 25