Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download SAP HANA in Data Centers
Document related concepts
Transcript
SAP HANA in Data Centers Dr. Ralf Czekalla Product & Management Strategy (SAP HANA) August 2015 http://www.saphana.com/docs/DOC-2010 © 2015 SAP SE. All rights reserved. 1 Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent. © 2015 SAP SE. All rights reserved. 3 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 4 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 5 SAP HANA Continuous Availability Customer Expectation: Planned & Unplanned SAP HANA Revisions & SPSs Patches for Data Services and SLT Maintenance Events for OS & Hardware Custom development & enhancements Planned outages ……. Data Center Readiness Hardware failure / Malfunction including Networks Software Malfunction / security threat / update Natural / Man-made disasters Failure of compliance & operation Unplanned outages Unplanned downtime Continuous availability Planned downtime HANA consumption Extended SAP backend deployments © 2015 SAP SE. All rights reserved. 6 SAP HANA Data Center Readiness Quick Overview SAP HANA Data Center Readiness Backup & Recovery Data & Log Backup Point-In-Time Recovery 3rd-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 © 2015 SAP SE. All rights reserved. 7 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 10 SAP HANA - Implications of being an Appliance Classic software delivery on-premise solutions Appliance delivery kind of “SaaS on-site customer” SAP ships only the software SAP defines the solution together with its partners Customer is responsible for entire product lifecycle SAP & partners control product lifecycle Setup/ Consulting SAP Development Software and Licenses Support (Software, Maintenance and Infrastructure) Operation HW- and Technology Partners Infrastructure Customer’s responsibility © 2015 SAP SE. All rights reserved. SAP responsibility Partners' responsibility Appliance Operation Concepts SAP Development Setup / Consulting Software and Licenses Support (Software, Maintenance and Infrastructure) Operation * Infrastructure * * Might be outsourced or owned by customer 11 SAP HANA Platform SAP HANA Technology Partners SAP HANA Hardware Partners Starting with HANA SPS08: Linux on IBM POWER CPUs 1000+ certified appliance solutions (July 2015) © 2015 SAP SE. All rights reserved. 12 SAP HANA scalability Scales from very small servers to very large clusters 12 PetaByte Data Warehouse with SAP HANA Guinness world record Single Server Scale Out Cluster Cloud Deployment • • 2 to n servers per cluster • • Each server is either 4 CPU/1TB or 8 CPU/2TB SAP HANA instances can be deployed to AWS • Limited to developer license • Largest certified configuration: 112 servers • SAP HANA Enterprise Cloud • Largest tested configuration: 250+ servers • Support for high availability and disaster recovery 2 CPU 128GB to 8 CPU 2TB (Special layout for Suite on HANA for up to 12TB per host) • Single SAP HANA deployments for data marts or accelerators • Support for high availability and disaster recovery © 2015 SAP SE. All rights reserved. 13 Certified Intel IvyBridge/Haswell-EX Hardware CPUs Sockets ⅛TB ¼TB ½TB >½TB <1TB 1TB 2 2 2 2 4 4 2-4 2-4 2-4 2-4 4-8 4-8 1.5TB 4 BW or Datamart Suite Memory Sizes July 2015* (available now) X X X 4-8 X 2TB 3TB <2TB 2TB 3TB 4-6TB 4 4 8 8 8 8 4-8 4-8 8 8 8 8 8-12TB 16 16 X X X X X X X X X X X X/X X/X X/X X/X X/X X/X X/X X/X X/X X X/X X/X X/X X/X X X/X X/X X/X X/X X X/X X/X X/X X/X X/X X X/X X/X X/X X/X X/X X/X X X/X X X/X X X/X X/X X X/X X X X X X X X/X X/X X/X X/X X/X X/X X/X X/X X/X X/X X/X X/X X X/X X X/X X X X X/X X X/X X X/X X/X X X/X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X controlled available Inst. image with virtualization X X X Support for SUSE SLES‡ X X X X X X Support for RedHat X X/X X/X X/X X/X X/X X/X general available* X RHEL‡ X X X X X X planned X X X X X X X X X X X X ‡ Distributions for SAP Applications * For most up to date list please go to the Certified SAP HANA Hardware or http://scn.sap.com/docs/DOC-52522 © 2015 SAP SE. All rights reserved. 14 Certified Intel IvyBridge/Haswell-EX HANA Hardware Sockets BW or Datamart Suite CPUs Memory Sizes July 2015* (available now) Scale-Out Scale-Out ½TB 2 2-4 X X ½TB 4 4-8 X X/X 1TB 4 4-8 X X/X X/X 1.5TB 4 4-8 X X X 1TB 8 8 X 2TB 8 8 X X 3TB 8 8 X X 4TB 8 8 R 6TB 8 8 R 12TB 16 16 R X X X X X X X X X X X X X X X X planned planned HA – Host Auto-Failover X X X X X X X DR – Storage Repl.: Sync X X X X X X X X X X planned DR – Storage Repl.: Async X X X R: restricted availability (Pilot program: SAP note 1781986, SAP note 1950470, SAP note 2075461) * For most up to date list please go to the Certified SAP HANA Hardware or http://scn.sap.com/docs/DOC-52522 © 2015 SAP SE. All rights reserved. 15 Relaxed HW Specifications for Non-Production Notes: Hardware still from PAM or ICC o SAP Product Availability Matrix or Processor http://scn.sap.com/docs/DOC-52522 Non-prod: Sizing flexible o Instances can be combined o SoH layouts can be used for BW Memory Storage Intel Xeon E7 Westmere Ex (E7-x8xx v1) or IvyBridge EX (E7-x8xx V2) Intel Xenon E5 - (E5-26xx v2/v3, min. 8 cores); 2 socket, up to 1.5TB; scale-up only 128 GB of RAM to Maximum memory supported on the box Size: 2x Memory - Any local storage or shared storage w/ standard disk on proven file systems GPFS (IBM only), NFS or XFS w/ Raid 0 and above Network Operating System Standard networking components SUSE Linux 11.x or Red Hat 6.5 Virtualized or Bare Metal Performance related support will only be provided on Production grade hardware (Certified hardware) © 2015 SAP SE. All rights reserved. 16 SAP HANA Tailored Data Center Integration Customer Feedback & Challenges and alternative Concept SAP HANA tailored data center integration is an additional option to the existing appliance model HANA HANA Server HANA Server Server Storage Limited flexibility in server/ storage combinations (well defined packages) Established IT operation processes have to be adapted slightly Well defined HW and performance KPIs Reduce hardware and operation cost at installed based customers Mitigate risk and optimize time to value by taking more responsibility Gain additional flexibility in hardware vendor selection * HANA HANA Server HANA Server Server (Corp.) Storage * Please contact for joining pilot phase: [email protected] © 2015 SAP SE. All rights reserved. 17 SAP HANA Tailored Data Center Integration A continuous journey towards openness SAP HANA TDI Phase 2: Shared Enterprise Networking Phase 3: Entry-level SAP HANA E5 servers SAP HANA TDI Phase 1: Shared Enterprise Storage SAP HANA TDI Phase 4: SAP HANA servers with Linux on IBM Power CPUs SAP HANA Appliance GEN 3 Intel Xenon EX Haswell (E7 v3) SAP HANA Appliance GEN 2 Intel Xenon EX IvyBridge (E7 v2) Today: SAP HANA Appliance GEN 1 Intel Xenon EX Nehalem & Westmere (E7 v1) 20112012 © 2015 SAP SE. All rights reserved. Oct. 2013 Feb. 2014 More than 1000 certified SAP HANA configurations available for nearly every customer budget and use case Nov. 2014 Mid. 2015 18 SAP HANA Tailored Data Center Integration The concept SAP HANA tailored data center integration is an additional option to the existing appliance delivery model Virtualization Application Database HANA HANA Server HANA Server Server Operating System HANA HANA Server HANA Server Server Network Storage SAP HANA appliance delivery © 2015 SAP SE. All rights reserved. Server certified Virtualization Network Server Storage defined defined Shared Network Enterprise Storage Storage certified SAP HANA tailored data center integration 19 SAP HANA Tailored Data Center Integration What‘s in it for you? Reduce hardware and operation cost by reusing existing hardware components and operation processes Mitigate risk and optimize time to value by enabling existing IT Management processes for SAP HANA implementation Gain additional flexibility in hardware vendor selection by Leveraging the existing ecosystem © 2015 SAP SE. All rights reserved. 20 SAP HANA Tailored Data Center Integration Differentiating Capabilities SAP HANA tailored data center integration SAP HANA appliance delivery Fast Implementation More Flexibility and Responsibility Support fully provided by SAP Save IT budget and existing investment Application HANA HANA Server HANA Server Server Database Operating System Virtualization Server Storage • • Network Storage © 2015 SAP SE. All rights reserved. • Solution validation done by SAP and partner Preconfigured hardware set-up Preinstalled software • • Installation and validation needs to be done by customer Customer aligns with the hardware partner on individual support model Virtualization HANA HANA Server HANA Server Server Server Network Shared Network Enterprise Storage Storage 21 SAP HANA Tailored Data Center Integration Prerequisites for Enterprise Storage Requirements: HANA HANA Server HANA Server Server Server - Only servers listed in the SAP HANA Product Shared Network Enterprise Storage Storage Availability Matrix are supported. Configuration adjustments like: ● No local disks, no flash cards required ● Additional FibreChannel adapters for SAN boot are allowed Storage – All storages successfully passed the SAP HANA Hardware Certification. For more information, see Partner Information Center or contact [email protected] SAP HANA Installation – Needs a certified expert (internal or external) to be executed ● ● The exam “SAP Certified Technology Specialist (Edition 2013) – SAP HANA Installation” (E_HANAINS141) needs to be passed successfully to perform SAP HANA installations at customer side. You get prepared for this exam with SAP training HA200. For more information, see SAP Training and Certification Shop (Requirements) © 2015 SAP SE. All rights reserved. 22 SAP HANA Tailored Data Center Integration Certified Partner Enterprise Storage Solutions (July 2015*) Storage Partners & certified storage solutions*: Certified Enterprise Storage for SAP HANA Dell EMC Fujitsu Compellent Symmetrix ETERNUS SC8000 VMAX DX VMAX DX200 S3 10K (2 contr.) VNX Unified Storage Systems VNX 5400 VMAX3 Family VMAX3 100K FusionIO Hitachi IONAccelerator R720 Enterprise Storage VSP (2010) HP Huawei IBM NetApp Pure Storage Violin FA-400 Series FA-405 6200 Series Flash 6264 (link) 3PAR StoreServ 7400 OceanStor Storage S5500T Flashsystem 820 E-Series E-5600 Enterprise 3PAR Storage StoreServ VSP G400 20800 OceanStor Storage 5500 V3 Storwize V7000 (SVC) FAS Series FAS 8060 Family Elastic Storage Server GS2 FAS Series FAS 8080 Family XP Storage XP7 XtremIO Storage Array DS8070, DS8000 Family XIV Storage 2810 * For most up to date list please go to Certified Enterprise Storage for SAP HANA © 2015 SAP SE. All rights reserved. 23 SAP HANA Tailored Data Center Integration Data Throughput and Latency KPIs for Production SAP HANA Systems Volume Log Data Block Sizes Test File Size KPIs Initial Write (MB/s) Overwrite (MB/s) Read (MB/s) Latency (µs) 4K 5G n.a. 30 n.a. 1000 16K 16G n.a. 120 n.a. 1000 1M 16G n.a. 250 500 n.a. 4K 5G n.a. n.a. n.a. n.a. 16K 16G 40 100 n.a. n.a. 64K 16G 100 150 250 n.a. 1M 16G 150 200 300 n.a. 16M 16G 200 250 400 n.a. 64M 16G 200 250 400 n.a. Source: SAP HANA Administration Guide section 2.7: Hardware Checks for Tailored Data Center Integration or SAP Note 1652078 – SAP HANA database: Hardware check MB/s == MByte/s Storage Requirements paper: http://scn.sap.com/docs/DOC-62595 © 2015 SAP SE. All rights reserved. 24 SAP HANA Tailored Data Center Integration Hardware Configuration Check Tool (HWCCT) 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 o Does not require SAP HANA SW being installed beforehand o Uses the same libraries for file system access and the same IO patterns as SAP HANA does Download it from SAP Service Marketplace o Navigation path: Software Downloads -> Support Packages and Patches -> A - Z Index -> H -> SAP HANA Platform Edition -> SAP HANA PLATFORM EDIT. 1.0 -> Entry by Component -> HANA config check -> SAP HANA HW CONFIG CHECK 1.0 -> Linux on x86_64 64bit -> HWCCT_80_020011536.SAR) Documented in the SAP HANA Administration Guide o Contains the latest KPIs o For latest docu changes, see PDF attachment of SAP Note 1943937 o SAP Note 1652078 – SAP HANA database: Hardware check Important: There is no Self-Certification, but a Self-Assessment © 2015 SAP SE. All rights reserved. 25 SAP HANA Storage Layout Disk sizing with class. HANA appliance vs. HANA TDI Classical SAP HANA Appliance SAP HANA Tailored Datacenter Integration “0.5:3:1” Disk layout “0.5:1:1” Disk layout 0.5 x RAM 512 GB* Log 0.5 x RAM 512 GB* 3 x RAM Data 1 x RAM 1 x RAM Shared/Trace 1 x RAM Reason for comfortable sizing: Appliance can not always be changed on short notice (add more disks) depending on the general design, etc. for the HW partner offering of choice. Source: SAP HANA Administration Guide (to be updated to latest changes) * Minimum value for every size above 512 GB - more might be necessary depending on very high workload situations (transactional load) © 2015 SAP SE. All rights reserved. (< 512 GB RAM) (≥ 512 GB RAM) Reason for reduced sizing: Customers can change disk layout (extensions of disk areas) on short notice because they are responsible for the complete HANA Stack Source: SAP HANA Storage Requirements Whitepaper (SAP note 1900823 or SCN) * Minimum value for every size above 512 GB - more might be necessary depending on very high workload situations (transactional load) 26 SAP HANA Tailored Data Center Integration The way we went so far… General Availability – Storage: The storage layer is the first layer to be opened up. HANA HANA Server HANA Server Server SAP HANA tailored data center integration – Enterprise Storage has already served more than 50 customers during a pilot program and is generally available since in Q4/2013. Shared Network Enterprise Storage Storage General Available – Network: HANA HANA Server HANA Server Server Network SAP HANA tailored data center integration – Enterprise Network was started for a limited number of customers in December 2013. Further information are available in Network Requirement Paper and defines the requirements for network devices and products which are usable for SAP HANA environments. Shared Network Enterprise Storage © 2015 SAP SE. All rights reserved. For further questions feel free to contact us: [email protected]. 27 SAP HANA Tailored Data Center Integration Enterprise Network Data Center 1 Application Server (ABAP, XS) Data Center 2 HANA Client (BI client, HANA Studio, ...) 1 Application Server (ABAP, XS) Data Sources 5 SAP HANA Server SAP HANA Server Node 1 Node 2 4 SAP HANA Server SAP HANA Server SAP HANA Server SAP HANA Server Node 3 Node 4 Node 1 Node 2 6 Enterprise Storage 7 1 Application Server Network 2 Client Network Internal zone: 4 Internode Network Storage zone: 6 Enterprise Storage Network 7 Backup Network 3 4 SAP HANA Server SAP HANA Server Node 3 Node 4 6 Backup Client zone: Data Sources 2 1 3 2 HANA Client (BI client, HANA Studio, ...) Enterprise Storage 7 Backup 3 Data Source Network 5 System Replication Network More details available in SAP HANA documentation: SAP HANA Master Guide, chapter 2 "The SAP HANA Network“ Network Requirement Paper with further details © 2015 SAP SE. All rights reserved. 28 SAP HANA Tailored Data Center Integration Enterprise Network Recommendations: All recommendations mentioned refer to the usage in productive environments HANA HANA Server HANA Server Server Network Segmentation – All networks need to be properly segmented Network Shared Network Enterprise Storage and may be connected to the same core/ backbone switch. Note: Network security and segmentation is a function of the network switch vendor and must be configured according to the specifications of the switch vendor. For more details on network security see the SAP HANA Security Guide, chapter 4. Bandwidth ≥ 10 GbE for Internode and Backup Network ≥ 10 GbE (Ethernet) or ≥ 8 GbF (FibreChannel) for Enterprise Storage Network Redundancy – It depends on the customer’s high-availability requirements if and how to apply redundancy for the different SAP HANA network segments. SAP strongly recommends to make the following networks redundant: ● Internal zone (Internode and System Replication networks) ● Storage zone (Enterprise Storage and Backup Storage networks) Fully redundant switches and routers are recommended. © 2015 SAP SE. All rights reserved. 29 SAP HANA Tailored Data Center Integration Recent changes and Outlook HANA HANA Server HANA Server Server Server Shared Network Enterprise Storage General Availability – Server options: More CPU flavors are introduced: Intel Xeon E5 for non-production and production Scope o Single Box, only Scale-Up o Intel Xeon 2 socket E5 26xx up to 1,5 TB (no 4 socket solutions) o Sizing process with NEW SAP HANA Quick Sizer o Lists with HW solutions with SCN as “Supported Entry Level Systems” SAP HANA on Linux for IBM Power8 Ramp-Up Scope o BWonH o No Scale-Out o SAP Note: 2133369 - SAP HANA on IBM Power Systems: Central Release Note o Only IBM Power 8; previous IBM Power architectures only for non-prod operation with SAP HANA Soon SoH on Linux for IBM Power CPUs Hardware partitioning Current status presented in SAP Note 1788665 o Hitachi LPAR o HP nPartitions CS900 „HANA Hawk“ (SAP Note 2077823) o Fujitsu pPAR (SAP Note 2077823) © 2015 SAP SE. All rights reserved. 30 SAP HANA Scale-Out “Extension” Heterogeneous Landscapes Supported with the following constraints: Certified SAP HANA scale out hardware from the same HW partner Same memory on each node (e.g. 512 GB per node) Distributed tables: Slowest part of a cluster will define the overall performance Mixture of two Intel CPU generations per cluster will be supported (e.g. Intel Westmere EX & IvyBridge EX) Scale-Out cluster members new CPUs new CPUs new CPUs old CPUs old CPUs old CPUs old CPUs x TB old CPUs Aim is to increase the size of the database, not primarily the performance CPU power © 2015 SAP SE. All rights reserved. 31 Fulfilling IT compliance (IT policies) for Data Centers Data Center compliances usually define specific topics to Managing, Monitoring and Backup & Restore tools Central user management with IDM tools Anti Virus software usage mandates OS security patches, firewalls Etc. Additional 3rd party tools required to complete these compliances are tolerated with following restrictions Neither SAP nor hardware vendor offers support for tools which are not official part of the SAP HANA BOM. The hardware vendor is tolerating the installation and operation of this compliance-related software. Customers might be asked to stop these tools in case of a support issue and to enable reproduction of the problem No closed source driver are allowed with these compliance tools without further support agreement of the vendor with SAP for these © 2015 SAP SE. All rights reserved. Tool Vendor Customer SAP HW Partner HW Partner Tool set 32 Technical Operational Manual for SAP HANA SAP offers a technical operational manual (TOM) with all kinds of topics about operating SAP HANA as an appliance (http://help.sap.com/hana_platform). This manual should be taken as input for further adaptations of the operation of SAP HANA in customers’ Data Centers. The needed regular duties around the operation of SAP HANA can be derived from this document. Usually HANA needs lesser administration than other databases, typical duties are: Regular backups (Database, Bare-Metal software and configuration backup) Patches; usually on demand in case of problems or known issues (DB, OS) Monitoring (automated or manual) © 2015 SAP SE. All rights reserved. Table: Cited from SAP HANA TOM Task Responsible SAP HANA appliance installation Hardware Partner Hardware Hardware Partner OS installation Hardware Partner OS updates Customer SAP HANA updates Customer Data source connectivity Customer BI Client installation Customer SAP HANA software support SAP 33 Project Cost Analysis (TCO) by Forrester Cost Savings Enabled By Transitioning to the SAP HANA platform Further documentation available on: www.sap.com/innovation-and-me Unlock business value and deliver breakthrough innovation while simplifying IT Executive Summary Full paper (with free registration) © 2015 SAP SE. All rights reserved. 34 Joined SAP HANA and SAP NetWeaver ABAP Application Server and HANA Database on one hardware SAP HANA and SAP NetWeaver AS ABAP deployed on one server is a multicomponent, resource and cost optimized deployment approach SAP HANA Server SAP HANA System SAP NW AS ABAP Server SAP HANA Server SAP NW AS ABAP System SAP NW AS ABAP System SAP HANA System Separated deployment approach SAP HANA and SAP NetWeaver AS deployed on one server Hardware resources isolated Cost optimized approach Separate hardware Shared Memory and CPU resources © 2015 SAP SE. All rights reserved. 37 Joined SAP HANA and SAP NetWeaver ABAP Application Server and HANA Database on one hardware SAP HANA and SAP NetWeaver AS ABAP deployed on one system is available since December 16, 2013. SAP HANA Server SAP NW AS ABAP System SAP HANA System © 2015 SAP SE. All rights reserved. Availability For all productive and non-productive SAP HANA SPS7 single node installations. All products based on SAP NetWeaver AS ABAP 7.4 are supported. Requirements ● Additive sizing: Additional memory resources for the SAP NetWeaver AS ABAP system needs to be available on the SAP HANA server. For more information, see memory sizing based on SAP Release Note - 1953429 ● Separate SID‘s for both systems required SAP HANA software installation The exam “SAP Certified Technology Specialist (Edition 2013) – SAP HANA Installation” (E_HANAINS131) needs to be successfully passed for a person to perform SAP HANA software installations. For more information, see SAP Training and Certification Shop 38 Joined SAP HANA and SAP NetWeaver High Availability setup based on System Replication Data Center 1 Data Center 2 SAP HANA Server SAP HANA Server SAP NW AS ABAP System SAP NW AS ABAP System ABAP SID <ERS##> ABAP SID <ERS##> ABAP SID <DVEBMGS##> Shared File System ABAP SID <DVEBMGS##> ABAP SID <ASCS##> ABAP SID <ASCS##> SAP HANA System (Primary) SAP HANA System (Secondary) © 2015 SAP SE. All rights reserved. SAP HANA System Replication 39 Sizing Process with SAP HANA Customer Requirements • Performance • Business SLAs • Business figures Sizing Recommendation CPU (SAPS) Memory (GB) Disk Space (GB) Component performance Final Sizing • • Scalable HW offering Practical sizing Experience • Different configurations • Different technology partners Hardware Vendor • Sizing Tools & Reports • Sizing Guidelines • Sizing Verification © 2015 SAP SE. All rights reserved. HW partner responsible SAP 40 Sizing with SAP HANA installations Sizing Scenarios Available Tools/Resources Sizing New Applications “Initial Sizing” 1. SAP QuickSizer tool 2. SAP Note 1793345 Migrating to SAP HANA Applications “Productive Sizing” 1. Stand-alone HANA: SAP Note 1514966 2. SAP Business Suite or Industry Solutions Powered by SAP HANA: SAP Note 1872170 3. SAP NetWeaver BW Powered by SAP HANA: SAP Note 1736976 Sidecar Scenarios Sizing 1. SAP HANA Enterprise Search: SAP Note 1872170 2. CO-PA Accelerator: HANA Sizing for CO-PA Accelerator 3. SAP Applications on HANA: SAP QuickSizer Tool 1. Please check SAP HANA Sizing Overview for latest updates. 2. Consider Sizing paper for SAP HANA 3. General statement: “Prefer a scale-up before starting to scale-out to multiple boxes” (SAP HANA Scalability document Chapter 4.5) 4. Special requirements for BW and Scale-Out: SAP note 1736976 check attachments © 2015 SAP SE. All rights reserved. 41 SAP HANA Virtualized – The Big Picture Supported Deployment Options for SAP HANA Virtualized ABAP HANA4 SAP HANA HANA ABAP HANA1 HANA2 HANA3 SLES RHEL Win * RHEL SLES SLES VM1 VM1 VM2 VM1 VM2 HANA3 HANA1 SLES SLES VM3 VM1 VM2 HANA2 SLES RHEL VM3 VM4 ESXi / LPAR ESXi / LPAR ESXi / LPAR ESXi / LPAR ESXi/ LPAR ESXi/LPAR host host host phost phost phost 1x HANA + other Multi VM MCOS Scale-out ✔ ✔ ✔ ✔ ✔ General Support for single SAP HANA virtual machine on a dedicated SAP HANA certified server in production (without overprovisioning and with resource priority configured over other VMs) Controlled Availability for multiple SAP HANA virtual machines on single SAP HANA certified server in production General support for single or multiple SAP HANA virtual machines in combination with MCOS for production Controlled Availability for SAP HANA scale-out configurations in virtualized environment, either production or nonproduction until further testing had been finalized. General Support for multiple SAP HANA database installations on one System / OS in production Single VM ✔ General Support for single SAP HANA virtual machine on a dedicated SAP HANA certified server in production SAP Note 1995460 SAP Note 2063057 ** © 2015 SAP SE. All rights reserved. SAP Note 2024433 ** SAP Note 2063057 ** SAP Note 1681092 MCOS * Windows guest OS currently not supported with Hitachi LPAR for SAP workloads ** Access to SAP Note is restricted to participants of Controlled Availability 42 SAP HANA Virtualized Current Supported Hypervisors Currently, the only SAP supported virtualization solutions for running SAP HANA virtualized are 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) for production and nonproduction use cases. VMware vSphere 6.0 support by SAP HANA planned for 2015. The following general conditions & constraints for running SAP HANA virtualized: Limited to 2 and 4 socket certified SAP HANA appliance hardware (large 8 socket appliances are not supported) CPU & memory overprovisioning must not be used 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 preconfigured as certified SAP HANA appliance, with hypervisor installed by SAP HANA hardware partner. See SAP Note 1788665 – SAP HANA Support for Virtualized Environments © 2015 SAP SE. All rights reserved. 43 SAP HANA Virtualized SAP HANA on VMware vSphere in production SAP has released SAP HANA on VMware vSphere 5.5 for general availability, allowing to go live with SAP HANA on VMware vSphere 5.5, provided the following conditions have been met: Single SAP HANA virtual machine on a dedicated 2 or 4-socket SAP HANA certified server Multiple SAP HANA virtual machines on a single physical server o SAP HANA multi-node / scale-out deployment configurations in controlled availability o No 8-socket hardware configurations Both, SAP HANA appliance and SAP HANA Tailored Datacenter Integration (TDI) delivery methods are supported for SAP HANA on VMware vSphere. o The maximum size of a virtual SAP HANA instance is limited by the maximum size of a virtual machine on VMware vSphere 5.5 release, which is 64 vCPUs and 1 TB of memory (limited by VMware, not SAP HANA). o No CPU and/or Memory overcommitting o VMware Vmotion (hot move) or VMware-HA are supported See SAP HANA Guideline for Being Virtualized with VMware vSphere http://www.saphana.com/docs/DOC-4192 © 2015 SAP SE. All rights reserved. 44 SAP HANA Virtualized Current Status Supported Hypervisors SAP HANA Platform Supported Hypervisors VMware Hitachi Other vSphere / ESXi LPAR Hypervisors Single/Multi VM Scale-out Single VM Multi VM Single/Multi VM ✔ ✔ ✔ ✔ General Support for single SAP HANA virtual machine on a single certified SAP HANA host server in production Controlled 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 SAP Note 1995460 SAP Note 2024433 SAP Note 2063057 Controlled Availability until further testing had been finalized. © 2015 SAP SE. All rights reserved. Not Supported until further testing had been finalized. 45 SAP HANA Virtualized Technology Roadmap Today Support for SAP HANA on VMware in non-production scenarios Support for single-VM SAP HANA on VMware in production Controlled Availability for multi-VM scenarios in production Controlled Availability for scale-out scenarios in production Multi VM support (in CA) Complement deployment options Single VM production support © 2015 SAP SE. All rights reserved. H2/2014 8 socket hardware Support of additional hypervisors Add variety Support of larger VMs (4 TB) Support for 8 socket HW Support of additional hypervisors H1/2014 GA vSphere 6 Large VM support (4TB) Extend platform support support for Hitachi LPAR On Roadmap SAP HANA on VMware vSphere on SCN BWoH Scale-out (in CA) GA H1/2015 H2/2015+ This is the current state of planning and may be changed by SAP at any time. (CA) Controlled Availability - (GA) General Availability - (BWoH) SAP business Warehouse, powered by SAP HANA 46 SAP HANA Virtualized Comparison SAP HANA virtualized vs. native, based on VMware vSphere 5.5 What use cases are a good fit for SAP HANA virtualized: During performance analysis the majority of tests stayed within 12% performance degradation compared to bare metal. However, there are around 100 low-level performance tests in the test suite exercising various HANA kernel components that exhibit a performance degradation of more than 12%. This indicates that there are particular scenarios which might not be suited for HANA on VMware. © 2015 SAP SE. All rights reserved. Performance Performance Critical Financial VMs > 512 GB RAM * Performance Non-Performance Critical Financial VMs ≤ 512 GB RAM * Users > ~500 named users (Business Suite) Technical > 64 vCPU * > 1 TB memory * Users 1:1 (server : user) < ~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) 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 5.5 release 47 SAP HANA Virtualized VMware vSphere Features Supported with SAP HANA The VMware vSphere 5.5 support for SAP HANA in production also covers the following VMware vSphere products / capabilities: Use of VMware HA to protect operating system or vSphere host hardware failures SAP HANA System Replication or Storage based replication plus VMware SRM to provide disaster protection The use of VMware vMotion in conjunction with DRS rules The use of additional non-SAP HANA VMs on SAP HANA server Use of snapshots and cloning capabilities © 2015 SAP SE. All rights reserved. Local DC A Remote DC B HANA System Replication OR Storage Replication and SRM Live Migration via VMware vMotion Local failover via VMware HA HANA VM VM HANA* VMware vSphere Cluster HANA Replica VMware vSphere Cluster VMware vSphere VMware vSphere VMware vSphere vSphere Host A vSphere Host B vSphere Host C 48 SAP HANA Virtualization & Multi-tenancy Options Horizontal View One Schema per DB Multiple Schemas One or more SAP HANA Databases One SAP HANA Database (whitelisted scenarios) App App Schema Schema Database SAP HANA Instance SAP HANA Instance Multiple SAP HANA instances on one SAP HANA virtualized HW appliance (e.g., VMware) Multiple tenant databases One HANA Instance App X App Y App X App Y App X App Y Schema X Schema Y Schema X Schema Y Schema X Schema Y Database SAP HANA Instance Database Database SAP HANA Instance SAP HANA Instance OS OS Tenant DB Tenant DB SAP HANA Instance OS OS Hypervisor OS HW HW HW HW SAP Note 1681092 for MCOS approval with HANA SPS09 See Notes 1661202 See SAP Note 1788665 See SAP Note 2096000 © 2015 SAP SE. All rights reserved. + 1826100 49 SAP HANA Multitenant Database Containers Overview System Database AS ABAP App 1 App N System-wide parameter settings Complete backup of all databases Static resource management across all databases (CPU, memory, disk for specific database) Tenant Database DB Schema DB Schema DB Schema Tenant 1 Tenant 2 Tenant N System DB Shared HANA Hardware Multiple strictly separated database tenants on one HANA system Tenant specific life cycle management including backup/ restore Clear separation of application data and user management Local user management within each tenant-DB Session and transaction management per tenantDB Move/copy of tenant-DBs to other systems/hosts Future Roadmap: Support for cloud provisioning scenarios planned for delivery with next Steps © 2015 SAP SE. All rights reserved. 50 SAP HANA Multitenant Database Containers Overview SAP HANA multi-tenant database containers (MDC) Support for multiple tenant containers within a single system database Initial focus on the following scenarios: SAP HANA Cloud Platform SAP HANA Enterprise Cloud Replace most MCOS deployments (Multiple Components One System) Address common MCOD scenarios (e.g. ERP-CRM-BW, QA/DEV, Data Marts) Cross scenario support: Fast federation between tenant databases (read only with SPS09) Typically scenarios with a database with ‘relatively’ small number of tenants i.e. Typically for ~10s of tenants vs. 1000s of tenant databases © 2015 SAP SE. All rights reserved. Application Application SAP HANA System System DB Tenant DB Tenant DB 51 SAP HANA Multitenant Database Containers Integration in Operations A SAP HANA multitenant database containers system has one SID and one HANA software version ● Shared installation of database system software ● Tenant databases are identified by name or port ● Additive sizing for all tenant database Strong isolation features, each tenant database has its own: ● Database admin and end users, database catalog, repository, persistence, backups, traces and logs ● Tenant database related parameter settings ● Tenants memory sizing and CPU consumption can be configured independently ● Clear separation of application data and user management ● One HA/DR setting for a SAP HANA system: all tenants are included in a HA/DR scenario AS ABAP Connect to: HAN.DB’A’ Any Application Connect to: HAN.<port> SAP HANA SID: HAN HAN.SystemDB HAN.DB A HAN.DB B Integration with SAP HANA data center operation procedures, housekeeping, backups, etc. SAP Note 2096000 for further information (released with SPS09) © 2015 SAP SE. All rights reserved. 52 SAP HANA Multitenant Database Containers Positioning multitenant database containers Multitenant Database Containers vs. Virtualization HANA SystemDB Multitenant Database Containers Lower TCO, single software stack Central configuration & administration (database level) Direct database resource management Optimized federation (performance benefits) Performance advantages (no virtualization overhead) Licensed via SAP HANA OS VM+OS VM+OS HANA HANA VM+OS VM+OS HANA HANA HANA Tenant Virtualization Strong isolation Separate SAP HANA revisions option Standard federation (SDA) Additional virtualization license (e.g. VMWARE) © 2015 SAP SE. All rights reserved. 53 SAP HANA Multitenant Database Containers Scale-out scenario with multitenant database containers Tenant databases can spread over multiple nodes (hosts) in scale-out systems Example: If host 2 goes down, the standby host becomes active. The tenant DBs normally running on host 2 will become active on the standby host SAP HANA System System DB System DB (standby) System DB (standby) Tenant DB A.1 Tenant DB A.2 Tenant DB A.3 Tenant DB B.1 Tenant DB C HOST 1 © 2015 SAP SE. All rights reserved. System DB (standby) Tenant DB B.2 Tenant DB D HOST 2 HOST 3 Standby (HOST 4) 54 SAP HANA Multitenant Database Containers Migration to a Tenant Database Preparation Conversion SAP HANA version providing the MDC features (>=SPS09). command: hdbnsutil –convertToMultiDB results in: Remove or migrate the statistics server according to documentation Shutdown the system: HDB stop Setting the "multidb mode" flag in configurations Creating the System DB Converting the original single DB to a tenant DB with name <SID> Updates the Secure Store With initial HDB start , only the SystemDB will start up. Connect to the SystemDB either with hdbsql -d SystemDB (recommended) or via SQL Port 3xx13 Start the new tenant database: ALTER SYSTEM START DATABASE <SID> Traces and configurations for any tenant DB are now stored in a respective subfolder DB_<dbname>. © 2015 SAP SE. All rights reserved. 56 SAP HANA – Variety of deployment options In the Cloud In the Data Center HANA developer edition free of charge Bare metal single Server pre-configured & validated stack SAP HANA One / HANA one premium pay per use Scale-Out / HA & DR cluster scalable from single node to Geo cluster SAP HANA Enterprise Cloud 24/7 mission critical / Enterprise Support Virtualized with VMware VMware vSphere 5.1 or newer http://www.saphana.com/docs/DOC-4184 © 2015 SAP SE. All rights reserved. 57 Cloud offerings SAP HANA in the Cloud ● SAP HANA Developer Edition o o o o For product evaluations, trials, students, data exploration projects, etc. Software is free, developers pay cloud provider for server usage. Community supported through http://saphana.com/cloud Available of choice on 4 public cloud providers ● SAP HANA One o Non-productive and productive usage o Option 1 - with community support according SAP Note 1798212 o Option 2 - with full SAP support through OSS as part of SAP HANA One premium license o Available of choice on 4 public cloud providers © 2015 SAP SE. All rights reserved. 58 SAP HANA Enterprise Cloud o Standards based cloud operation Enterprise-class cloud offering for o Monthly External Penetration Tests mission critical global 24 x 7 operation cloud elasticity Open for any data footprint Any valid SAP HANA T-shirt size o Global Availability (4 data centers in US and Europe, 2 more planned in APJ) Full SAP support through OSS o Custom data center arrangements for compliance o Advanced business continuity and support SAP HANA Enterprise Cloud SAP Business Suite SAP Business Warehouse Custom Apps ERP | CRM | … Services BW | BPC Big Data | Consumer Assessment Onboarding & Migration Cloud Hosting & Managed Services Custom Services SAP HANA Cloud Platform In-memory Infrastructure © 2015 SAP SE. All rights reserved. 59 The Path to BW powered by HANA 1 2 3 4 5 Start: BW with any DB Preparation: Fulfill HANA-DB Prerequisites Proposed: Consider Additional Aspects Target: BW powered by HANA Future: Potentials from BW p.b. HANA using a) • BWA SAP BW 3.x/7.x • • any DB • • • • SAP BW Release Upgrade: min. Release BW 7.30 SP5 Release Upgrade for additional components (e.g. SEM-BCS)? Single Stack Separation: Separate ABAP and JAVA Check Modifications Convert Unicode JAVA Upgrade Migrate Authorizations to 7.x-Concept • b) c) d) e) f) g) Sizing of required HANA DB incl. HW/ SW investment Definition of future System Landscape (incl. DR/ HA – Single Node/ Scale Out) Housekeeping: Reduction of to be migrated data volume Data Aging Concept NLS/ Archiving + Temperature-Concept Assess new Release Features Optimize Data Models & Check Native HANA Data Models Check New Frontends (incl. UI5, Fiori, Design Studio, Analysis Office, Mobility) Complete HANA Strategy (BW = EDW, Operational Reporting, Suite on HANA, HANA Live, Fiori, UI5, …) SAP BW 7.40 SP6+ HANA Link BW-Cookbook © 2015 SAP SE. All rights reserved. 64 The Path to ERP powered by HANA 1 2 3 4 5 Start: ERP with any DB Preparation: Fulfill HANA-DB Prerequisites Proposed: Consider Additional Aspects Target: ERP powered by HANA Future: Potentials from ERP p.b. HANA using SAP ERP 6.7 SAP ERP 6.x any DB • Sizing (SAP Note 1872170) • Data Center: Architecture • Archiving: Evaluate potential of data archiving • Stack Separation: Separate ABAP and JAVA Stack • Unicode: Unicode Conversion required • Add-Ons: Verify add-on compatibility (SAP Notes 1760306, 1855666) • Released Scenarios: Verify released scenarios (SAP Note 1768031) • Functional Correctness (SAP Note 1935918) © 2015 SAP SE. All rights reserved. • Improved Business Processes: Evaluate usage of improved standard transaction (SAP Note 1761546) as well HANA as Industry specific improvements • Operational Reporting: Leverage SAP HANA Live Content as the basis for realtime operational reporting • Custom Code Optimization: Monitor your system using SQLM / User Procedure Logging or Individual Traces • Fiori: Improve End-User Experience by • Business Re-Engineering: implementing SAP Fiori Redefine existing business • Simplify: Reduce complexity & interfaces processes by eliminating existing apps and dbs by • New Business Models: moving them to SAP HANA Establish new business • Search: Evaluate usage of Google-Like models using ERP on HANA Search Capabilities 65 SAP HANA Release Strategy Retrieve incremental, but non-disruptive SAP HANA innovation Updates shipped for SAP HANA are strictly downward compatible. Incompatible changes may be considered due to legal or security reasons, but follow a strict exception approval process (Time-less Software). These Updates are shipped with SAP HANA Support Package Stacks (SPS), delivered from within one delivery stream and without additional ramp-up. SPS are planned to be released twice per year. The SAP HANA product stays in mainstream maintenance as long as application releases that are built on top SAP HANA are in mainstream maintenance, extended maintenance, or priority-one support (e.g. Release note 74.xx 1935871). SPS 08 …. 73 74 SPS 09 80 81 82 … 90 91 92 … Updates are cumulative and strictly downward compatible © 2015 SAP SE. All rights reserved. 66 SAP HANA Release Strategy Understand the Differences in SAP HANA Revisions SAP HANA Support Package (SP) Revisions Represents the individual software corrections and updates available for SAP HANA. Revisions are cumulative and strictly downward compatible. SAP HANA Maintenance Revisions Contain only major bug fixes found in key SAP HANA scenarios. The provisioning of new maintenance revisions ends with availability of SAP HANA production system verified revision, approx. 3 months after release of a successor SPS. From this date, customers must adopt the regular SP revisions to receive further fixes (see SAP Note 1948334). SPS 08 SAP HANA Revisions 73 74 80 81 82 74.01 74.02 74.xx © 2015 SAP SE. All rights reserved. SPS 09 … 85 90 91 … 85.01 85.02 85.05 67 SAP HANA Release Strategy Adapt new SAP HANA releases at your own speed Customers may choose to maintain their SAP HANA system either with the latest SAP HANA SP revision or to stay temporarily on the SAP HANA Maintenance revisions stream. SAP HANA Datacenter Service Point Outlines certain revisions which have been running in production enterprise applications at SAP before they are released to customers. Those revisions are planned approx. 3 months after release of the latest SPS and are intended to allow better planning of maintenance windows for production environments running on SAP HANA. For all other customers, early birds and pilots who do not run SAP HANA in productive usage, SAP propose an immediate switch to a new SPS by implementing the regular SAP HANA SP Revisions as soon as they are released. This will allow to benefit from incremental, but non-disruptive innovation, provided by the latest SAP HANA features and fixes. Datacenter Service Point (DSP) Recommended path for production systems bug fixing, using SAP HANA Maintenance Revisions © 2015 SAP SE. All rights reserved. SPS 07 SAP HANA Revisions 68 69 70 71 72 73 74 69.01 69.02 69.xx SPS 08 80 81 82 83 … 74.01 74.02 74.xx 68 SAP HANA Release Strategy Expect stability and predictability for your SAP HANA maintenance The newly introduced SAP HANA Datacenter Service Point (DSP) provides SAP HANA customers with more guidance when and based on which SAP HANA Revision to plan their SAP HANA maintenance stack on. As most customers have to plan their maintenance window between their quarterly end closings, the DC service point had been defined to be between the SAP HANA SPS, at the end of March and at the end of September. As prove of SAP’s commitment in its own software quality, the Revisions referenced by such DC service point will also be running in production enterprise applications at SAP for at least one week before they are finally released, assuring customers even more stability and predictability. Recommended path for production systems planned maintenance, leveraging the SAP HANA Datacenter Service Points © 2015 SAP SE. All rights reserved. SPS 07 SAP HANA 70 71 72 73 74 Revision 68 69 DSP 07 SPS 08 80 81 82 83 … DSP 08 69 SAP HANA Revision and Maintenance Strategy Summary Release of New SPS SAP HANA Revisions: Datacenter Service Point 70 71 72 73 74 80 81 … 74.01 Zero Downtime SAP HANA Revision Update 74.02 74.xx Revision Type Schedule Comprises of Recommended to RTC Revision Every 6 months New features and fixes Early adapters and Non-production systems DSP Revision Every 6 months, after having run in SAP production system for 2+ weeks Incremental fixes, based on latest SPS feature set Production systems (targeting planned maintenance) Standard Revision On demand Incremental fixes, based on latest SPS feature set Systems on DSP Revision and Non-production systems Maintenance Revision On demand, provisioned between RTC and DSP only Incremental critical fixes only, based on predecessor SPS feature set Production systems, (targeting unplanned maintenance) © 2015 SAP SE. All rights reserved. 70 SAP HANA Platform SAP LVM Roadmap for SAP HANA integration SAP Landscape Virtualization Management Release 2.1 Details, SP3, Videos • • SAP BW to SAP HANA migration support** Automation for post-copy processing tasks for SAP applications on SAP HANA systems System clone, copy, rename and refresh (including synchronized clone) for single-node SAP HANA systems Provisioning SAP Systems* Landscape Management* Provisioning SAP Systems* • Basic Management: Outlook (planned beyond) • Basic Management: • • • Detect/start/stop/monitor single-node and multi-node (scale-out) SAP HANA systems Single/Mass operations on SAP HANA systems (with in-build support for system dependencies) Relocate Single hosts SAP HANA system Take-over procedure for SAP HANA system replication • Relocate multi-node (scale- • System clone, copy, • rename and refresh for multi-node (scale-out) SAP HANA systems Use SAP HANA replicated system as source for Provisioning PLANNED INNOVATIONS Landscape Management* out) SAP HANA and SAP HANA replication system • Enablement of further SAP HANA high availability procedures • Basic Management: Start/stop/monitor for Sybase IQ as NLS for SAP application** based on SAP HANA system • Relocate operation for Sybase IQ as NLS for SAP applications** based on SAP HANA system FUTURE DIRECTION * SAP HANA standalone systems and ABAP on SAP HANA tailored data center integration ** Through post-copy automation task list © 2015 SAP SE. All rights reserved. This is the current state of planning and may be changed by SAP at any time. 71 SAP HANA Platform Introducing SAP HANA Dynamic Tiering Priority and Data Volume Performance and Price HANA column store hot • • HANA warm • Non-Active Data Concept / Disk store of dynamic tiering • • • Cold (NLS) In DB In memory No restrictions, all features available In DB On disk No restrictions, all features available • Near-line Storage External to DB Near-line Storage Read access, no updates • Traditional Archive External to DB • Archive storage • No read access or updates • • Archive Archive © 2015 SAP SE. All rights reserved. This is the current state of planning and may be changed by SAP at any time. 72 SAP HANA Platform Ways to tackle data growth Archiving Memory Eviction Tiered Data Storage Application manages movement of data into some kind of archive (Suite ILM, BW NLS, …) Unload “not so important” data from main memory Offer data stores of different “priorities” Active/non-active data (BW) Page-loadable columns (Suite) SAP HANA (Main Memory) E.g. dynamic tiering Future: also Hadoop? SAP HANA Hot Store (Main Memory) SAP HANA Archive store But: do you really want to archive, or is it just a strategy for cost-evasion? © 2015 SAP SE. All rights reserved. Data file Process requires loading data into RAM Caching etc. lead to reduced but non-negligible memory footprint (Classical HANA) WarmStore (Disk) (New DT Store) Beginning of a journey Enterprise readiness Concept for data distribution, management, retrieval 73 SAP HANA Platform Introducing SAP HANA Dynamic Tiering Introducing SAP HANA Dynamic Tiering ● ● Ability to manage data according to its value - not all data needs to be accessed in true real time SAP HANA database now comprised of a memorybased hot store and a disk-based warm store HANA Database Service ● Two table definition types: HANA table (hot data) and HANA extended table (warm data) ● Push down query processing ● SQL and Calculation View support ● Use Cases: ● Table o Maintain current, more frequently accessed data in hot store, and historical data in warm store Table o Handle Big Data use cases where data volume prohibits an all in-memory solution Extended table o Also supported with BW 7.4 SP8 ● Table Initially not supported natively by SAP Business Suite Does not replace BW NLS and SoH ILM archiving (cold) © 2015 SAP SE. All rights reserved. Table Client Connect HANA Database Application Engine Fast data movement and optimized push down query processing (warm data) HANA Dynamic Tiering Engine All related data resides in extended store This is the current state of planning and may be changed by SAP at any time. 74 SAP HANA Platform Dynamic Tiering – Map data priorities to data management Hot data BW on HANA Data for dynamic tiering stores All in one database Warm data Hot Store o All tables with no specific location Warm Store SAP HANA Database Dynamic Tiering Hot store Primary image Durability © 2015 SAP SE. All rights reserved. Warm store Virtual table Cache / Processing SDA Primary Image o PSA tables o wo-DSO tables o Available starting HANA SPS 09 and BW 7.40 SP8 NLS read This is the current state of planning and may be changed by SAP at any time. 75 Extended Tables in BW on HANA Use Case: Staging and Corporate Memory Object Classification in BW Data Sources and write-optimized DSOs can have the property “Extended Table” Generated Tables are of type “Extended” All BW standard operations supported – no changes Only minor temporary RAM required in HANA InfoCubes and Regular or Advanced DSOs Generate standard column table BW System Staging Area Corporate Memory Data Mart Data Source Write-optimized DSO InfoCube Database Catalog PSA Table Active Table Table Schema Table Schema Data Fact Table Table Schema Data Warm store Data Hot Store SAP HANA database © 2015 SAP SE. All rights reserved. 76 SAP HANA Platform Extended Tables HANA extended table schema is part of HANA database catalog HANA extended table data resides in warm store HANA extended table is a first class database object with full ACID compliance Database Catalog Table Definition Data Hot Store Classical HANA column table Data Warm Store Extended table Table Definition HANA Database © 2015 SAP SE. All rights reserved. This is the current state of planning and may be changed by SAP at any time. 77 SAP HANA Platform Possible HW layout for Dynamic Tiering with SAP BW Failover Group extended_storage Failover Group default Failover Node SAP HANA BW (Extended Storage) Node 1 Node 2 Node 3 data& log data& log data& log Data for persistence & recovery FailOver Node Warm data (Cashed) Hot data (Loaded) © 2015 SAP SE. All rights reserved. Dynamic Tiering Node 4 Node 5 Node 6 data_es & log_es Warm Data 79 SAP HANA Platform Dynamic Tiering: Roadmap PLANNED SAP HANA dynamic tiering available to be used by any HANA application (if the application supports the feature) FUTURE HANA ES host scale-out and auto-failover (HA) Common installer Disaster Recovery (SAP HANA system replication) Unified administration and monitoring using HANA Cockpit Further integration with respect to backup/recovery Extended Storage (ES) engine is part of HANA topology Hybrid extended tables with rule based automatic data movement / aging Single authentication model Optimization of communication between hot and warm store Single licensing model Combined error log / trace handling Integrated File-based backup/recovery, including point-in time recovery Further unification of DDL and DML for HANA extended tables Further optimizer enhancements Further extension of unique HANA capabilities to warm store © 2015 SAP SE. All rights reserved. 80 SAP HANA Platform Future Direction: Hybrid extended tables Single HANA table that spans hot and warm stores Hot partitions in HANA memory; remaining partitions in warm store Automatic, rules-based, asynchronous data movement between hot and warm stores regulatory audit Hybrid Extended Table © 2015 SAP SE. All rights reserved. Current Historical Hot data in HANA tier aging Warm data In warm tier 81 SAP HANA Platform News with SAP HANA SPS09 and Beyond removing services Tailored Data Center Integration Intel Xeon E5 processor support SAP HANA support for IBM Power CPUs with “Linux on Power” Data Temperature SAP HANA SPS10 SAP HANA support for IBM Power CPUs with “Linux on Power” o Ramp-up for BWoH started early in 2015 Introducing SAP HANA Dynamic Tiering SAP LVM deeper integration o Cloning, Renewing, Copying, Clustermanager Multi Tenancy SAP HANA Multitenant Database Containers Planned beyond Functional extensions for o SAP HANA Tailored Data Center Integration Topology changes Removing surplus services (deleting surplus hosts already implemented) o SAP HANA Dynamic Tiering o SAP HANA Multitenant Database Containers o SAP LVM integration UI support in SAP HANA Studio for This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 83 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 85 SAP HANA Persistence: In-Memory Data Is Regularly Saved to Disk HANA Data: SQL data and undo log information Additional HANA information, such as modeling data Kept in-memory to ensure maximum performance Write process is asynchronously Log: Information about data changes (redo log) Directly saved to persistent storage when transaction is committed (synchronous) Cyclical overwrite (only after backup) Savepoint: Changed data and undo log is written from memory to persistent storage Automatic At least every 5 minutes (customizable) © 2015 SAP SE. All rights reserved. Memory Data Information about data changes Regular automatic savepoints Log Volume Data Volumes Persistent Storage 86 SAP HANA Database Landscape Distributed HANA database even on a single host with shared nothing concept In-Memory LOG DISK DATA DISK LOG DISK LOG DISK DATA DISK DATA DISK Persistence Layer © 2015 SAP SE. All rights reserved. 87 SAP HANA Persistence Regular Saving of In-Memory Data to Disk, Restart In-memory computing is secure The SAP in-memory database holds the bulk of its data in memory for maximum performance, but still uses persistent storage to provide a fallback in case of failure. The log is capturing all changes by database transactions (redo logs) Data and undo log information (part of data) are automatically saved to disk at regular savepoints The log is also saved to disk continuously and synchronously after each COMMIT of a database transaction (waiting for end of disk write operation) After a power failure, the database can be restarted like a disk-based database: System is normally restarted („lazy“ reloading of tables to keep the restart time short) System returns to its last consistent state (by replaying the redo log since the last savepoint) Time 1 Savepoint: Data & undo log is written to disk (data area) © 2015 SAP SE. All rights reserved. 2 Continously and after each COMMIT, redo log is written to disk (log area) 3 Power failure 88 SAP HANA Smart Data Access Data virtualization for on-premise and hybrid cloud environments Benefits Transactions + Analytics Remote real-time query processing Smart continuously self-tuning system Secure access to heterogeneous data sources SAP HANA Heterogeneous data sources MS SQL Oracle ASE/IQ Teradata Hadoop, Spark © 2015 SAP SE. All rights reserved. SAP HANA to Hadoop (Hive), Spark Teradata SAP Sybase ASE SAP Sybase IQ, ESP Oracle 12c MS SQL-Server SAP MaxDB MaxDB SAP HANA 91 SAP HANA Smart data access Differentiation The intelligence of knowing when to delegate query processing or pull the data into SAP HANA for query processing, based on the performance windows Data Federation Data Virtualization Smart Data Access Dynamic query recommendation To return query results extremely fast. Capabilities supporting fast processing leveraging in-memory acceleration Cost-based query optimization Data pre-caching In-flight transformation Converged data processing © 2015 SAP SE. All rights reserved. 92 SAP HANA Smart Data Access Data modeling in SAP HANA studio Transactions + Analytics Applications SAP HANA Studio Enables users to develop applications SAP HANA SAP HANA Tables on SAP HANA, Virtual Tables Allows remote data to be accessed seamlessly Adapter Framework Built-In Adapters Third Party Adapters Heterogeneous data sources accessed in SQL statements through a virtual table Data Sources © 2015 SAP SE. All rights reserved. 93 SAP HANA Persistence News with SAP HANA SPS10 and Beyond Persistence development Next steps (current planning) Deeply involved in several projects, like new technology integration into SAP HANA Operational security: Existence check and alert for missing Data and Log Volumes Startup time optimization by parallelizing activities necessary during startup Planned beyond More flexible Data Volume management with possibility for multiple smaller data volume files This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 95 SAP HANA Persistence – SPS 10 News Existence check for vital files Check for existence of Data and Log Volume structures With every SAP HANA Savepoint execution now also a check of vital database files is executed Checked objects: / (root) Linux /usr/sap 10GB 50GB Data Volumes directory Data Volumes files Log Volume directory Log Volume segment files The check is looking for the file/object existence to offer alerts early enough to start activities to ease the impact of the accidental file deletion mnt00001 Recommended activities: As long as the database is still functional admins can still create backups and use them for recovery after restart With the restart of the SAP HANA finally the locks on the file bodies are stopped and the file bodies (block chains on disk) are not existing anymore. Before that only the file meta data was deleted in directory structures. /hana data log shared H36 H36 H36 mnt00002 mnt00001 mnt00002 n x RAM hdb00001 hdb00002 hdb00003 hdb00004 hdb00005 hdb00001 hdb00002 hdb00003 hdb00004 hdb00005 3 x RAM 3 x RAM 1 x RAM 1 x RAM Host 1 Host 2 Host 1 Host 2 With this alert we want to inform HANA admins early enough to take action! © 2015 SAP SE. All rights reserved. 96 SAP HANA Persistence – SPS 10 News Improved Start-up Performance Improved Start-up performance Optimization in RowStore (RS) handling during start-ups Secondary index creation decoupled With HANA SPS10 the rebuild of the secondary indexes during activation of the RowStore now can be done in a decoupled way No necessity to wait for finishing the creation process Is done asynchronously in background Short-time missing secondary indexes can be coped with primary key accesses to involved tables until they are created © 2015 SAP SE. All rights reserved. Secondary HANA RS CS 97 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 98 SAP HANA Backup and Recovery Memory Disk Backup SAP HANA database Memory Savepoint Data Area (disk) Data Backups © 2015 SAP SE. All rights reserved. COMMIT Data backups Contain the current payload of the data volumes Any pages that are changed during the data backup written to different locations in the data volumes (shadow page concept) Manual (SAP HANA studio, SQL commands), or scheduled (DBA Cockpit) Log backups Log Area (disk) Contain the content of closed log segments Automatic (asynchronous) whenever a log segment is full or the timeout for log backup has elapsed Log Backups 99 SAP HANA Backup and Recovery Terminology Data Data Area Data area = all data volumes 1 data volume per service with persisted data (per node) Redo log Data Volume Log area = all log volumes 1 log volume per service with persisted data (per node) Log volume contains log segments Log Area Log Volume Log Volume © 2015 SAP SE. All rights reserved. Log Segment o Number of pre-formatted log segments is configurable o Log segments are closed when they are full, or the log backup timeout has elapsed o After a log segment has been successfully backed up, it is released for overwriting 100 Backup and Recovery Advantages for Backups with HANA Kernel involvement Structural knowledge of data in database kernel Mini-verify of every page with relevant information during simple data and log backup Header and Trailer verification of checksums ensures valid data in pages Hardware problems get soon recognized and can be treated early enough w/o further implications to general data consistency OS-related or external tools don’t offer this structural knowledge into HANA data types Performance Only occupied space is backed up Throughput of up to 0.5 or 1 TB per hour and per host (scale-out case) reported in an optimal situation (There are a lot of ways like bad network throughput, slow NFS storage perf., no hardware separation etc. to ruin such a good B&R performance) Check Backup General possibility to check also backups with data knowledge in kernel available (please check SAP note 1869119 and 1873247 for further information) © 2015 SAP SE. All rights reserved. 101 SAP HANA Backup/Recovery Data backup: Only payload is backed up Shared Backup Directory (staging area) SAP HANA Server Backup Savepoint DATA_BACKUP_0000 Data Name Server DATA_BACKUP_0001 Backup Savepoint Data DATA_BACKUP_0002 Data Index Server Backup Savepoint DATA_BACKUP_0003 Data Statistics Server © 2015 SAP SE. All rights reserved. 102 SAP HANA Backup/Recovery Data backup: Single-node and scale-out systems SAP HANA automatically handles the synchronization of backups for all nodes no special user interaction required All services that persist data are backed up o e.g. index servers, master name server) Global data backup savepoint for all these services o Synchronized across all nodes and services o Transactions are paused very briefly o Savepoint is kept until the backup is finished for all services. If a page is changed during the backup, it’s written to a different location (shadow page concept) Data marked in the savepoint is read from data volumes and written to backup files o One backup file per service o Parallelization Master Name Server Name Server Name Server Index Server Index Server Index Server Savepoint Savepoint Savepoint Savepoint Parallelization Synchronized backup savepoint Backup File Shared Backup Directory © 2015 SAP SE. All rights reserved. 103 SAP HANA Backup and Recovery Destinations for backups (I) Backups to the file system For both data and log backups E.g. to an NFS share For information on file systems: SAP Note 1820529 Data backups triggered/scheduled using SAP HANA studio, SQL commands, or DBA Cockpit, log backups written automatically (unless disabled) © 2015 SAP SE. All rights reserved. SAP HANA studio hdbsql Create backup SAP HANA Database Backup Storage, e.g. NFS 104 SAP HANA Backup and Recovery Destinations for backups (II) Backups to 3rd party backup server For both data and log backups “Backint for SAP HANA” API can be implemented by a 3rd party backup agent (certification required) Provides functions for backup, recovery, query, delete 3rd party backup agent runs on the SAP HANA server, communicates with 3rd party backup server Backups are transferred via pipe Direct integration with SAP HANA: o Data backups to Backint can be triggered/scheduled using SAP HANA studio, SQL commands, or DBA Cockpit o Log backups are automatically written to Backint (if configured) © 2015 SAP SE. All rights reserved. SAP HANA studio hdbsql Create backup SAP HANA Database 3rd Party Backup Agent 3rd Party Backup Server 105 SAP HANA Backup and Recovery Backint Certification In December 2012 SAP released the certification process for “Backint for SAP HANA”. Certification is an installation prerequisite for backup tools using the “Backint for SAP HANA” interface. SAP Note 1730932 (“Using backup tools with Backint”) Release announcement Certified tools (as of 2014-June) Vendor Certified Backup Tool Support Process Symantec NetBackup 7.5 SAP Note 1913568 IBM Tivoli Storage Manager for Enterprise 6.4 SAP Note 1913500 Commvault Simpana 10.0 SAP Note 1957450 HP Data Protector 8.0 SAP Note 1970558 EMC Data Domain SAP Note 1970559 EMC Networker 8.2 SAP Note 1999166 SEP Sesam 4.4 SAP Note 2024234 Dell Quest Netvault Backup - Planned - Online listing of certified tools: http://www.sap.com/partners/directories/SearchSolution.epx ”SAP-Defined Integration Scenarios” = "HANA-BRINT” Information for tool vendors: http://scn.sap.com/docs/DOC-34483 © 2015 SAP SE. All rights reserved. 106 SAP HANA Backup Backup in SAP HANA Studio © 2015 SAP SE. All rights reserved. 107 SAP HANA Backup and Recovery Destinations for backups (III) Storage snapshots as backups SAP HANA also supports the creation of storage snapshots, which can later be used for recovery 1. Using SAP HANA studio, prepare the database for the storage snapshot. Technically, this creates an internal data snapshot 2. Using the storage tool, create a storage snapshot of the SAP HANA data area 3. In SAP HANA studio, confirm the storage snapshot as successful. An entry including the external backup ID is written to the backup catalog © 2015 SAP SE. All rights reserved. SAP HANA studio Storage Tool hdbsql Prepare database Confirm storage snapshot SAP HANA Database Data snapshot Data Area (Disk) Create storage snapshot External Storage 108 SAP HANA Backup and Recovery Creating a storage snapshot Creating a snapshot 1. In the Systems view in SAP HANA studio, right-click on the system and choose Storage Snapshot... Then choose the Prepare option. Alternatively, you can use the SQL command: BACKUP DATA CREATE SNAPSHOT COMMENT ‘snapshot_test’ 2. Using the storage tool, create a storage snapshot of the SAP HANA data area 3. In SAP HANA studio, confirm the successful storage snapshot and enter the external snapshot ID. Alternatively, you can use the SQL command: BACKUP DATA CLOSE SNAPSHOT BACKUP_ID 3456789 SUCCESSFUL 'storage_id_12345‘ Storage snapshots are listed in the backup catalog. You can either display the backup catalog in SAP HANA studio, or query it using SQL (system view M_BACKUP_CATALOG). © 2015 SAP SE. All rights reserved. 109 SAP HANA Backup and Recovery Options for backup: Comparison Advantages File system Backint Storage snapshot Consistency checks on block level Consistency checks on block level Fast Ease of use – no explicit backup files management, integrated into Studio Negligible network load First storage partners offer integration in their tools Data center integration Additional features, e.g. encryption or de-duplication Backups immediately available for recovery Disadvantages Additional storage required Network load File system fill level needs to be monitored 3rd party backup tool necessary No consistency checks on block level Additional time needed to make backups available for recovery Network load In case of recoveries, backup files must be returned to staging area Size Payload only Payload only ~ Size data area, but usually compressed/de-duplicated by storage Duration IO-bound (reading from data volume, writing to target) IO-bound (reading from data volume) Negligible (logical pointers are replicated) Network-bound (writing to file system) Network-bound (writing to backup server) © 2015 SAP SE. All rights reserved. 110 Backup and Recovery Backups during normal operation of the database: Summary Time 1 Data backups (external backup destination) 2 3 Log backups Most recent (external backup log entries destination) from log area 4 Crash To learn more about “Recovery with missing log backups” see SAP Note 1816483 or about “How to recreate the backup catalog” see SAP Note 1812057. © 2015 SAP SE. All rights reserved. 111 SAP HANA Backup and Recovery Backup catalog The backup catalog provides detailed information on data backups, log backups and storage snapshots, for example start/end time, duration, size, and throughput The backup catalog is stored within the SAP HANA database, and also backed up as part of the log backup (even in log mode OVERWRITE). This allows for offline access to the backup catalog during recovery. © 2015 SAP SE. All rights reserved. 112 SAP HANA Backup and Recovery Starting a recovery In the Systems view in SAP HANA studio, choose Recover... from the context menu of the database and enter the credentials of the SAP HANA operating system user <SID>adm Caution: For a recovery, the SAP HANA database will be shut down © 2015 SAP SE. All rights reserved. 113 SAP HANA Recovery Recovery in SAP HANA Studio You can use either a data backup (from the file system or Backint), or a storage snapshot as the basis for the recovery © 2015 SAP SE. All rights reserved. 114 SAP HANA Backup and Recovery Recovery using a specified data backup or storage snapshot You can use either a data backup (from the file system or Backint), or a storage snapshot as the basis for the recovery © 2015 SAP SE. All rights reserved. 115 SAP HANA Backup and Recovery Recovery phases After the initial collection of system information for the recovery, the recovery wizard shows the following phases: Phase 1: Data recovery – using data backup or snapshot Phase 2: Log recovery – using log backups and/or log that is still available in the log area Phase 3: Restart © 2015 SAP SE. All rights reserved. 116 SAP HANA Backup and Recovery Backup information in SAP HANA Studio You open the backup overview tab by double-clicking Backup in the Systems view in SAP HANA studio Progress information on currently running data backup, with information on the services included in the backup Last successful data backup o Start/end time, duration, size, and throughput o To display more detailed information on this data backup, click More Information Information on open snapshot Buttons for Canceling running data backup Starting backup Displaying backup.log file © 2015 SAP SE. All rights reserved. 117 SAP HANA Backup and Recovery Recovery steps when using a storage snapshot 1. Using the storage tool, transfer the storage snapshot to the data area of the SAP HANA database 2. Using SAP HANA studio, recover the database using the storage snapshot as basis (available in the recovery wizard) Note: All recovery options are available, including point-in-time recovery using log backups/log from the log area SAP HANA Studio Storage Tool hdbsql Recover database SAP HANA Database Transfer storage Note: All recovery options are available, including point-in-time recovery using log backups/log from the log area © 2015 SAP SE. All rights reserved. snapshot to data area Data snapshot Data Area (Disk) External Storage 118 Backup and Recovery Database Copies SAP HANA database copy from PROD to QA or DEV allows to change the topology in case of a Scale-out setup on PROD side: Backups which are produced on scale-out landscapes with n hosts can be recovered to one QA, DEV or sandbox systems. Purpose is to offer a possibility for a light system copy without the full performance scope like PROD Ability to work on that copy limited by performance and restricted by tables/partition sizes PROD Node n IndexNode Server 2 IndexNode Server 1 Node 1 Index Server n Index Server 2 Index Server N1 NM QA, DEV or Sandbox Index Server 1 Database inside changes © 2015 SAP SE. All rights reserved. 120 SAP HANA Backup and Recovery Database Copy Details You can carry out database copies using SAP HANA’s standard backup/recovery functions A typical use case would be to create a copy of your production system for tests on a smaller QA system. Note: If the target system has less resources, e.g. less CPU and RAM, performance cannot be expected to be the same as in the source system. Both file system backups, backups via a 3rd party backup tool, and storage snapshots can be used for database copies. Options for database copy Using data backup or storage snapshot + log backups of the source database This allows you to restore the database to a point in time after the data backup or storage snapshot Using only data backup or storage snapshot of the source database This restores the content exactly as of the point in time of the data backup or storage snapshot Copying from a larger (m nodes) to a smaller system with fewer hosts (n nodes) is supported for database copies using data backups (but not when using storage snapshots). You will need to configure (m-n) additional index servers in the target database. © 2015 SAP SE. All rights reserved. 121 SAP HANA Backup and Recovery Database Copy with SAP HANA native backup files Using data and log backups – source and target databases may have different number of hosts Node n Node 2 Index Server Node 1 Check detailed scenarios & descriptions in SAP HANA Admin Guide (Chapter 5.2.6 – SPS10) Index Server Node 2 Node 1 Index Server Index Server 1 Index Server 1 Index Server 2 Source database with n nodes (e.g. PROD) © 2015 SAP SE. All rights reserved. Data backup + log backups (optional) Target database with 2 nodes (e.g. QA) 122 SAP HANA Backup and Recovery Database Copy in combination with Storage Snapshots Using snapshot and log backups – source and target databases must have same number of hosts Node n Node 2 Index Server Node 1 Check detailed scenarios & descriptions in SAP HANA Admin Guide (Chapter 5.2.6 – SPS10) Node 1 Index Server 1 Index Server 1 © 2015 SAP SE. All rights reserved. Node 2 Index Server Index Server Index Server Source database with n nodes (e.g. PROD) Node n Snapshot + log backups (optional) Target database with n nodes (e.g. DEV) 123 Backup and Recovery Internal Snapshots in SAP HANA SAP note: 1703435 Limitation: One internal Snapshot only right now Conflicts with Backup Snapshot which is needed during backup execution time. If an internal snapshot already exists when backup is started, the backup will not be executed and an error presented. Roadmap: multiple named internal Snapshots are planned © 2015 SAP SE. All rights reserved. 124 SAP HANA Backup and Recovery More information Documentation SAP HANA Administration Guide, SAP HANA Technical Operations Manual Overview presentation Backup/recovery overview presentation Best practices 2091951: Best practice: SAP HANA Backup and Restore Important SAP Notes 1642148: FAQ: SAP HANA database backup and recovery 1730932: Using backup tools with Backint 1869119: Check backup integrity For further notes on backup/recovery, see HANDB-BAC Backint for SAP HANA certification Certification announcement and description © 2015 SAP SE. All rights reserved. 126 SAP HANA Backup & Recovery News with SAP HANA SPS10 and Beyond 3rd party backup tools: tenant copy via Backint (for MDC systems) Backint 2.0 API and certification Backup & Recovery Delta backups (incremental/differential) Backup header contains software version SAP HANA Cockpit: web-based backup operations o extended scope e.g. Redhat support Additional backup options – e.g. o Support for backup operations on secondary system in system replication scenarios o Offline log backup o Create data backups o Display backup catalog o Monitor Backups SAP HANA setups with Dynamic Tiering now support Backint API Next Steps (current planning) Multiple parallel backup streams for huge index server data backups Planned beyond Additional Recovery Options o Restart-able log recoveries after a successful data recovery as the 1st step of the process. Additional options for backup lifecycle management in discussion e.g. o Local backup staging integrated with 3rd party backup tools support (local backup buffer) o Integrity check for the backup catalog o Partial recovery (service oriented) o Option for manual log backupd o Configuration file backup o Backup compression o Backup throttling This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 127 SAP HANA Backup and Recovery – SPS10 News Delta backups (incremental and differential) Full data backup – all data F III D A full data backups contains all current data Incremental backup – changed data since the last data backup (full or delta) Delta backups contain data that was changed since an earlier data backup Two types of delta backups are available: Differential backup – changed data since the last full backup You can create delta backups using Studio or SQL © 2015 SAP SE. All rights reserved. Incremental and differential 128 SAP HANA Backup and Recovery – SPS10 News Delta backups (incremental and differential) – when to use what Full data backup F Comparison of incremental and differential backups Incremental backups... III D Incremental backup Differential backup © 2015 SAP SE. All rights reserved. ...are usually small faster backup ...are restored one after the other during a recovery longer recovery times Differential backups... ...increase the amount of data saved with each backup longer backup times ...reduce the number of data backups during recovery faster recovery You can also mix incremental and differential backups 129 SAP HANA Backup and Recovery – SPS10 News Delta backups – During normal operation Now F I I D I I Time 5 Most recent entries from log area 1 Last full backup 2 Incremental backup 3 Differential backup 4 Log backup © 2015 SAP SE. All rights reserved. 130 SAP HANA Backup and Recovery – SPS10 News Delta backups – Recovery Options C F B I I D I A I Time (A) To the most recent state Full data backup or snapshot + last differential backup (Note: not supported if a snapshot is used as basis) + subsequent incremental backups (Note: not supported if a snapshot is used as basis) + subsequent log backups + redo log entries that are still available in the log area (if it was not destroyed by the failure) (B) To a point in time in the past Same as above; redo log entries from the log area might not be required (C) To a specified full data backup or snapshot Full data backup or snapshot, but no log replay (“clear log”) © 2015 SAP SE. All rights reserved. 131 SAP HANA Backup and Recovery – SPS10 News Use of delta backups during recovery Recovery includes delta backups automatically SAP HANA automatically determines the best recovery strategy based on all available backups, including delta backups. If you do not want SAP HANA to use delta backups for the recovery, de-select Use Delta Backups when specifying your recovery settings © 2015 SAP SE. All rights reserved. 132 SAP HANA Backup and Recovery – SPS10 News Backup integration into SAP HANA Cockpit (I) Backup operations are now available in SAP HANA Cockpit There is a new tile in SAP HANA Cockpit that shows the status of the current data backup. Clicking on the tile takes you to the backup catalog. © 2015 SAP SE. All rights reserved. 133 SAP HANA Backup and Recovery – SPS10 News Dynamic tiering supports Backint API for connecting 3rd party backup tools The Backint API for connecting 3rd party backup tools has been implemented for dynamic tiering Add-on certification process planned Backup tools will need to be certified for HANA+DT systems Not included in regular „Backint for HANA“ certification HANA Dynamic tiering Index server Name server XS engine DT table spaces One data backup © 2015 SAP SE. All rights reserved. 134 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 135 High Availability – Disaster Recovery Business Continuity High Availability Disaster recovery per Data Center between Data Centers SAP HANA Host Auto-Failover (Scale-Out with Standby) SAP HANA Storage Replication SAP HANA System Replication SAP HANA System Replication ● Performance Optimized ● Performance Optimized ● Cost Optimized ● Cost Optimized © 2015 SAP SE. All rights reserved. 136 SAP HANA High Availability Scale to a setups, bigger than one host Offer an easy HA option by putting one or more hosts as spare/standby Host Auto-Failover is offered by the Name Service The resulting cluster is managed by this name service inside of HANA. He regularly checks on the cluster members to be still active. In case of problems he initiates a fully automated take-over to the standby hardware. Together with the switched of mounts/disks also the identity of the failing cluster member is moved to the standby hardware. Name server Server 1 Name server Server 2 Name server Server 3 Name server Server 4 Name server Server 5 Name server Server 6 Name server Shared Storage SAN Storage Scale-out clusters address two problems Storage Connector API Scale-Out with Host Auto-Failover Standby Server Starting with shared storage, HANA Scale-Out today can use SAN storage with FibreChannel adapters Name server © 2015 SAP SE. All rights reserved. Server 1 Standby Server SAN Name server 137 Storage Minimalistic setup for only HA: Storage Connector API Storage Connector API ensures the possibility of remounting necessary file systems to standby hosts More details with: SAP Note 1900823 - Storage Connector API Please check its attachments for white papers etc. SAP HANA storage Storage for persistent data Shared-nothing architecture with Cluster File Systems Fibre Channel Storage using SAN Shared Storage Infrastructure using Cluster File System with local disks Non-shared SAN storage attached via Fibre Channel for HANA data and log volumes and shared NFS/NAS storage for HANA binaries Network attached storage using NFS Network Attached Storage attached via NFS © 2015 SAP SE. All rights reserved. More details available in SAP HANA Storage Requirements whitepaper and Fibre Channel Storage Connector Admin Guide: SAP Note 1900823 138 SAP HANA High Availability Host Auto-Failover Failover decision • Heartbeat • TCP communication based heartbeats • Ping Nameserver and Daemon (internal communication protocol) • Storage based heartbeats (nameserver.lck) • In shared storage for HANA binaries (e.g. /usr/sap/MB1/SYS/global/hdb) Fencing to prevent data corruption • NFS4 or GPFS • File locking • NFS3 • Disable built-in file locking (no automatic lock release) • HANA Storage Connector using STONITH (shoot the other node in the head) • Block storage via fibre channel (SAN) • HANA Storage Connector using SCSI-3 persistent reservations © 2015 SAP SE. All rights reserved. Split Brain • Master Nameserver is the only entity to make a failover decision • Network errors between master candidates and master nameserver can cause split brain situations • As long as the randomly written string in file nameserver.lck is changing, master is still alive Worker (Mastercandidate 2) Master (Master candidate 1) Standby Rewrites single random strings repeatedly (Mastercandidate 3) .lck Located in shared storage for HANA binaries Checks for changes Tries to become new master Check Nameserver locks If .lck is still changing original Master still alive 139 SAP HANA Architecture Single host configuration Multi-node cluster configuration SAP HANA Appliance SAP HANA Database Node 2 Node n Maintains landscape information Name Server Name Server Name Server Holds data and executes all operations Index Server Index Server Collects performance data about HANA Statistics Server* Text analysis pre-processor XS engine Repository for HANA Studio updates Enables remote start/stop Manages SW updates for HANA … Index Server Preprocessor Preprocessor Preprocessor XS engine XS engine XS engine SAP Host Agent SAP Host Agent SAP HANA Studio Repository SAP Host Agent Software Update Manager Shared storage for fail-over and recovery © 2015 SAP SE. All rights reserved. 141 SAP HANA Database Landscape Distributed HANA database even on a single host with shared nothing concept In-Memory Standby without own persistence LOG DISK DATA DISK DATA DISK LOG DISK LOG DISK LOG DISK DATA DISK DATA DISK LOG DISK DATA DISK Persistence Layer © 2015 SAP SE. All rights reserved. *Standby Host: Name Server (active) Index Server (standby) 142 HANA High Availability Host Auto-Failover (standby) Different implementation of High Availability by HW partners Using storage solution inside © 2015 SAP SE. All rights reserved. Using internal disk Standby Name Server Name Server Index Server Index Server Index Server Data Disks Data Disks Data Disks Log Disks Log Disks Log Disks Name Server GPFS GPFS 143 SAP HANA High Availability Minimal Setup for Host Auto-Failover Minimal setup for a Host Auto-Failover (Scale-Out): active standby Master Name Server Name Server Index Server Index Server 2 Servers including one Standby External storage or similar technology necessary which ensures the data provisioning to second node via external data location This setup aims for High Availability not performance scaling or size. Note: Some use cases (e.g. SAP BW powered by HANA) might have different requirements or recommendations for minimal setups (e.g. BW has a defined setup for SAP HANA Scale-Out – SAP note 1736976 attached PDF). © 2015 SAP SE. All rights reserved. Data Disks Log Disks 144 SAP HANA High Availability Client Management with Scale-Out SQL clients: SAP Appl. Server hdbsql User Store hana1;hana2;hana3 round robin hana1 hana2 hana3 Clients: During installation the clients get initial information about how to contact to HANA database – often only one host is offered To prevent single point of failure, more host should be offered in case of Scale-Out The list is only necessary to establish a first connect to HANA cluster – afterwards the client gets the full topology from the database Name Server anyway The complete list of hostnames including the standby host should be stored HANA Scale-Out hana1 hana2 hana3 Name Server Name Server Name Server Index server Index server Index server standby Data Disks Log Disks © 2015 SAP SE. All rights reserved. User store: Contains the list of host names like “hana1;hana2;hana3” etc. next to user and encrypted password information All tools based on this database interface named sqldbc (SAP Appl. Server, hdbsql, ODBC, python, etc.) can use this user store. Algorithm: Round robin process is used to find this first contact point 145 SAP HANA Disaster Recovery HA/DR Provider Framework – Functionality HA/DR Provider Framework now offers an active “communication” channel Possibility to inform external entities about activities inside of SAP HANA Scale-Out E.g. during move of master service to a different host inside Scale-Out a virtual IP/hostname can be moved accordingly to represent the actual master host Documented in SAP HANA Admin Guide with detailed examples (Chapter 5.1.5 ff. Example HA/DR Provider Implementation) o vIPMover HA/DR Provider o mySTONITH HA/DR Provider A Python script provides hooks that can be called in response to events during Host Auto-Failover and System Replication takeover process (see table) Parameter section in global.ini: [ha_dr_provider_<classname>] o provider = : The class name o path = : Location of the script o execution_order = : The ordering of the HA/DR Provider if there is more than one; this is a number between 1 and 99 © 2015 SAP SE. All rights reserved. Name Trigger Caller Landscape Error behavior startup() beginning of nameserver’s startup phase starting nameserver each host individually nameserver aborts, startup is cancelled shutdown() just before the stopping nameserver exists nameserver each host individually error trace is written failover() [Host AutoFailover] as soon as the host that nameserver made takes over the decision about the role the new role each host that gets a new role nameserver aborts, failover is cancelled stonith() [Host AutoFailover] as soon as the master nameserver made nameserver the decision about the new role for each failed host nameserver aborts, failover is cancelled preTakeover() [System Replication] as soon as the hdbnsutil sr_takeover command is issued as soon as all services with a volume return from their assigncall (open SQL port) master nameserver called only takeover is once on the aborted master master nameserver called only error trace is once on the written master postTakeover() [System Replication] 147 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 149 HA & DR Concepts in general …system operational Sync or backup design & prepare operation resumed… RPO RTO detect recover time perf. ramp KPIs: • Recovery Point Objective (RPO) = worst-case data-loss • Recovery Time Objective (RTO) = time to recover from outage Solution Backup & Recovery SAP HANA Host Auto-Failover SAP HANA Storage Replication w/ QA, Dev. SAP HANA System Replication SAP HANA System Replication w/ QA, Dev. Used for HA & DR HA DR HA & DR HA & DR Cost RPO $ high $ 0 $$ 0* $$$ 0* $**/$$ 0* ** single host installations © 2015 SAP SE. All rights reserved. RTO high med med low med Perf. ramp med long long short long *synchronous solution 150 SAP HANA Disaster Recovery Different ideas of solutions 1. SAP HANA Storage Replication of SAP HANA disk areas controlled by storage technology • First synchronous implementation (available, SAP note 1755396) • Afterwards asynchronous implementation planned and in preparation with HW partners SAP HANA System Replication (initial solution): DATA and LOG content is continuously transferred to secondary site under control of SAP HANA database 2. • • • Fast switch-over times because secondary site can preload DATA First synchronous implementation available since SAP HANA SPS05 Asynchronous implementation offered with SAP HANA SPS06 SAP HANA System Replication (extended solution): DATA content is only initially transferred to secondary site, afterwards continuous LOG transfer and LOG replay on secondary site 3. • • • LOG is provided to secondary site on transactional basis (COMMIT) controlled by SAP HANA database (including initial DATA transfer) Fastest switch-over times, sec. site preloaded and rolled forward on COMMIT basis Synchronous and asynchronous implementation planned for next steps © 2015 SAP SE. All rights reserved. 151 SAP HANA Disaster Recovery: Storage Replication Cluster across Data Centers Clients Application Servers HA Solution Partner OS: DNS, hostnames Primary Secondary (inactive) Name Server Name Server Name Server Name Server Name Server Name Server Index server Index server Index server Index server Index server Index server HA Solution Partner Data Center 2 Data Center 1 Data Volumes Data Volumes Log Volume Log Volume © 2015 SAP SE. All rights reserved. Storage Mirroring OS: Mounts Data Volumes Data Volumes Log Volume Log Volume 152 SAP HANA Disaster Recovery: Storage Replication Cluster across Data Centers with QA & Dev. on 2nd site Clients Application Servers HA Solution Partner OS: DNS, hostnames Primary Secondary Prod. (inactive), QA&DEV (active) Name Server Name Server Name Server Name Server Name Server Name Server Index server Index server Index server Index server Index server Index server HA Solution Partner Data Center 2 Data Center 1 Data Volumes Data Volumes Log Volume Log Volume © 2015 SAP SE. All rights reserved. Storage Mirroring OS: Mounts Data Volumes Data Volumes Data Volumes Data Volumes Log Volume Log Volume Log Volume Log Volume 153 SAP HANA Disaster Recovery: System Replication Cluster across Data Centers with DB controlled transfer Clients Application Servers HA Solution Partner OS: DNS, hostnames, virt. IPs Primary Secondary (active) (active, data pre-loaded) Name Server Name Server Name Server Index server Index server Index server Transfer by HANA database kernel Name Server Name Server Name Server Index server Index server Index server HA Solution Partner Data Center 2 Data Center 1 OS: Mounts Data Volumes Data Volumes Data Volumes Data Volumes Log Volume Log Volume Log Volume Log Volume © 2015 SAP SE. All rights reserved. 154 SAP HANA Disaster Recovery: System Replication Cluster across Data Centers with QA & Dev on 2nd site Clients Application Servers HA Solution Partner OS: DNS, hostnames, virt. IPs Primary Secondary (active) Name Server Name Server Name Server Index server Index server Index server Transfer by HANA database kernel (active,) PRD Name Name shadow Server Server operation Name Server Index server Index server Index QA/DEV server running HA Solution Partner Data Center 2 Data Center 1 OS: Mounts Data Volumes Data Volumes Data Volumes Data Volumes Data Volumes Data Volumes Log Volumes Log Volumes Log Volumes Log Volumes Log Volume Log Volume © 2015 SAP SE. All rights reserved. PRD QA/DEV 155 SAP HANA High Availability: System Replication Minimal setup in one Data Center for fast takeovers Clients Application Servers Data Center 1 Primary Secondary (active) (active, data pre-loaded) Name Server Transfer by Index server © 2015 SAP SE. All rights reserved. Index server HANA database kernel Internal Disks Data Disks Name Server Log Disks Internal Disks Data Disks Log Disks HA Solution Partner HA Solution Partner OS: DNS, hostnames, virt. IPs 156 SAP HANA in Data Centers Video about SAP HANA System Replication Videos about SAP HANA by the SAP HANA Academy on YouTube: SAP HANA System Replication 1. 2. 3. 4. 5. 6. 7. Concepts Setup Replication Full-SYNC Configuration Parameter Disable Replication Take-over Near Zero Downtime upgrade More videos planned: 8. Fail-back 9. Multi-Tier 10. Online addhost Corresponding Blog © 2015 SAP SE. All rights reserved. 159 SAP HANA in Data Centers: Availability of solutions High Availability per Data Center Host Auto-Failover (Scale-Out with Standby) Available today from several HW partners System Replication Adaptations from most HW partners on the way High Availability across Data Centers – Disaster Recovery Storage Replication: Hardware validation successfully finished with partners, SAP note 1755396 Further HW partners planned to follow Mirroring solutions depend on HW partner technology Further detailed information about the solutions offered by HW partners. System Replication: since HANA SPS5, (End 2012) Partly HW partner related, especially external cluster management (network) Similar outside implementation like Storage Replication Step-by-Step Implementation Guide: https://scn.sap.com/docs/DOC-47702 © 2015 SAP SE. All rights reserved. 160 SAP HANA in Data Centers Cluster Manager with direct SAP HANA Support HP Service Guard Directly available from HP and HP drives the implementation process Link for further information: o Reference Guide: HP ServiceGuard Extensions, March 2014 o User Guide: Managing HP ServiceGuard Extensions for SAP for Linux, December 2013 SUSE Cluster Included with “SUSE SLES for SAP Applications” Blog: Fail-Safe Operation of SAP HANA®: SUSE Extends Its High-Availability Solution Setup Guide: SAP HANA System Replication on SLES for SAP Applications SAP Landscape Virtualization Manager (SAP LVM) Since Release 2.1 integrated, earlier releases need consulting package (Infrastructure Kit) Adaptation to local environment or resources (virtual IP addresses) necessary Other cluster managers In pipeline or can be adapted with individual consulting packages © 2015 SAP SE. All rights reserved. 161 Downtime optimized take-over Setups Client setup with virtual hostnames Datacenter 1 DNS virtual Hostname Datacenter 2 SAP NetWeaver SAP NetWeaver ASCS + ABAP Server default.pfl: SAPDBHOST=HANAscale1 Client: hdbuserstore Key: default ASCS + ABAP Server SUSE Cluster Manager default.pfl: SAPDBHOST=HANAscale1 DBSL DBSL Client: hdbuserstore Key: Hosts: HANAscale1; HANAscale2 default Hosts: HANAscale1; HANAscale2 Virtual Hostnames for HANA hosts: HANAscale1.mydomain.com; HANAscale2.mydomain.com; HANAscale3.mydomain.com SUSE Cluster Manager virtual hostname Primary Sync/Async mirrored Master Worker Standby redo log writing Secondary Master Worker Possible Standby Transport incremental data Data Log Data © 2015 SAP SE. All rights reserved. Log Data Log Data Log Data Log Data Log 163 Zero Downtime maintenance Featured by SAP NetWeaver ABAP stack As an evolution of “Near Zero Downtime Maintenance”, SPS7 now offers Zero Downtime Maintenance SAP NetWeaver ABAP Server Based on connectivity suspend feature of the SAP NetWeaver ABAP stack (SAP note 1913302) o DBSL of the database interface decouples transaction management between ABAP and HANA database o This keeps transaction on ABAP layer alive and allows to change components (software versions) on the layers below on secondary (shadow) HANA instance Further information also in Step-by-Step Implementation Guide for SAP HANA System Replication: https://scn.sap.com/docs/DOC-47702 Hardware mix (SAP note 1984882 - Using HANA System Replication for Hardware Exchange with minimum Downtime) DBSL Software Upgrade Order SAP HANA Version Sync/Async mirrored redo log writing Walldorf Rot Secondary Primary Data Volumes © 2015 SAP SE. All rights reserved. SAP HANA Version +1 Name Server Name Server Name Server Index server Index server Index server Log Volume Data Volumes Transport incremental data Log Volume Data Volumes Name Server Name Server Name Server Index server Index server Index server Log Volume Data Volumes Log Volume 164 Zero Downtime Maintenance for SAP HANA Revision Update HANA Planned Downtime DNS virtual Hostname DNS virtual Hostname DNS virtual Hostname 2 1 3 SAP NetWeaver ABAP Server SAP NetWeaver ABAP Server DBSL DBSL SAP HANA Version Walldorf Primary SAP HANA Version +1 SAP HANA Version Sync/Async mirrored redo log writing Log © 2015 SAP SE. All rights reserved. Connectivity Suspend Rot Walldorf Secondary Primary Rot Walldorf Secondary Primary Log Data Log virtual IP 3. Re-initiate SAP HANA Version +1 SAP SAP HANA HANA Version Version +1 Sync/Async mirrored redo log writing Transport incremental data Data Cluster Manager (e.g. SUSE Cluster) 1. Update 2. Reconfigure Takeover Transport incremental data Data DBSL Cluster Manager (e.g. SUSE Cluster) Software Upgrade Order virtual IP SAP NetWeaver ABAP Server SAP HANA Version +1 Sync/Async mirrored redo log writing Rot Secondary Transport incremental data Data Log Data Log Data Log 165 SAP HANA High Availability: Takeover Procedure In case of outage HANA Unplanned Downtime DNS virtual Hostname DNS virtual Hostname DNS virtual Hostname 2 1 3 SAP NetWeaver ABAP Server SAP NetWeaver ABAP Server DBSL Cluster Manager (e.g. SUSE Cluster) SAP NetWeaver ABAP Server DBSL Cluster Manager (e.g. SUSE Cluster) virtual IP Takeover virtual IP Walldorf Primary Sync/Async mirrored redo log writing Rot Walldorf Secondary Primary Transport incremental data Data Log © 2015 SAP SE. All rights reserved. Sync/Async mirrored redo log writing 1. Rebuild 2. Reconfigure Rot Walldorf Secondary Secondary Transport incremental data Data Log Data Log DBSL virtual IP 3. Re-initiate Sync/Async mirrored redo log writing Rot Primary Transport incremental data Data Log Data Log Data Log 166 SAP HANA High Availability: Takeover Procedure In case of outage – more detailed description HANA Unplanned Downtime 1. Initial situation SAP NetWeaver is connecting to SAP HANA via the DBSL (Database Shared Library) Usually a virtual hostname (virt. IP address) is used to access the database host and the database instance on that host. Usually the Domain Names Service (DNS) translates virtual hostnames into corresponding virt. IP addresses which can move between network adapter ports. SAP HANA System Replication is working and secondary is in a synchronous or asynchronous state with primary SAP HANA instance System Replication always tries to get in some kind of synchronous state (not guaranteed) although configured as ASYNC Of course with SYNC setup the primary waits for secondary to confirm operation of COMMITs © 2015 SAP SE. All rights reserved. 2. Incident happens, Take-over executed A cluster manager is checking on operational state of the setup and takes action if a failure is happening In case of this failure the cluster manager would isolate the box (drag virt. IPs away, even send a STONITH command) to prevent any further usage of primary host The orchestrator "cluster manager" also initiates the take-over, waits for the secondary to prompt the full operational state and finally moves the virtual IP address to the secondary host network port. With the move of the virtual IP address finally there is a living system again behind this interface and SAP NetWeaver sessions with workprocesses can be reconnected to the secondary database instance 3. Follow-up and re-initiate SAP HANA System Replication in reverse direction Every committed transaction and related changes are available again on the take-over system. Afterwards the recreation of the HA or DR has to happen with the rebuild of the hardware, maybe reinstall a blank installation or revive of SAP HANA and reconfigure it to be a secondary System Replication host. Initiate the resynchronization between new secondary and primary instance. The resync will probably take some time. Here SAP HANA automatically choses the optimal way to fulfill this task of execution (delta-transfer). Only after this resync a takeover back to the initial situation (failback) can be started. 167 Worldwide Data Center Setups Multi Tier System Replication – Cascading Systems Data Center Data Center Async Sync Tier 1 Tier 2 Production Local shadow with data preload © 2015 SAP SE. All rights reserved. Tier 3 Remote system/shadow with or without preload (mixed usage together with non-prod. operation) 168 SAP HANA System Replication Log Replication Modes: Improved Asynchronous – ASYNC Buffer Improvement for ASYNC With SPS 07 the ASYNC mode has been changed in a way that additionally to the buffering capabilities of the Operating System, an additional memory buffer inside HANA was added and operated with signaling semaphores. This introduces another decoupling with possibly limited resources (short term) on OS or HW side when it comes to ASYNC operation. The size of the intermediate buffer can be changed with the following parameter (here with default size): [system_replication]/logshipping_async_buffer size = 67108864 It is sufficient to set the parameter only for services with high log generation (e.g. in indexserver.ini) to save memory with other services. It is not necessary to set it globally. Using the following parameter, the behavior in case of buffer full can be change (with default setting): Transactions and their log transfer are waiting for free space in the buffer, if it’s full global.ini/[system_replication]/logshipping_async _wait_on_buffer_full = true Log replication modes Since Short name in system table SR_REGISTER Synchronous SPS 05 SYNC Synchronous in Memory SPS 05 SYNCMEM Asynchronous SPS 06 ASYNC “Full SYNC option” SPS 08 SYNC ASYNC operation: Primary Transaction Data © 2015 SAP SE. All rights reserved. Log Buffer SAP HANA offers the shown log replication modes Secondary Data Log 171 SAP HANA System Replication Synchronous Log Replication with Full SYNC option Log Replication “Synchronous with Full Sync Option” Available since Primary Secondary STOP SPS 08 Transaction Viewed in system table SR_REGISTER as SYNC (Full Sync is configured via configuration parameter) Data Log Data Log Description Log write is successful, when the log buffer has been written to the log volume of the primary and the secondary instance. In addition, when the secondary system is getting disconnected (e.g. because of network failures), the primary systems suspends transaction processing until the connection to the secondary system is re-established. No data loss occurs in this scenario. Implementation The replication mode Synchronous can be configured with the full sync option by setting the following configuration parameter on the primary site: • global.ini/[system_replication]/enable_full_sync = true. • hdbnsutil -sr_fullsync [--enable|--disable] Replication mode most interesting for financial institutes © 2015 SAP SE. All rights reserved. 172 Network design options for System Replication System Replication over separate network Optionally configurable with global.ini: [public_hostname_resulution] Client Applications 10.0.1.* Public Network 10.0.* Site 1 Host s1h1 10.0.2.* Site 2 Host s1h2 Host s1h3 Internal Network 192.168.* Separate Replication Network 10.5.* 10.5.1.* 10.5.2.* Host s2h1 Host s2h2 Host s2h3 Internal Network 192.168.* Host Configuration: Host Configuration: global.ini [communication] listeninterface=.internal global.ini [communication] listeninterface=.internal [internal_host _resolution] 192.168.1.1=s1h1 192.168.1.2=s1h2 192.168.1.3=s1h3 [internal_host _resolution] 192.168.1.1=s2h1 192.168.1.2=s2h2 192.168.1.3=s2h3 [system_replication_communication] listeninterface=.global (default value) [system_replication_communication] listeninterface=.global (default value) [system_replication_hostname_resolution] 10.5.2.1=s2h1 10.5.2.2=s2h2 10.5.2.3=s2h3 [system_replication_hostname_resolution] 10.5.1.1=s1h1 10.5.1.2=s1h2 10.5.1.3=s1h3 © 2015 SAP SE. All rights reserved. 173 SAP HANA in Data Centers Bandwidth considerations for System Replication SAP How-To Guide: Network requirements for System Replication: http://scn.sap.com/docs/DOC-56044 1. “Throughput”: Out of practical reason it must be possible to transport the size of the persistently stored data within one day from the primary to the secondary. 2. “Latency”: In case of SYNC operation: The redo log shipping wait time for 4 KB log buffers must be less than a millisecond or in a low single-digit millisecond range – depending on the application requirements (relevant for synchronous replication only). More info with SAP HANA Network Requirement Paper or SAP note 1969700 contains among others an SQL statement (in zip archive attached) to estimate the average (per day) bandwidth required for SAP HANA System Replication depending on the data and log amount per day © 2015 SAP SE. All rights reserved. Bandwidth Delta-Data continuous Log Peaks Average bandwidth need Baseline Time Example for a bandwidth calculation: Given: 4.3 TB of persistently stored data (sum of data backup file sizes). Throughput: 4.3 TB per day ~ 50 MByte/s ~0.5 GBit/s minimum connection required 174 SAP HANA System Replication SAP HANA Multitenant Database Containers SAP HANA Multitenant Database Containers SAP HANA System Replication can be used to replicate the whole system The replication process treats the complete collection of tenant containers as one HA&DR is the intention of this first support Replication of a single tenants to an individual location not possible Secondary Primary SystemDB SystemDB TenantDB1 TenantDB2 TenantDB n MDC DeltaData TenantDB1 Log TenantDB n TenantDB2 MDC Further information with SAP Note 2092793 © 2015 SAP SE. All rights reserved. 176 SAP HANA System Replication Improved Take-Over Performance Improved take-over performance Optimization in RowStore (RS) handling during take-overs RowStore stays in main memory on Secondary during take-over No necessity to re-loading RowStore from disk to memory again ColumnarStore (CS) is preloaded for possible take-over anyway (if the performance optimized version of System Replication is used) Secondary Primary HANA HANA Takeover RS CS preload Same implementation background as with “graceful restart option” of SAP HANA RowStore was transferred in Shared Memory and this can be handed over from thread to thread © 2015 SAP SE. All rights reserved. 177 SAP HANA System Replication Optimized Delta-Data transfer Optimized Delta-Data transfer In Multi-Tier environment – Tier 3 rebuild is now using a delta process if possible Possibility of part-time extraction and operative usage of Multitier members Tier 1 SYNC Tier 2 Tier 1 SYNC Tier 2 ∆ ASYNC Tier 3 Temporarily extract a Tier with a take-over command into online mode o Alternatively the desired Tier can also be shut down to offline Don’t disable replication or unregister Tier o This will delete the HANA-internal snapshot necessary for the delta sync Following Parameter in global.ini controls the retention time for HANAinternal snapshots (default: two hours) o [system_replication] datashipping_snapshot_max_retention_time = 120 o After this time the HANA-internal snapshot – necessary for a delta sync – is deleted o With extending this parameter, snapshots are kept longer o The longer a snapshot is kept the more delta-data shipment is neceassary for reconnection o Extending the parameter to one or more days will anyway result effectively in a full transfer with the regular data changes happening on Primary Tier 3 ∆ Re-syncing No further administration necessary o Snapshot are created with last delta-data transfer automatically and dropped if not necessary any more Use cases Test a take-over with System Replication and re-couple after execution again Rearrange Tiers: E.g. coupling of Tier3 with Tier1 because Tier2 is failing © 2015 SAP SE. All rights reserved. Tier 1 Tier 2 Tier 3 178 SAP HANA System Replication Log & Data Transfer Compression Log & Data Transfer Compression (lossless algorithm LZ4) with SAP HANA System Replication Compression can be used to reduce traffic on data exchange between sites especially over long distance Can be used … Primary HANA DeltaData Secondary HANA Log For initial data transfers For sub sequential delta-data transfers For continuous redo-log transfers Configuration parameter in global.ini [system_replication] enable_log_compression = true (default = false) enable_data_compression = true (default = false) By default content compression is turned off Log Buffer tail compression (default = true) and Log Buffer content compression can be combined As an alternative, also zlib can be offered © 2015 SAP SE. All rights reserved. History of transfer compression in SAP HANA System Replication Log o Log Buffer tail compression (SPS 07) o Log Buffer content compression (SPS 09) Data o Data page compression (SPS 09) 179 SAP HANA System Replication AddHost & RemoveHost in Secondary Online AddHost & RemoveHost in Secondary On Primary and Secondary o As of SPS 09 system replication need not be turned off when adding or removing a host o Operation can be done with hdblcm or preferably hdblcmgui Process for AddHost o Start on Secondary (1) with addition process and then move to Primary (2) o Add a host to the secondary site and start it – starts as a standby and the coordination process to primary side begins (this can take a little) o Add a host to the primary site and start it – as soon as this one is active the Secondary can find a counterpart o Replication begins automatically o With this order of adding the hosts the primary does not operate with a missing secondary Primary Secondary Master Master Worker Worker Worker Worker 2 Standby 1 Process for RemoveHost o To remove a host, first remove it from the primary site and then remove the host from the secondary site (reverse execution compared to AddHost) © 2015 SAP SE. All rights reserved. 180 SAP HANA System Replication Explicit Alerts for System Replication Explicit alerts for SAP HANA System Replication Existing Alerts made more prominent and show themselves not as “Internal Events” any more Own event or alert names o System Replication Connection Closed (Alert ID 78) o System Replication Configuration Parameter Mismatch (Alert ID 79) Alerts only visible with an embedded Statistics Server (ESS) Backwards compatible o Old style alerts are still generated in order not to invalidate any reporting infrastructure after upgrade o Old alerting can be disabled by setting the following configuration parameter in global.ini: [system_replication] keep_old_style_alert = false (default=true) Further info: http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf © 2015 SAP SE. All rights reserved. 181 SAP HANA Disaster Recovery News with SAP HANA SPS10 and Beyond operations • Beta shipment program planned for end of summer 2015 System Replication extensions Improved support for SAP HANA Multitenant Database Containers setups Improving take-over times by parallelizing efforts with RowStore initialization Support for SAP HANA Cockpit with meaningful tiles for SAP HANA System Replication operational information Next Steps (current planning) System Replication extension o Pure Log-based transfer (HotStandby) • Reduced take-over times • Reduced transfer traffic • Build the foundation for active/active Planned beyond Further System Replication extension o o o o o Active/Active Operation (r/o reporting on Sec.) Backup on shadow instance More asymmetric options (nm) More 1:n relationships for shadow instances Time travel via internal snapshots on shadow instance to handle logical errors o Time delay option between sites Log Shipping o Based on backup files (initial data, sub sequential log, steady roll forward) This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 182 SAP HANA System Replication – SPS 10 News Improved Take-Over Performance Improved take-over performance Optimization in RowStore (RS) handling during take-overs Secondary index creation decoupled Extension of the SPS09 feature keeping the Primary RowStore in main memory on Secondary during take-over HANA With SPS10 the rebuild of the secondary indexes during reactivation of the RowStore now can be done in a decoupled way No necessity to wait for finishing the creation process Is done asynchronously in background Short-time missing secondary indexes can be coped with primary key accesses to involved tables until they are created ColumnarStore (CS) is preloaded for possible take-over anyway (if the performance optimized version of System Replication is used) © 2015 SAP SE. All rights reserved. Secondary HANA Takeover RS CS preload 183 SAP HANA System Replication – SPS 10 News Support for SAP HANA Cockpit – Main Tile Tile on the main screen Type of landscape (2 tier or 3 tier) Sums up the status info underneath Presents synchronization mode for the first replication in chain The following states can be shown: Not configured (meaning system replication is not configured) Active and in sync (green square) All services are active but not yet in sync yet (yellow triangle) Errors in Replication (red circle) © 2015 SAP SE. All rights reserved. 184 SAP HANA System Replication – SPS 10 News Support for SAP HANA Cockpit – Details Chain of Systems Behind the main screen tile Lists involved systems in order of their relationships The upper part sums up the chain of systems in case of Multi Tier system replication The mentioned avg. write times are related to log writing o Values on ASYNC connects usually are smaller because of OS buffering Avg. Log Buffer Size is the Log info which is ... SY stands for SYNC AS stands for ASYNC © 2015 SAP SE. All rights reserved. 185 SAP HANA System Replication – SPS 10 News Parsable output of hdbnsutil Easier interaction of external tools with SAP HANA System Replication hdbnsutil -sr_state -sapcontrol=1 When using the additional option --sapcontrol=1 the key-value-pair output can be parsed by a script line by line Delivers output even on offline HANA (not true for host mapping when executed on Secondaries) Support all kind of interactions with SAP HANA System Replication e.g. cluster managers or own developed cluster management scripts etc. © 2015 SAP SE. All rights reserved. 186 SAP HANA in Data Centers: Agenda Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Recovery Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 187 SAP HANA Administration and Monitoring Introduction HANA Studio is one administration & monitoring tool for managing SAP HANA LVM It enables customers to make sure their HANA system runs as expected and provides possibilities to analyze SAP problems HANA Studio It also houses the SAP HANA modeler and the user management for the SAP HANA database © 2015 SAP SE. All rights reserved. SAP Solution Manager can be used for basic administration and holistic monitoring of HANA systems within existing SAP landscapes. It is used by SAP support for early problem analysis and as backbone for CTS+ transport integration. SAP HANA also integrates with SAP Landscape and Virtualization Manager (LVM) for basic operation of larger/more complex SAP landscapes (start/stop & dependencies, etc.) 188 SAP HANA Studio Native Administration & Monitoring Console Administration View Navigator View Properties View © 2015 SAP SE. All rights reserved. 189 SAP HANA as Part of the Customer Solution Provide a holistic operations concept GUI Browser BW on HANA SAP ECC SAP HANA Mobile SAP CRM Warehouse HANA Studio SAP Solution Manager integrates SAP HANA and SAP HANA Studio © 2015 SAP SE. All rights reserved. 190 SAP HANA Administration and Monitoring Screenshots SAP HANA Studio © 2015 SAP SE. All rights reserved. DBA Cockpit in SAP Solution Manager 191 Monitoring of the complete scenario Example: BI Monitoring in SAP Solution Manager Watch the entire application process: from data load to data presentation Replication Monitoring of Technical Systems (ABAP and Java, Application Server, Scale-out Database, Servers) Monitoring of BI Objects (process chains, queries and templates in SAP BW system; jobs in BO system) and SYSTEMS – grouped by BI component type (BW, HANA, SLT, Data Services, Business Objects Explorer, BO Web Applications) Watch the entire stack: from frontend to server © 2015 SAP SE. All rights reserved. 192 The Monitoring and Alerting Infrastructure Supports SAP HANA 1 Threshold value exceeded! 3 4 1. Utilize established SAP Solution Manager functions 2. Knowledge Articles explain how to handle exceptions 3. Notifications lead to Guided Procedures that document the individual steps 2 Daily/weekly/monthly HANA Database Administration tasks Handling of HANA Database Alerts 4. … and provide access to required activities Training on the Job while operating SAP HANA © 2015 SAP SE. All rights reserved. 193 E2E Root Cause Analysis with SAP Solution Manager 7.1 End-To-End Workload Analysis Analyze workload across components End-To-End Change Analysis Ensure compliance with standard configuration End-To-End Exception Analysis Get central access to all log information End-To-End Trace Analysis Investigate performance across the full stack System, Host & Database Analysis Analyze capacity needs and trends per technical component Accelerate time for problem analysis and resolution © 2015 SAP SE. All rights reserved. 194 Using Standard CTS for SAP Business Suite on HANA ABAP CTS ABAP Dev Export SAP HANA Artifacts ABAP Test Import SAP HANA Artifacts How it works? Develop in ABAP workbench (ABAP) or in HANA Studio (HANA Studio) Export HANA developments (views, stored procedures) into transport container Assign transport container to a transport request in ABAP Transport Organizer SAP GUI SAP GUI Application Logic Application Logic SAP NetWeaver SAP NetWeaver SAP HANA SAP HANA Use standard Change and Transport System (CTS) to transport and deploy changes For HANA systems without ABAP stack, use enhanced Change and Transport System (CTS+) Result Utilize full transport system and change control of SAP Solution Manager for SAP HANA Use well-proven technology for transport of changes © 2015 SAP SE. All rights reserved. 195 SAP HANA Administration and Monitoring Feature comparison between Studio <> LVM SAP HANA Studio Administration – – – – Starting/Stopping the SAP HANA database Backup and recovery User and role management Configuration changes Monitoring – Integration of all SAP HANA databases in the landscape possible – Detailed views for specific areas (like services, volumes, performance relevant information) Alerting – Alerts for critical situations are generated by the database automatically – Adjustment of alert thresholds to customer needs – Configuration of Email notifications SAP NetWeaver Landscape Virtualization Management Administration – Auto-detection of SAP HANA systems within SAP landscapes by LVM and required configuration parameters (incl. host- and instance-information) – Managing hierarchies in starting/stopping the SAP HANA database in context of larger SAP landscapes, respecting their dependencies Monitoring – Monitoring of SAP HANA system status and process activity Tracing – Changing trace levels – Display of individual trace files – View to display merged trace files of the different database services and from all database hosts © 2015 SAP SE. All rights reserved. 196 SAP HANA Monitoring, Alerting, Scheduling External monitoring tools Use SAP Solution Manager as relay station for monitoring information for external monitoring tools. A lot of these tools offer SAP Solution Manager as a counterpart in these communications. Alternatively possible by direct SQL connect to SAP HANA Monitoring via direct connection to SAP HANA Statistics Server Scheduling via SQL administration commands send directly to SAP HANA by tool © 2015 SAP SE. All rights reserved. 197 SAP HANA Monitoring, Alerting, Scheduling External monitoring tools List of possible monitoring tools and their support status for SAP HANA ● ● Vendor Tool Support for SAP HANA Contact Centerity BSM, SP Yes (see link, Technical Suitability Review by SAP ICC) Link Blue Medora Ops MP for SAP HANA Yes (see link, Technical Suitability Review by SAP ICC planned) Link DataVard Canary Code Yes (see link) Link syslink Xandria Yes (see link, confirmed by customer) Link Bradmark Surveillance DB Yes (see link) Link Axibase AER for SAP HANA Yes (see link) Link Ozsoft HANA Management Pack Yes (see link), add-on package for Microsoft System Center Operations Manager Link Fujitsu FlexFrame Orchestrator Yes (see link) Link IBM Tivoli Prototype maybe available, please contact IBM directly Link BMC Patrol Native (planned, see link) or via SAP Solution Manager Link HP Openview No native support, only via SAP Solution Manager possible Link HP Oneview Planned (on HP’s roadmap) Link Realtech The Guard (tbd – in contact with Realtech product management) Link If you don‘t find your long-term monitoring tool of choice, please contact your tool vendor directly! There is no certification in place for monitoring tools. The support is managed directly by tool vendor © 2015 SAP SE. All rights reserved. 198 SAP HANA Monitoring, Alerting, Scheduling News with SAP HANA SPS09 and Beyond Monitoring and alerting Improved Monitoring and Supportability o Additional alerts and metrics o Improved resource monitoring Web-based frontend: SAP HANA Platform Cockpit Dynamic Tiering support in SAP HANA Platform Cockpit Enhancements in SQL Monitoring First support for SAP HANA Multitenant Database Containers Planned beyond SAP HANA SPS10 (current planning) SAP DB Control Center o Extended functionality to support cloud environments o Enhanced alert and health monitoring capabilities SAP HANA Cockpit SAP HANA Platform Cockpit for mobile and desktop use Predefined and adaptable administration reports that can be scheduled Extended administration for system replication Improved parameter configuration Further improvements regarding monitoring and supportability Improved support for cloud scenarios o SAP HANA administration o System monitoring for multitenant database containers This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 199 SAP HANA in Data Centers: Agenda Introduction & Overview Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Tolerance Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 201 SAP HANA – unified security architecture Client SAP HANA Tools SQL SQL MDX Client HTTP(s) Application Server Application XS Encryption Authentication/SSO Authorization Identity Store Audit Logging SAP HANA © 2015 SAP SE. All rights reserved. 202 SAP HANA – overview of security functions Function Details Authentication • JDBC/ODBC access: User name and password (incl. password policy), Kerberos, SAML, SAP logon and assertion tickets • HTTP access (SAP HANA XS): User name and password (incl. password policy), SPNEGO, SAML, SAP logon and assertion tickets, X.509 Users and roles • User and role concept, separation of duties, transport mechanism (development -> production system), SAP Identity Management and GRC Access control support Authorization • Privilege concept based on standard SQL privileges + extensions for business applications Encryption • Communication encryption (SSL), data volume encryption (on disk), backup encryption via certified 3rd party backup tools Audit logging • Audit logging framework for logging critical events, e.g. user/role or configuration changes, data access logging, firefighter mode; audit trail written to Linux syslog or to SAP HANA database table Security administration • SAP HANA Studio, SAP HANA XS administration tool, additionally SQL interface for user/role management and other administration tasks (command line tool hdbsql available) © 2015 SAP SE. All rights reserved. 203 SAP HANA – role lifecycle Design time Runtime Developers Studio Administrators Web IDE Studio Repository package1 subpackage1 .hdbroles – DEV © 2015 SAP SE. All rights reserved. Database Repository Activation via _SYS_REPO Export/import: Delivery Unit (DU) Transport: HANA Application Lifecycle Manager package1 subpackage1 .hdbroles – role Grant/revoke PROD 204 SAP HANA – encryption Communication encryption: SSL (can be enforced for client connections) Data encryption: Data volumes on disk Backup encryption: o We recommend to use a suitable 3rd party backup tool (currently certified for SAP HANA: Symantec NetBackup, IBM TSM, Commvault Simpana, HP Data Protector, EMC Data Domain Boost, EMC Networker) Encryption Authentication/SSO Authorization Identity Store Audit Logging SAP HANA © 2015 SAP SE. All rights reserved. 205 SAP HANA Security – data center integration Security Infrastructure Identity Management Infrastructure SQL Compliance Infrastructure SQL Single Sign-On Infrastructure Kerberos SAML Logging Infrastructure syslog SAP HANA User and role provisioning – Out-of-the-box connector for SAP NetWeaver Identity Management – SQL interface for integration with other identity management solutions) Compliance infrastructure – Out-of-the-box connector for SAP Access Control 10.1 Standards-based single sign-on infrastructure – E.g. Microsoft Active Directory Logging infrastructure – Database audit trail written via Linux syslog XS Antivirus © 2015 SAP SE. All rights reserved. NW-VSI compatible 206 SAP HANA – security patching Operating systems SUSE Linux Enterprise and RedHat Enterprise Linux Security patches SAP HANA security patches are published as part of the SAP Security Patch strategy (SAP Security Notes) Delivered as SAP HANA revisions Operating system security patches are provided and published by SUSE/RedHat SAP HANA security documentation General information on SAP HANA security: SAP Help Portal Security whitepaper: http://www.saphana.com/docs/DOC-3751 Best practice document on SAP HANA roles (incl. role templates): https://scn.sap.com/docs/DOC-53974 Important SAP Notes 1598623: SAP HANA appliance: Security (Central Security Note) 1514967: SAP HANA appliance (Central Appliance Note) 1730929: Using external tools in an SAP HANA appliance 1730930: Using antivirus software in an SAP HANA appliance 1730999: Configuration changes in HANA appliance © 2015 SAP SE. All rights reserved. 207 SAP HANA Security News with SAP HANA SPS09 and Beyond New GUI editor for creating repository roles Multi-tenant Database Containers User self services (XS-based): password reset, request new user SAP HANA Cockpit (web-based administration tool) Setting user parameter “mail address” via SAP HANA Studio Extension of SQL-based analytic privileges to SQL views Next Steps (current planning) o Role assignment editor o Certificate management Planned beyond User and role management Encryption service for XS applications More fine-granular configuration options for audit trails; specify audit policies per schema o Kerberos support per tenant o Audit logging enhancements o Improve support for role designers and administrators, reporting and troubleshooting, user self services Encryption o Enhance HANA native encryption o Extend partner support Web-based administration tools o Extend functionality in HANA Cockpit and Web IDE Encryption o Unified certificate handling in the database This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 209 SAP HANA in Data Centers: Summary Introduction & Overview Platform & Appliance methodology (Installation & Update) Persistence Backup & Recovery (System Copy) High Availability Disaster Tolerance Monitoring & Administration Security & Auditing © 2015 SAP SE. All rights reserved. 211 SAP HANA Timeline The journey so far SAP HANA Data Marts Round-Off Release Real Time Data Platform SPS2 SPS4 SPS6 27. June 2011 11. May 2012 Mid 2013 SPS3 SPS5 SPS7 7. Nov. 2011 29. Nov. 2012 End. 2013 SAP Suite powered by SAP HANA Core Topics Innovations SAP BW powered by SAP HANA © 2015 SAP SE. All rights reserved. 212 SAP HANA Timeline What's ahead One Platform, Enabling New Business Delta Backup Active/Active SPS08 SPS10 SPS12 2. June 2014 Mid 2015 Mid 2016 SPS09 SPS11 SPS13 Nov. 2014 End 2015 End. 2016 Dynamic Tiering, Multitenant Database Containers Optimized Sys. Repl. (HotStandby) Simplification This is the current state of planning and may be changed by SAP at any time. © 2015 SAP SE. All rights reserved. 213 More Information © 2015 SAP SE. All rights reserved. 216 More Information SAP HANA documentation SAP Help Portal: http://help.sap.com/hana_platform SAP HANA Administration Guide, several chapters e.g. “High Availability for SAP HANA” covering also Disaster Recovery topic SAP HANA Technical Operations Manual (TOM) FAQ for SAP HANA Operations: SAP HANA Operation Expert Summit FAQ Document List of interesting links about the topic Data Center Operation: http://www.saphana.com/docs/DOC-2935 SAP Notes 2075266: SAP HANA Platform SPS 09 Release Note 1755396: Released DT solutions for SAP HANA with disk 1876398: Network configuration for SAP HANA System Replication 1834153: HANA high availability disaster tolerance config © 2015 SAP SE. All rights reserved. 217 Customer statements about SAP HANA Interesting presentation sessions by SAP HANA customers and users SAP HANA Customer Spotlight. www.sap.com/hanaspotlight More than 15 recordings of customer statement about SAP HANA Global HANA iFG VIP Customer Community: http://ifg.saphana.com Individual Customer Feedbacks Germany: Schukat electronic – The first SME on SAP HANA / SAP HANA trotz Mittelstand (german) "Molson Coors talks SAP BW on HANA” http://diginomica.com/2014/03/25/molson-coors-talks-sap-bw-hana/ (including a 5 min video with global BI specialist) Newsletter MaxAttention Newsletter with portait of HANA usage at Bayer SAP’s own Data Center Management: SAP Data Center © 2015 SAP SE. All rights reserved. 218 Customer statements about SAP HANA Reference & Success stories: SAP HANA Tailored Data Center Integration with Geberit SAP HANA Tailored Data Center Integration with MR (Maschinenfabrik Reinhausen) The winners of the first SAP HANA Innovation award (https://ideas.sap.com/SAPHANAInnovationAward#list_most-recent-list) EVONIK (https://ideas.sap.com/D16201) Mercedes-AMG (https://ideas.sap.com/D15654) Kaeser (https://ideas.sap.com/D16218) Unilever (https://ideas.sap.com/D15539) © 2015 SAP SE. All rights reserved. 219 Thank You! http://www.saphana.com/ Contact information: Dr. Ralf Czekalla Product Management TIP In-Memory Platform [email protected] © 2015 SAP SE. All rights reserved. 221 © 2015 SAP SE. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP SE. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. © 2015 SAP SE. All rights reserved. 222
