Planning an SAP HANA Landscape

Transcription

1 Planning an SAP HANA Landscape Customer Glen Leslie September 2016

2 SAP HANA: The Platform for All Applications SAP HANA PLATFORM ON-PREMISE CLOUD HYBRID 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 2

3 Application Development Process Orchestration SAP HANA platform Innovative technology in a DB, and much, much more Any App Any App Server Analytic Applications Any BI Tool SQL MDX R JSON Open Connectivity SAP HANA Platform Extended Application Services Supports any Device App Server UI Integration Services Web Server Processing Engine OLTP OLAP Search Text Analysis Predictive Events Spatial Rules Planning Core Database Other Services, Function Libs, Data Mgmt., etc. Predictive Analysis Lib. Business Function Lib. Data Models & Stored Procedures Unified Administration Life-cycle Management Security Integration Services Federation / Big Data Replication ETL/ELT Remote Data Sync Streaming Deployment: On-Premise Hybrid On-Demand SAP HANA platform converges database, data processing and application platform capabilities *and* provides so much more for specialized use cases 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

4 SAP HANA platform common use cases Optimizing Business Operations Get instant insights into real-time transactions to optimize business operations Operational Reports, Dashboards, and Analytics Analyze and visualize operational details to support your day-to-day activities Real-time Operational Intelligence Run queries against operational data, streams and events to deliver real-time insights Data Warehouse and Data Mart Deliver actionable insights on enterprise-wide or departmental data Big Data Uncover the value in large, complex and rapidly growing data sets Decision Support, Simulation and Automation Streamline and automate business processes with advanced analytics 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 4

5 SAP HANA: Choice of deployment Cloud, On-Premise and hybrid Bus. Suite BW SAP S/4 HANA 3 rd Party Apps Concur Concur Ariba SuccessFactors Ariba SuccessFactors Cloud On-Premise Hybrid Run all applications in the cloud Run all applications On-Premise Leverage right deployment option that meets business priorities 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

6 Sizing

7 SAP HANA Sizing Translate business requirements into hardware requirements in an iterative process SAP HANA Sizing Key Performance Indicators Memory Memory sizing is determined by the data footprint in SAP HANA business and meta data in column and row store) Memory (static) is also being used by other components (e.g. SAP HANA caches and operating system) CPU Disk Size Disk I/O CPU utilization in SAP HANA differs from a traditional database (HANA is designed to use all CPU power available) OLAP systems require more CPU horsepower than OLTP systems Disk is required for data persistence and for logging data Sizing formula is independent of whether the system is an OLAP or OLTP system Network Load SAP provides recommendations for inter-node network in case of scale-out, as well as recommendations for the client network, the application server network and the backup and storage network 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

8 Sizing SAP HANA: Process overview Three-party Collaboration Model Hardware Vendors Contributions Certified benchmarks scalable hardware Different configurations together with technology partners Performance studies Custom load tests in collaboration with customers Service level agreements Responsible for final sizing Technical requirements Feedback and experience Hardware configuration Sizing Recommendation CPU (SAPS) Memory (GB) Database space (GB) Disk I/O operations per sec Frontend bandwidth mbps SAP Contributions Development and provision of benchmark toolkits Regression testing for new releases Standard sizing guidelines as part of quality assurance process Sizing verification processes Customer Expectations from benchmarking and sizing Optimal performance Suggestion for hardware configuration Contributions Response time requirements Throughput requirements Provides business data input Feedback and experience Business requirements 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 8

9 SAP HANA Sizing SAP HANA Sizing SAP HANA Quick Sizer - Sizing New Applications Initial Sizing Migrating to SAP HANA Applications Productive Sizing Sidecar Scenarios SAP HANA Quicksizer: > HANA Version Requires login credentials to the SAP Service Marketplace 1. Standalone HANA Re-Sizing: SAP Note Migration: SAP Note SAP S/4HANA and Business Suite/ Industry Solutions powered by HANA SAP Note SAP BW powered by HANA SAP Note Enterprise Search SAP Note CO-PA Accelerator HANA sizing for CO-PA Accelerator 3. SAP Applications on HANA SAP HANA Quicksizer: > HANA Version 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

10 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

11 Infrastructure Options

12 SAP HANA: One type of overview Application Any Database SAP HANA Operation System Virtualization / Partitioning Server Network Storage SUSE/SLES Redhat/RHEL VMware, Huawei Fusion Sphere; Hitachi LPAR / HP npar /Fujitsu PPAR / Lenovo Flex Node/ IBM Power LPAR) CPU type: Intel E7 with up to 20 TB RAM Intel E5 with up to 1.5 TB RAM IBM Power8 with up to 9.2 TB RAM Client Zone/ Internal Zone/ Storage Zone Appliance delivery approach or - SAP HANA tailored data center integration 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 12

13 SAP HANA infrastructure partners and deployment scenarios Single Server 2 CPU 128GB to 20 CPU 20TB (Intel Xeon E5/E7) 8c to 96c flexible LPAR configs., max 96GB RAM/core ( IBM Power System 8) Single SAP HANA deployments for data marts or accelerators Support for high availability and disaster tolerance Scale Out Cluster 2 to n servers per cluster each server is: 4 CPU or 8 CPU, size ranges 128GB to 4TB (Intel Xeon E7) 8c to 32c flexible LPAR configs., max 50GB RAM/core (IBM Power System 8) Largest certified configuration: 56 servers Largest tested configuration: 100+ servers Support for high availability and disaster tolerance 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 13

14 Infrastructure architectural considerations Scale up / Scale out Public

15 Scalability and scale-up / scale-out Scalability is the ability of a computer hardware/software to take full advantage of its changed context in a re-scaled situation, e.g. by adding or reducing resources Vertical Scalability (scale-up) Adding resources within the same computing unit, e.g. #CPUs, #DRAMs Horizontal Scalability (scale-out) Adding multiple computing units and making them perform well together as one logical computing unit For successful scalability, all layers of a HW/SW stack have to scale with fast performance 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 15

16 SAP HANA scale-up Basic Concept: Single-node hardware server with expansion capacity HANA is heavily optimized for state-of-the-art (multi core/processor) HW architectures HANA uses massive intra-plan and intra-operator parallelism for query execution HANA tries to use all available resources for maximal parallelization Challenge: NUMA-effects on large multi-socket systems Pros No inter-node communicaton overhead Slightly less administrative overhead (design & operations) than for scale-out deployments Does not require deep knowledge of application, data, and hardware (data distribution) Cons Practical size limits (currently in the 15 24TB range) Lack of data distribution may introduce data access inefficiencies (only compared to scaleout) 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 16

17 SAP HANA scale-out Basic concept: Multi-node system comprised of several server nodes acting together; shared-nothing architecture Multiple servers (nodes) are switched together to one logical, but physically distributed database system The shared-nothing SAP HANA architecture helps to minimize communication costs between servers 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 17

18 SAP HANA scale-out HANA s shared-nothing architecture Topology Each node runs on its own local data (shared-nothing) Standby node(s) without own persistence Shared file system for node fail-over and recovery (HW partner implementation) Data Volume Log Volume Data Volume Master node Slave node HDB net Nodes communicate via internal HDB net protocol All nodes belonging to the same HANA system must have the same HW setup Log Volume Standby node(s) Auto fail-over 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 18

19 SAP HANA scale-out Pros & Cons Pros High scalability: Distributed systems can overcome hardware limitations of one single server by distributing load between multiple servers No hardware limits (theoretically) have tested beyond 100TB, SAP owns the Guiness Book of World Records EDW record: 12.1PB Scale-out provides more hardware flexibility and less initial hardware costs than scale-up Cons Scale-out requires more knowledge about data, application and hardware than scale-up (Shared-nothing imposes to understand how data are used in a distributed system) Attention to design & operations on large-scale (>20TB) systems SAP recommendation: Always scale-up first; scale out only if you have to 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 19

20 Tailored Datacenter Infrastructure TDI Options

21 Data center integration approaches: Key concepts overview SAP HANA TDI is an alternative deployment approach. Compared to an appliance, it offers more flexibility when you have to select the appropriate hardware for integrating SAP HANA in your data center. Appliance building blocks: All in one box SAP HANA TDI: Use your own prefered HW SAP HANA HANA Server Server Storage Application Server Database Operating System Virtualization Server (CPU, RAM) Network Storage SAP HANA HANA Server Server Enterprise Network Enterprise Storage Server (CPU, RAM) Network Storage Additional flexibility: Customers can leverage their existing storage, choose their prefered compute server vendor, storage 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 21

22 SAP HANA TDI Enterprise Storage Considerations With the introduction of TDI with Enterprise Storage, SAP supports hardware setups which comply with the three prerequisites below. Apart from that, no further approval by SAP is required. 1) Use certified hardware only Only servers out of the list of certified compute servers are supported Same servers as for SAP HANA appliances 2) Use certified storage only Storages used for TDI setups must have successfully passed the SAP HANA hardware certification for Enterprise Storage Certificate states that the storage fulfills SAP HANA s requirements for data throughput and latency times 15+ storage partners with dozens of certified storage families (as of Sep, 2016) 3) Let only certified person(s) do the SAP HANA software installation Required exam: SAP Certified Technology Specialist (Edition 2015) SAP HANA Installation (E_HANAINS151) For more information, see SAP Training and Certification Shop The exam needs to be successfully passed for a person to perform SAP HANA SW installations SAP HANA hardware partners and their employees do not need this certificate Companies, or their employees, who are sub-contractors of hardware partners must be certified to perform HANA SW installations 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 22

23 SAP HANA TDI Enterprise Storage Detail Read SAP s Storage Whitepaper Get a copy of your storage vendor s configuration guide for SAP HANA. Make sure to run the SAP HANA HW Config Check Tool to check your storage KPIs every time you change your storage configuration Customers should consider involving SAP Global Services and Support (GSS) to perform a HANA Go-Live Check prior to going productive 1) Storage Whitepaper Background Knowledge Conceptual storage layout, non-shared storage vs shared storage Storage sizing formulas Helps you understand the impact of SAP s data throughput KPIs in daily operation of SAP HANA Explains SAP HANA s high-availability support (Host Auto Failover) Available on SCN: SAP HANA Enterprise Storage white paper 2) Storage Configuration Vendor-specific Configuration Guide For getting certified, each storage vendor must file in a configuration guide Explains how to configure the storage for optimal collaboration with SAP HANA Incl recommendations how many SAP HANA server nodes can be connected at maximum Get a copy directly from your storage vendor 3) SAP HANA HW Config Check Tool (HWCCT) Command-line tool, generally available since SAP HANA SPS07 Used by storage vendors, SAP Support, and customers Measures the data throughput and latency times between the SAP HANA servers and the Enterprise Storage system Does not require SAP HANA SW being installed beforehand Uses the same libraries for file system access and the same IO patterns as SAP HANA does Download it from SAP Support Portal Navigation path: A - Z Index -> H -> SAP HANA Platform Edition -> SAP HANA PLATFORM EDIT > Entry by Component -> HANA config check -> SAP HANA HW CONFIG CHECK 1.0 -> Linux on x86_64 64bit -> select SAR file for download Documented in the SAP HANA Administration Guide Contains the latest KPIs For latest docu changes, see PDF attachment of SAP Note SAP SE or an SAP affiliate company. All rights reserved. Customer 23

24 SAP HANA TDI Enterprise Network Considerations With the introduction of TDI, SAP supports Network hardware setups which comply with the prerequisites below. Apart from that, no further approval by SAP is required. SAP does not introduce any certification of network components for TDI setups. Customers should consider involving SAP Global Services and Support (GSS) to perform a HANA Go-Live Check prior to going productive. 1) For the SAP HANA computing nodes, use certified hardware only Same as with TDI with Enterprise Storage 2) In multi-node setups, check the bandwidth available between the computing nodes Make sure that the intra-node network of your SAP HANA scale-out solution fulfills the recommended minimum bandwidth requirements Conduct self-managed tests using the Network Test available with HWCCT SAP does not introduce any additional certification of network components for TDI setups 3) Let only certified person(s) do the SAP HANA software installation Same as TDI Enterprise Storage requirements 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 24

25 SAP HANA TDI Enterprise Network Considerations Read SAP s Network Whitepaper. Make sure to run the SAP HANA HW Config Check Tool to check your network KPIs every time you change your HANA cluster configuration. 1) Network Whitepaper Background Knowledge Helps you understand the impact of SAP s network recommendations on the daily operation of SAP HANA Introduction to SAP HANA s logical network zones: Client Zone, Internal Zone, Storage Zone Detailed description of the network traffic in typical situations of an application scenario Which network zones are involved in situations like data load, reporting, backup, failover, takeover Technical requirements and recommendations for all network zones Available on SCN: HANA Network Requirements white paper Complements existing sources of information: Network zones, ports and connections, host name resolution: SAP HANA Master Guide, chapter 3.3 "The SAP HANA Network Network and communication security: SAP HANA Security Guide, chapter 5 Network recommendations for SAP HANA System Replication: SCN How-To Guide 2) SAP HANA HW Config Check Tool (HWCCT) Network test added with SAP HANA SPS08 Used by hardware vendors, SAP Support, and customers Measures the minimum bandwidth of the intra-node network i.e. the bandwidth available between the hosts that comprise a multinode system Does not require SAP HANA SW being installed beforehand Hosts are tested pair-wise. For each pair, two tests are available: Unidirectional: Transfer test load from host 1 to host 2, measure bandwidth Bidirectional: At the same time, transfer test load from host 1 to host 2 and vice versa; measure bandwidth Documented in the SAP HANA Administration Guide Contains the latest KPIs recommended for the bandwidth of the intranode network For latest docu changes, see PDF attachment of SAP Note SAP SE or an SAP affiliate company. All rights reserved. Customer 25

26 SAP HANA TDI: Extended Support for Intel Xeon E5 v2/v3 CPU Entry-level systems managing expectations Basic idea: Leverage Intel s E5 technology for SAP HANA cost optimized entry-level system Intel Xeon 2 socket E5 26xx v2/v3 with minimum 8 cores per CPU are supported For the SAP HANA computing nodes, use certified hardware only as listed on SCN Homogenous symmetric assembly of DIMMs and maximum utilization of all available memory channels Single server systems scale up only, with systems ranging in size from 128GB to 1.5TB Supported as SAP HANA tailored datacenter integrated system The sweet spot is around $10K (768GB system, populated with 32GB DIMM s) Let only certified person(s) do the SAP HANA software installation Production support for proper sized systems which fulfil the data throughput and the latency KPI s Relaxed HW Specifications for Non-Production system (e.g Cost-Optimized SAP HANA Infrastructure for Non- Production Usage) Restrictions No support for Intel Xeon E5 4 socket systems No support for SAP HANA scale out solutions based on Intel Xeon E5 compute nodes 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 26

27 SAP HANA TDI Phase 4 Introduction to HANA on IBM Power Systems Starting with SPS 11, customers can chose to run SAP HANA on IBM Power Systems 8 (in production) or on Power Systems 7+ (in non-production), as long as they follow the requirements and restrictions listed below: Compute server requirements See Table below for suported Power 8 System configurations Power 8 Model Min cores per LPAR Max cores per LPAR Max RAM per Core (BWoH) Max RAM per LPAR (BWoH) Max RAM per Core (SoH) Max RAM per LPAR (SoH) S GB GB Comment 1 Comment 2 S822L GB GB S824 S824L GB GB All Models: E GB GB E GB GB E GB GB For E850, E870, E880 models users can leverage IBM Capacity on Demand (COD) to turn on/off capacity as needed SLES 11 SP4 required Dedicated, donating LPARs only; Shared Processor Pool not allowed (See SAP Note ) Support for Live Partition Mobility (LPM) (*) See SAP HANA on IBM Power Systems: Allowed Hardware for an up-to-date list of supported Power 8 system configurations, also SAP Note SAP HANA on IBM Power Systems with multiple LPARs per physical host, and SAP Note Supported products when running SAP HANA on IBM Power Systems 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 27

28 SAP HANA Tailored Data Center Integration Comparison with Appliance Delivery Model Appliance Delivery Model SAP HANA TDI Approach Hardware Selection Limited (customer) flexibility Customer can choose between appliance vendors No option to replace certain components with HW already used in customers Data Center Potential Savings leveraging existing investments Use customer-preferred storage Use customer-preferred network components A choice of compute server processor (Intel Xeon E5, E7 CPU, Compared to the appliance delivery, SAP HANA TDI is an additional approach IBM Power providing 8 CPU) you with more flexibility to fulfill your needs of integrating SAP HANA in your data center. Implementation Effort Low for customer Preconfigured HW plus preinstalled SW Only HW is delivered Installation to be done by customer (incl. OS) Extensive documentation (guides, SAP notes) available Safeguarding / Solution Validation Done together by SAP and HW Partner SAP HANA Going-Live check offered by SAP AGS Self-managed, customer run infrastructure tests optional SAP HANA HW Configuration Check Tool Support Fully provided by SAP Individual support agreement(s) with HW partner(s) required OS Service Contract Appliance vendor is reseller of OS provider s service contract Customer to care for getting the OS provider s service contract 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 28

29 SAP HANA On-Premise SAP HANA appliance vs. SAP HANA TDI support model SAP HANA appliance model: SAP HANA software pre-installed by certified hardware partners on validated hardware running a specific operating system SAP coordinates all support requests for all components of the system, including hardware, with the responsible partners SAP is the main point of contact for all issues; SAP works with the hardware partner as needed SAP HANA TDI model: Customer is responsible for software installation; the customer is also responsible for defining support agreements with the various partners and for managing support with all the involved partners Customers work with hardware partners on hardware support requirements Supportability tool called the HW Configuration Check Tool for SAP HANA * (documentation attached to SAP Note ) allows customers to check if the hardware is optimally configured to meet the requirements of SAP HANA Customers are also responsible for on-going system maintenance and support, including: initial software installation updating patching the OS and SAP HANA DBMS software 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 29

30 DB Configuration / Virtualization TDI Options

31 Bare Metal Virtualization Bare Metal Virtualization Summary MCOD / MCOS / Virtualization on one SAP HANA hardware unit Productive Systems Classical scenario Appliance approach for optimal performance 1 x Appliance 1 x SAP HANA DB 1 x DB schema 1 x Application (e.g. ERP, CRM or BW) Bare-metal or virtualized White-Listed Scenarios MCOD Multiple Components on one Database 1 x Appliance 1 x SAP HANA DB n x DB schema n x Applications Prod. usage for white listed scenarios allowed, e.g. SAP ERP together with SAP Fraud Management. See SAP notes and MCOS Multiple Components on one System, multi-sid 1 x Appliance n x SAP HANA DB n x DB schema n x Applications Restricted Production Systems (scale-out) E.g. DEV and QA system on one hardware. See SAP note Virtualization (On-Premise) Virtualization technology separates multiple OS images each containing one HANA DB n x Virtualized Appliances n x SAP HANA DB n x DB schema n x Applications See SAP note AS ABAP SID: ABC AS ABAP SID: ABC Application SID: XYZ AS ABAP SID: ABC AS ABAP SID: XYZ AS ABAP SID: ABC AS ABAP SID: XYZ SAP HANA <HDB> Schema ABC SAP HANA <HDB> Schema ABC Schema XYZ SAP HANA <HDB1> Schema ABC SAP HANA <HDB2> Schema XYZ SAP HANA <HDB> Schema ABC SAP HANA <HDB> Schema XYZ 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 31

32 SAP HANA virtualization / multi-tenancy options Horizontal View Multiple Components, one Database (MCOD) Multiple Components / Instances, one System (MCOS, Virtualization) Multi-tenant Database Containers, one HANA Instance (MDC) App X App Y App X App Y App X App Y Schema X Schema Y Database SAP HANA Instance OS HW Schema X Schema Y Database Database SAP HANA Instance SAP HANA Instance OS OS Hypervisor HW Schema X Schema Y Tenant DB Tenant DB SAP HANA Instance OS HW See Notes See SAP Notes See SAP Note SAP SE or an SAP affiliate company. All rights reserved. Customer 32

33 SAP HANA multi-tenancy options SAP HANA Multi-tenant Database Containers (MDC) Multitenant Database Containers provide strong isolation capabilities Each tenant database has its own database admin and end users, database catalog, repository, persistence, backups, traces and logs Tenants Memory and CPU consumption can be configured independently Integration with SAP HANA data center operation procedures, housekeeping, backups (full and/or on tenant level), etc. Application SAP HANA System Application Multitenant Database Containers share one SID and Revision Shared installation of database system software Tenant databases are identified by name or port SAP HANA system replication covers whole system (Sys. DB and tenants) Additive sizing for all tenant database Tenant DB System DB Tenant DB Targeting MCOS-like On-Premise and SAP HANA Cloud scenarios with reasonable amount of tenant databases per system. Cloud-friendly SAP HANA MDC capabilities Elasticity (shrink and grow tenants, move tenants) Security (Separation of provider and customer) Optimized for many small tenants (footprint reduction) 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 33

34 SAP HANA Virtualized Current Status Supported Hypervisors SAP HANA Platform Supported Hypervisors VMware vsphere / ESXi Hitachi LPAR Huawei FusionSphere IBM PowerVM Other Hypervisors Scale-out Single VM Multi VM Single/Multi VM Single/Multi VM General Availability for multiple SAP HANA virtual machines on multiple certified SAP HANA host server in production. General Availability for single SAP HANA virtual machine on a single certified SAP HANA host server in production General Availability for multiple SAP HANA virtual machines on a single certified SAP HANA host server in production Controlled Availability for single or multiple SAP HANA virtual machines on a single certified SAP HANA host server in production Only Supported for Non-Prod Prospects are open source hypervisors like XEN and KVM. SAP Note SAP Note SAP Note SAP Note SAP Note SAP Note SAP Note SAP Note SAP SE or an SAP affiliate company. All rights reserved. Customer 34

35 SAP HANA virtualized General conditions and constraints General guidelines for Virtualization of SAP HANA: o Limited to 2 and 4 socket certified SAP HANA appliance hardware (large 8 socket appliances check with Hypervisor vendor first!!!! ) o CPU & memory overprovisioning and nesting must not be used. o SAP HANA installation was either done 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 SAP HANA Support for Virtualized Environments 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 35

36 SAP HANA on VMware Comparison SAP HANA virtualized vs. MDC Performance of SAP HANA virtualized During performance analysis the majority of tests stayed within 12% performance degradation compared to bare metal. Performance Performance Critical What use cases are a good fit for SAP HANA virtualized: Financial VMs > 512 GB RAM * Performance Non-Performance Critical Financial VMs 512 GB RAM * SAP works closely with hypervisor provider to keep performance overhead minimized This indicates that there are particular scenarios which might not be suited for SAP HANA on VMware. Users > ~500 named users (Business Suite) Technical * > 64 vcpu > 1 TB memory Use Cases: Mission Critical / High-Performance Scenarios Absolute Performance Testing (E2E elapse time) Scale-out / HANA Host Auto-Failover SAP Central System (Business Suite) Users 1:1 (server : user) < ~500 named users (Business Suite) Technical * 64 vcpu 1 TB memory Use Cases: Sandbox / Trial Systems / Development and Test Systems Relative Performance Tests (old vs. new version on VM) High-Available / Disaster Recovery Tolerant System Setup * Relates to VMware vsphere 6.0 release 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 36

37 Datacenter Readiness Capabilities TDI Options

38 SAP HANA Data Center Readiness Quick Overview SAP HANA Data Center Readiness Backup & Recovery Data & Log Backup Point-In-Time Recovery 3 rd -party backup tool support Netbackup, Tivoli, Simpana, DataProtector, Networker, Sesam Storage Snapshots Point-In-Time Recovery High Availability In case of hardware or system failure the standby system takes over in the same data center Several options: storage-based shadow databases Internal or external cluster manager Disaster Recovery Failover to a different HANA instance in another, even far distant data center Automatic and manual procedures possible Several options: storage-based shadow databases External cluster manager Design & Setup Several deployment options Multi-Tenant Database Container NetWeaver Central instance on HANA server Virtualization for production usage Tailored Data Center Integration Dynamic Tiering Security & Auditing Comprehensive security framework Fine-granular authorizations Encryption Compliance (SoD, audit logging,...) Secure hardware / software setup IDM and GRC integration 3rd party via standard / documented interfaces Continuous Improvement of Simplification & Flexibility Starting Page: Features of SAP HANA: Data Center - Enterprise Readiness and HA/DR 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 38

39 High Availability Disaster Recovery Business Continuity High Availability per Data Center Disaster recovery between Data Centers SAP HANA Host Auto-Failover (Scale-Out with Standby) SAP HANA Storage Replication SAP HANA System Replication Performance Optimized Cost Optimized SAP HANA System Replication Performance Optimized Cost Optimized 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 39

40 Storage Connector API Shared Storage SAN Storage Ways to setup High Availability and Disaster Recovery Host Auto-Failover Cluster-like solution One data pool Includes internal cluster manager for micro cosmos Auto-Failover Uses Storage Connector APIs for communication with environment Name server Name server Server 1 Server 2 System Replication Similar to classical shadow database solutions Ambivalent solution for HA & DR Automation possible with external cluster manager (macro cosmos) Primary HANA Automatic Initial Data Load Log Secondary HANA preload Storage Replication Often already used by several customers Usually used for DR Automation possible with external cluster manager (macro cosmos) Primary HANA Secondary HANA preload Name server Server 3 Name server Standby Server Data Log Data Log Data Log Log Data Data Log Covers HW problems with additional host(s) Covers HW and data integrity problems with an additional set of individually driven data pools Covers HW (data center) failures on a broader scale 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 40

41 Worldwide Data Center Setups Multi Tier System Replication Cascading Systems Data Center Data Center Sync Tier 1 Tier 2 Tier 3 Production Local shadow with data preload Remote system/shadow with or without preload (mixed usage together with non-prod. operation) Tier 1 2 Tier 2 3 SYNCMEM ASYNC SYNC ASYNC SAP Note SAP HANA Multitier System Replication supported replication modes between sites with SPS11: ASYNC&ASYNC, SYNCMEM&SYNC (Of course, distance (latency) will rule the use of replication mode options!) 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 41

42 Tools for managing SAP HANA systems and landscapes Which tool to use, for what SAP Solution Manager SAP Landscape Management Use it for: End-to-end root cause analysis and unified alert inbox for entire landscape and for business process reporting Central alerting and monitoring infrastructure Runs on SAP NetWeaver AS for ABAP Use it for: Automation and orchestration of SAP HANA advance operations, accelerating migration projects and centralizing landscape operations Central landscape management solution Runs on SAP NetWeaver AS for Java Native Tools for SAP HANA database administration SAP HANA cockpit SAP DB Control Center SAP HANA studio Use it for: Core administration and detailed monitoring of a single SAP HANA database Web-based SAP Fiori launchpad Runs on SAP HANA XS Classic Use it for: Administration and monitoring of the entire SAP HANA database landscape Web-based SAP Fiori launchpad Runs on SAP HANA XS Classic Use it for: SAP HANA basic administration tasks and development including modeled views Eclipse-based IDE No longer in feature development 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 42

43 SAP Landscape Virtualization Management (SAP LVM) aka SAP Landscape Management 3.0 SAP LVM is a powerful automation solution that helps you simplify and automate the management and operations of your SAP landscapes Further details about Release 2.1, SP3, Videos 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 43

44 Capabilities SAP Landscape Virtualization Management What are customers using it for A Landscape Management B E2E System Copy/Refresh C Managing SAP HANA D Full Setup E As Part of Cloud Transformation Automate operations: start, stop, relocate, mass operations with inter-system dependencies Validations, Notifications Extensibility Landscape Visualization, Dashboards and Reports Storage-Based automated end-to-end SAP system copy, rename and refresh including PCA VM-Based automated end-to-end SAP system copy, rename and refresh including PCA Automate post-copy processing steps for ABAP/Java using PCA Custom Provisioning Centralized Operations and Management such as; start, stop, relocate with built-in support for system dependencies Automate advance operations such as; system clone, copy, refresh, takeover to secondary Accelerate HANA Migration projects using specialized post-copy automation task lists (e.g. BW to HANA migration) Use full functionality provided by LVM Visualize your SAP Landscape, Dashboards, Reports Mass Operations with intersystem dependencies Validations, Notifications Extensibility E2E Automated SAP System Clone, Copy, Rename, Refresh Managing SAP HANA systems and landscapes Use LVM as a provisioning engine for SAP application provisioning & customization execute LVM operations via thirdparty orchestration solutions using template interfaces (e.g. vcac) Use LVM as a front-end within SAP hybrid/private cloud setup for SAP deployments and application customization along with selfservice portal and performance dashboards etc. SAP consulting offering for SAP LVM projects virtualization-services@sap.com 2016 SAP SE or an SAP affiliate company. All rights reserved. Customer 44

45 SAP Landscape Virtualization Management Managing SAP HANA on-premise systems Today Provisioning SAP HANA Systems * System clone, copy, rename and refresh (including synchronized clone) for single-node and multi-node (scale-out) systems Automation for post-copy processing tasks Landscape Management for SAP HANA * Detect, start, stop, monitor and relocate singlenode and multi-node (scale-out) systems Mass operations on systems with in-built support for system dependencies Takeover procedure for SAP HANA replication * SAP LVM use-cases focus on SAP HANA tailored data center integration ** through post-copy automation task list Relevant SAP notes: # , # For additional information on SAP HANA tailored data center integration (TDI), please refer to: SAP SE or an SAP affiliate company. All rights reserved. Customer 45

46 Thank you Contact information: Glen Leslie SAP HANA COE