Technology Roadmap Arne Arnold, SAP HANA Product Management September, 2014
High-Level Overview
Why care about SAP HANA virtualized Why SAP HANA virtualized offer customers reduced TCO and additional options for planning and managing their systems landscapes. It also impacts CAPEX positively and hence can help lower the barriers to entry for SMEs and startups. How A hypervisor specific validation process has been established to determine all necessary constraints and best practices to ensure supportability and minimum performance requirements for running SAP HANA in virtualized environments. The first hypervisor which went through validation and is supported in the context of SAP HANA is VMware vsphere, but others will follow over time. Source: Gartner Magic Quadrant for x86 Server Virtualization Infrastructure, July 2014 (G00262673) 2014 SAP SE. All rights reserved. Customer 4
Technology Roadmap (high level) F u t u r e 2012 2013 2014 2015 2014 SAP SE. All rights reserved. Customer 5
SAP HANA Deployment Scenarios production On premise SAP HANA appliance SAP HANA Tailored Datacenter Integration VMware vsphere Hitachi LPAR ABAP on SAP HANA MCOD Cloud SAP HANA Enterprise Cloud HANA Cloud Platform IaaS Providers On-premise/private virtual private/public On premise Multi SID (MCOS) Cloud SAP HANA One SAP HANA developer edition non-production 2014 SAP SE. All rights reserved. Customer 6
Hypervisor Support Status & Outlook
Currently Supported Hypervisors Currently supported hypervisors for running SAP HANA virtualized (on either SLES or RHEL guest OS): VMware vsphere 5.1 and SAP HANA SPS 05 (or later releases) for non-production use cases VMware vsphere 5.5 and SAP HANA SPS 07 (or later releases) production and non-production use cases o In General Availability for single-vm scenarios (see SAP Note 1995460 for details). o In Controlled Availability for multi-vm scenarios, (see later slide for process description) Hitachi LPAR 2.0 and SAP HANA SPS 07 (or later releases) production and non-production use cases o In Controlled Availability for single- and multi-vm scenarios, (see later slide for process description) The following general constraints and conditions do apply while running SAP HANA virtualized: o Limited to scale-up scenario only (scale-out / multi-node database installations are not supported). o CPU & memory overprovisioning must not be used. Each SAP HANA instance / virtual machine is sized according to the existing SAP HANA sizing guidelines and corresponding hypervisor vendor recommendations. o SAP HANA installation was either done following by an SAP HANA certified engineer on SAP HANA certified hardware and successfully verified with the SAP HANA hardware configuration check tool (SAP HANA Tailored Datacenter Integration option), or system had been delivered pre-configured as certified SAP HANA appliance, with hypervisor installed by SAP HANA hardware partner. See SAP Note 1788665 - SAP HANA Support for Virtualized Environments 2014 SAP SE. All rights reserved. Customer 8
High Availability Options High Availability solution Hypervisor High Availability Hypervisor HA + In-Guest Cluster (node recovery) Scenario Description Standard VM HA solution (based on shared file system, no split brain) Cluster manager handles switch over to secondary site, while VM HA is used to restart/restore availability of primary host, so HA cluster is ready for next fault situation (just in opposite direction). In-Guest cluster only SAP HANA System Replication * + In-Guest Cluster Standard 3 rd party cluster manager, not utilizing VM capabilities. Data replication between primary and secondary site may be done by storage replication (or similar). Operating system failures Yes Yes Yes Yes Standard 3 rd party cluster manager, not utilizing VM capabilities. Data replication between primary and secondary site is done by SAP HANA system replication, however. Hardware failures Yes Yes Yes Yes Application failures No ** Yes Yes Yes IP Redirect / DNS update Not necessary Handled by In-Guest Cluster Manager RTO Medium (crash recovery of DB) Medium (crash recovery of DB) Handled by In-Guest Cluster Manager Medium (crash recovery of DB) Handled by In-Guest Cluster Manager Shortest (IP redirect) RPO 0 0 0 0 (synchronous) >0 (asynchronous) Remarks: Suitable also for disaster tolerant (DT) solution, in conjunction with site failover with VMware Site Recovery Manager and storage replication Note: 2 nd cluster node shall not reside on same physical host Possible cluster manager includes SUSE HA; HP Service Guard, SAP LVM, VMware Site Recovery manager Note: 2 nd cluster node shall not reside on same physical host Alternative to VM HA / DT solution, leveraging SAP HANA system replication to achieve possible lower RTO. * The SAP HANA host auto-failover is currently not supported, as scale-out supported is missing for virtualized environments ** In case of VMware, future plans to also support application failure detection 2014 SAP SE. All rights reserved. Customer 9
Technology Roadmap (from today to 2015+) Today Support for SAP HANA on VMware in non-production scenarios Support for single-vm SAP HANA on VMware in production and nonproduction scenarios Controlled Availability for VMware multi-vm scenarios, as well as Hitachi LPAR technology in production On Roadmap Support for scale-up on vsphere 6 Support for scale out scenarios Single VM production support Complement deployment options Extend platform support Add variety Multi VM support Support of additional hypervisors HANA scale out 8 socket hardware Future vsphere optimization / releases On single host On vsphere cluster H1/2014 H2/2014 2015+ This is the current state of planning and may be changed by SAP at any time. 2014 SAP SE. All rights reserved. Customer 10
Application Process for Controlled Availability Customers interested in running multiple SAP HANA VMs on VMware vsphere 5.5 in production one or more SAP HANA VMs on Hitachi LPAR 2.0 in production can apply for Controlled Availability of SAP HANA production support by sending an email to: sap_hana_tailored_data_center_integration@sap.com This email should contain High-level scenario description and timeline (e.g. planned Go-live date) Expected database size (compressed HANA DB size, number of users) Hardware spec (HW vendor, server t-shirt size), Planned HA/DR setup (if applicable), Contact details (if possible incl. SAP account number) for further communication All information provided will be kept confidential and is only being used during the selection process. Once accepted, customers will receive the usual SAP HANA support as also provided for non virtualized environments for the presented scenario. 2014 SAP SE. All rights reserved. Customer 11
Further Reading SAP HANA Virtualized Central Note https://service.sap.com/sap/support/notes/1788665 SAP HANA Virtualized Overview ppt http://www.saphana.com/docs/doc-3334 SAP HANA Guidelines for VMware http://www.saphana.com/docs/doc-4192 VMware Best Practices for SAP HANA http://vmware.com/go/sap-hana Hitachi Best Practices for SAP HANA http://scn.sap.com/docs/doc-57936 SAP HANA Enterprise Cloud http://www.sap.com/entcloud SAP HANA One http://www.saphana.com/docs/doc-2482 SAP HANA Developer Edition http://scn.sap.com/docs/doc-28294 More info will be made available through http://www.saphana.com/community/resources HANA Technology Virtualization 2014 SAP SE. All rights reserved. Customer 12
Thank you Contact information: Arne Arnold, MSc, PMP SAP HANA Product Management AskSAPHANA@sap.com To get the best overview of what s new in SAP HANA SPS 08, read this blog.
2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. 2014 SAP SE. All rights reserved. Customer 14