IBM SAP HANA Produktiv auf der IBM Plattform

Transcription

1 IBM SAP HANA Produktiv auf der IBM Plattform Betriebsaspekte Roland Goll IBM Solution Sales for SAP Mobile:

2 SAP HANA Use Cases HANA ist für SAP hoch strategisch und wird in allen Bereichen forciert

3 In Memory Computing: Re-think Paradigms Today Future Calculation Application Layer Database Layer Calculation In-Memory Computing Imperative: Avoid movement of detailed data Calculate first, then move results

4 IBM : Database and Technology / HANA Co-innovation Partner of the Year Run Together Database and Technology / HANA Co-innovation Partner of the Year Winner: IBM

5 Why IBM for SAP HANA? What makes the difference? scaleout certified start small, grow big simple modular growth installation and managed services all T-Shirt sizes seamless preinstalled unlimited scalability simplified maintenance simplified order process appliance in a single box HPC goes Business proven technology preloaded integrated packaging and assembly easy install no SAN to manage simple wiring expand database by adding nodes highly available no breaks superior performance no full mesh speeds deployment priority support highly reliable

6 IBM Workload Optimized Solution for SAP HANA appliance Applications SAP Know How SUSE SAP HANA FPO functionality OS SUSE Linux Enterprise Server Priority Support for SAP applications Server HW ex5 - x3690 X5 and x3950 X5 IBM Know How ITM TSM IBM Director Data Center Ready Reliability by eliminating single points of failure Reduced risk, maintainance and administration Persistence in internal disks Integrated Backup / Restore High Availability Monitoring Disaster Recovery Solutions Security and Auditing Technology Services provide a safe project start in the datacenter

7 Please check for updates frequently 7

8 8

9 9

10 10

11 IBM Systems solution for SAP HANA sizes / building blocks / upgrade path Size XS S S+ M L Building Block x3690 X5 x3690 X5 x3950 X5 x3950 X5 x3950 X5 Part Number (Sys x - config) 7147-HAx 7147-HBx HAx HBx 7143 HBx HCx Intel CPU 2 x E x E x E x E x E RAM 128 GB DDR3 (8 x 16GB) 256 GB DDR3 (16 x 16GB) 256 GB DDR3 (16 x 16 GB) 512 GB DDR3 (32 x 16 GB) 1 TB DDR3 (64 x 16 GB) Log Storage 10 x 200 GB 1.8 MLC SSD 10 x 200 GB 1.8 MLC SSD 1.2 TB iodrive2 FusionIO 1.2 TB iodrive2 FusionIO 2 x 1.2 TB iodrive2 FusionIO Data Storage x 900 GB 10k SAS HDD 8 x 900 GB 10k SAS HDD 16 x 900 GB 10k SAS HDD Storage Ctrl 2 x M x M x M x M x M5015 Data / Log Storage Summary 1.6 TB RAID 5 data and log storage 1.6 TB RAID 5 data and log storage 5.4 TB RAID5 data storage 1 TB log storage 5.4 TB RAID5 data storage 1 TB log storage 10.8 TB RAID5 data storage 2 TB log storage Ethernet 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 8x 10 GbE, 12 x 1 GbE Upgrade Option Scale Up or Scale out XS - > S Up to 16 node scale out with HA, SAP certified S+ M M L (with L-option) Up to 56 node scale out with HA, SAP certified Up to 56 node scale out with HA, SAP certified Software Preload: SLES4SAP SAP HANA Preload: SLES4SAP SAP HANA Preload: SLES4SAP SAP HANA Preload: SLES4SAP SAP HANA Preload: Addtl. lic.

12 IBM Systems solution for SAP HANA Single Nodes for SAP Business Suite Size XL XXL Building Block x3950 X5 x3950 X5 Part Number (Sys x - config) tbd tbd Intel CPU 8 x E x E RAM 2 TB DDR3 (128 x 16 GB or 64 x 32 GB) 4 TB DDR3 Log Storage 2 x 1.2 TB iodrive2 FusionIO 4 x 1.2 TB iodrive2 FusionIO Data Storage 16 x 900 GB 10k SAS HDD 24 x 900 GB 10k SAS HDD Storage Ctrl 2 x M x M5015, 1 x M5025 (128 x 32 GB) Single node only for SAP Business Suite on HANA Data / Log Storage Summary 10.8 TB RAID5 data storage 2 TB log storage 16.2 TB RAID5 data storage 4 TB log storage Ethernet 8 x 10 GbE, 12 x 1 GbE 8x 10 GbE, 12 x 1 GbE Upgrade Option Scale Up or Scale out XL XXL (with additional memory, iodrive2, M5025, EXP 2524) Software Preload: SLES4SAP SAP HANA Preload: SLES4SAP SAP HANA 12

13 IBM Scale-Out capabilities today and in the future For the first published benchmark of a scale-out SAP HANA System SAP chose a 16- node cluster of IBM X5 servers with 512 GB RAM TB The volume of data was an equivalent of 100 TB uncompressed user data. From each of about 6 minutes could be loaded 100 million records. The response times of typical user queries ranged in subsecond area. Even complex queries over the whole data required only a few seconds. Download this reports under: p/us/en/landing/hana.html) The ultimate proof of the performance of the IBM solution, SAP delivered itself with the showcase of a 100 TB memory system on the Sapphire in May Here SAP coupled 100 IBM SAP HANA systems (IBM x3850 X5 Size L) into a single scale-out cluster. See details: ?

14 Reference Customers Link Link Link Link Fragrance Company owns several European fashion brands Link 14

15 : A Scalable File-system for Shared Nothing Architectures Node Node Node Node common file system namespace Local Disk Local Disk Local Disk Local Disk Local Disk Local Disk Cluster: thousands of nodes, fast reliable communication, common admin domain. Shared disk: all data and metadata on disk accessible from any node, coordinated by distributed lock service. Parallel: data and metadata flow to/from all nodes from/to all disks in parallel; files striped across all disks. Key Ideas: Locality Write Affinity Metablocks Pipelined replication Distributed recovery NEW

16 IBM SAP HANA Appliance Scale Out HA (with Built in High Availability via ) Production up to 56 TB with 56 Nodes Production Node 1 TB Production FAILED Node GB1 TB Production Node 3 1 TB Production Standby Node 2 11 TGB TB SAP HANA DB DB partition 1 DB partition 2 DB partition 3 - SAP HANA DB worker node - SAP HANA DB worker node - SAP HANA DB worker node - SAP HANA DB standby worker node - index server - statistic server - SAP HANA studio - index server - statistic server - index server - statistic server - index server - statistic server shared filesystem - HDD flash HDD flash HDD flash HDD flash primary data HDD replica data01 data01(1) data02(3) data03(2) log01 data02 data01(1) data03(3) log02 data03 data01(2) data02(1) log03 log03(3) data01(3) data02(2) data03(1) Log replica log02(3) log03(2) log01(1) log03(3) log01(2) log02(1) log01(3) log02(2) log03(1) x HBx+HCx (1 TB) x HBx+HCx (1 TB) x HBx+HCx (1 TB) x HBx+HCx (1 TB)

17 SAP HANA appliance Scaleout w/ High Availability & Disaster Tolerance (Recovery) Available with HANA SPS5 since end of Nov. 2012

18 SAP HANA appliance Scaleout w/ High Availability & Disaster Recovery Avoid idle infrastructure e.g. QA System Internal disks on remote site are used for the synchronous replica of the primary site. Non production systems (e.g. QA or Pre-Production) can run on the remote site with direct attached disk expansions (EXP2524) Validated by SAP and now ready for implementation SAP Note

19 SAP HANA appliance Stretched HA Cluster with High Availability & Disaster Recovery HANA Appliance PROD HANA Appliance PROD Standby/DR + NonProd Name Server Index Server Data Disks Log Disks SAP HANA PROD in DataCenter 1 Synchronous Data replication (Production Data) Name Server Index Server Data Disks Log Disks SAP HANA DEV or QA in DataCenter 2 (including Storage Replication of Productive Data on HANA Appliance internal Disks) Internal disks on remote site are used for the synchronous replica of the primary site. Non production system (e.g. QA or Pre- Production) can run remotely with direct attached disk expansions (EXP2524) quorum node Site 3 Data Disks Log Disks EXP2524 Avoid idle infrastructure

20 SAP HANA Disaster Recovery Disaster Tolerance The basic features for disaster tolerance in SAP HANA are available from SAP. Details are described in SAP presentations on their web site. Possible solutions: Recovery time Availability Backup/recovery over distance (transfer) hours today Synchronous replication to two sites minutes today System replication with warm standby (SPS5) minutes today Log shipping 1 seconds planned: 2013 Enhanced DT (asynchronous replication) planned: late 2013 Note 1 : Log shipping functionality needs to be provided by SAP (with HANA SPS5) If multiple nodes fail at the same time or if a second node fails while the reconfiguration of the has not been recovered upon a single node fail, then the whole cluster will go down as some primary and secondary (replicated) data is lost. Therefore, this is considered a disaster. If such disaster happens and a whole site (here primary) goes down, then a scenario where a secondary datacenter would take over is called disaster tolerant.

21 SAP HANA virtualized Supported: Single node Non-Production deployments on certified scale-up single hardware appliances such as test and development systems. SAP supports VMware vsphere 5.1 with the release of SAP HANA SP5. Restrictions: Currently the largest SAP HANA virtualized database is limited to the number of cores supported by a single vsphere (64). That means that currently the maximum memory size for a VMware virtualized SAP HANA instance is 512GB (with 40 cores). VMware vsphere Virtual machine does have a performance impact on SAP HANA processing from a CPU processing, I/O and memory access perspective. The impact is highly dependent on the specific operation being executed and the data on which is operating on. The specific impact cannot be predicted but across a range of pre-release tests it has been observed to be about 10% or less. SAP HANA Scale-out and HA scenarios are NOT currently available for deployments on VMware. Also, VMware vsphere Fault Tolerance and VMware vsphere System Cloning are NOT supported for use with SAP HANA. SAP HANA appliances will continue to be offered without virtualization. More information: The latest information from SAP about running SAP HANA on VMware can be found at and SAP note

22 SAP HANA Network connectivity - generic diagram IBM IBM The following network connections are required for SAP HANA and remote server management: 10Gb network with VLAN configuration for all SAP HANA communications Or 1Gb dedicated network between SAP ERP and SAP HANA (10Gb network connection is optional) 1Gb dedicated network for Business Intelligence (BI) client access 1Gb dedicated network for data management 1Gb dedicated network for appliance management 1Gb dedicated network for internal communications (also valid for single-node cluster) 1Gb dedicated network for server management via IMM (Integrated Management Module)

23 Tivoli Storage Manager: Data Protection for SAP HANA databases Backup recovery for: SAP HANA Database, Redo Logs, Configuration Files node01 node02 node03 node04 SAP HANA backup IMDB DB partition 1 DB partition 2 DB partition 3 DB partition 4 TSM Data Protection for SAP HANA databases Run on one node in SAP HANA cluster Trigger SAP HANA backup into filesystem Send backup files for all nodes to TSM Exploit high performance features as needed shared file system - DP for SAP HANA Backup files HDD HDD HDD HDD Save pts & redo logs TSM Server Backup / Recovery of other system files can be done by TSM BA client Demo:

24 Multi Tenancy Möglichkeiten und Grenzen die Hardware effizient zu nutzen Unterstützt von SAP und IBM Aktueller Stand laut SAP HANA Test HANA QA Multiple SAP HANA Instanzen auf 1 Scale- Out Cluster ( MCOC ) wird unterstützt soweit pro Node nur eine SAP HDB (HANA Instanz) installiert ist Produktion MCOS Multiple Components auf 1 Server Mehrere SAP HDBs (HANA Datenbanken) auf einem Server (Multiple Components=SIDs), werden nicht unterstützt (Ref. SAP Note ) HANA APO App2 App3 App4 MCOD Multiple Components in 1 singulären Datenbank wird unterstützt Achtung mögliche Einschränkungen im Betrieb: Herunterfahren und Recovery der Datenbank betrifft alle Inhalte gleichzeitig (Ref SAP Note ) Keine Produktion MCOS Multiple Components auf 1 Server Mehrere SAP HDBs (HANA Datenbanken) auf einem Server (Multiple Components=SIDs), werden unterstützt (Ref. SAP Note ) (SAP Multi-SID-Installer ab HANA SPS5) Achtung: Konfliktpotential bei unterschiedlichen SAP HANA DBs auf einem singulären Server Beispiele: gemeinsame Daten- und Log-Voluumes mögliche Performance-Einbußen Interferenzen der Systeme untereinander

25 Agents on the SAP HANA box Monitoring Agents Backup Agents Virus-Scan prohibited NO!!! May corrupt your data! May severely impact SAP HANA's performance IBM will provide guidance on Supported agents (e.g. Tivoli agents) Tolerated agents (3rd party agents) Blacklisted agents (e.g. virus-scan)

26 IBM Appliance Support for SAP HANA Take what you need, it s ready! Application SAP Systems Operation Suse SLES Reactive Services IBM Standard Support for SAP Appliance Project Services System Operation SAP Application SinglePoint of Contact Project Services Leistungen Proactive Services Reactive Services Base Services Server Support Standard or Priority HWMaintenance Service Pack Passport Advantage Optimized reactive support Single Point of Contact Proactive Services HWand SW installation services onsite services Individual contract due to customer needs SAP Licence support SAP Application Support HW Maintenance / SW () Support / remote Support Central call number Remote Support Shorter Commtitted Recovery Time Optional Optional 7x 24 h (Severity 1 problems) Reaction time for critical problems (Severity 1) SLES Support Single point of contact Immediate problem solving / fixes in sync with appliance Health Check for appliance incl. Microcode and release mgmt. Yearly capacity planning with customer Detailed planning workshop Preinstallation Call / meeting HW installation / SW implementation Support customer skill development Implementation Patches / Updates /Reconfig. / Upgrades Consulting in planning / installation/ SW implementations Montoring 1h (priority) SUSE recomme nded Service Level Objective (SLO) 2h required Service Level Agreement (SLA) 30 Minutes SAP Base Services Total Solution Support Full Service Managing / Operating

27 Services to Install, Monitor & Maintain SAP HANA Platforms from IBM Application (Customer/SAP) Application SAP BWA / HANA Implementation (IBM ) Design Work shop Installation Systems Operation SAP Appl. Patch Management Update MC/ Release Mgmt System Update Ongoing Support (IBM) SAP Single Point of Contact into IBM Proactive - Optional (IBM) Appl. Status Analysis Microcode Release Mgmt. Analysis Application Health Check System Health Check Yearly Configration Planning Remote Access Hot Standby In Test Backbone Integration Sol.Mgr. & Retain TSS Reactive - Standard (IBM HW & SW Support) HW Maintenance ETS Storage Passport Adv ETS Linux (SLES) SAP Maintenance

28 IBM SAP HANA Highlights IBM is in the leading position with SAP HANA and PoC projects (over 50% market share). The SAP AG itself in Walldorf developed SAP HANA software on IBM x3850 X5 systems and is due to the development activities for HANA even the largest customer for IBM System x-based HANA systems. IBM HANA offerings are developed with the active participation of our IBM SAP HANA development team, which is working closely with the development teams of SAP. Simple, Seamless, Scalable! The IBM SAP HANA solution has no single point of failure! The first 16 TB cluster that SAP has certified, consisted of IBM System x servers, now we have certified up to 56 TB cluster and additionally 2 TB (XL) and 4 TB (XXL) single nodes for SAP Business Suite on HANA, which currently is exclusively available from IBM! The first cluster of 100 TB SAP, presented at SAPPHIRE 2012, consisted of 100 IBM x3850 servers Size L, was extended now to 150 TB. - The main differentiators in the market for IBM SAP HANA solutions The IBM General Parallel File System () was originally developed to meet the availability requirements of the media industry and the high-performance computing requirements of the natural sciences and has developed since its market introduction in 1997 for more and more applications.

29 Besuchen Sie uns auf unserem Stand mit IBM DB2 BLU DIE Standard Datenbank für SAP mit neuer Hybrid- In-Memory Technologie mit IBM Systems Lösungen für SAP HANA und erfahrenen Beratern zu BI Lösungen im SAP und non-sap Umfeld

30 Herzlichen Dank! Roland Goll IBM Solution Sales for SAP Mobile: