Downloaded 31 times
Uploaded byChris Kernaghan
01 sap hana landscape and operations infrastructure v2 0
This document discusses SAP HANA landscape and operations infrastructure. It covers HANA editions and technical scenarios, the HANA database lifecycle including patching, installation, backup and restore. It also discusses using HANA as a platform and monitoring HANA performance. Additionally, it outlines different data load scenarios into HANA and provides tips for tools like SAP BODS and SLT. The document concludes that introducing HANA brings technical challenges across areas like reporting, data management, development and operations that require consideration.
More Related Content
Similar to 01 sap hana landscape and operations infrastructure v2 0
01 sap hana landscape and operations infrastructure v2 0
- 1. and Chris Kernaghan Capgemini UK 25rdApril 2013 SAP HANA Landscape and Operations Infrastructure
- 2. 2The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved.
- 3. 3The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. Topics HANA Editions and Technical Scenarios HANA Database Life Cycle HANA as a Platform HANA Performance Monitoring HANA Data Load Scenario Support Summary and Questions
- 4. 4The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Editions
- 5. 5The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Scenarios (Needs redrawn) Single System (Classic Scenario)
- 6. 6The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Scenarios (Needs redrawn) MCOD Scenario
- 7. 7The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Scenarios (Needs redrawn) MCOS Scenario
- 8. 8The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. SAP HANA Database Life Cycle Patching Uses Software Update Manager Cumulative patches Can be patched online or offline Check dependencies with HANA Studio Installation HANA Unified Installer Python based installer Architecture very like SQL Server Backup Internal Backup tool available 3rd Party Backint capability Major Backup vendors certified Restore Persistence layer Recovery will be tested during your project Data/Log corruption Logical Corruption Performance Primary application = HANA Studio Secondary application = DBA Cockpit SQL Scripts to query Database views/tables
- 9. 9The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA as a Platform
- 10. 10The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Monitoring
- 11. 11The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. Monitoring Screen Shots Add Screenshots of E-mails, HANA Studio, DBA Cockpit
- 12. 12The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. HANA Dataload Scenarios A number of data load tools available Direct flat file/CSV upload Business Objects Data Services (BODS) SAP Landscape Transformation (SLT) Sybase Replication Server (SRS) Sybase Event Stream Processing (ESP)
- 13. 13The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. SAP BusinessObjects DataServices - Tips and Tricks Virtualisation – Do you do it? Transformations – On the way in Performance profile often Invest in your network – 10GBe is essential
- 14. 14The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. SAP Landscape Transformation - Tips and Tricks Based on the same SAP technology as TDMS and NZDT Trigger based – so can be used on non-SAP databases as well Uses an SAP ABAP Stack – good excuse to use NW7.3 or 7.4 in May 2013 Replication jobs – rule of thumb, 10 tables per replication job Normal SAP ABAP Administration
- 15. 16The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. To Summarise Reporting Tools and Solutions Data Management Development Methodologies Operational Approach Introducing SAP HANA into your estate introduces a challenges across a number of categories In the time available today we’ve just touched on some of the Technical challenges to consider Technical
- 16. 17The information containedin this document is proprietary. Copyright © 2013 Capgemini. All rights reserved. Final Thoughts
- 17. The information containedin this presentation is proprietary. © 2013 Capgemini. All rights reserved. Rightshore® is a trademark belonging to Capgemini. www.capgemini.com Chris Kernaghan Senior Technical Strategy Consultant Capgemini UK Email: Chris.Kernaghan@capgemini.com http://twitter.com/BoobBoo http://www.linkedin.com/in/chriskernaghan Phone: +44 870 366 0788
Editor's Notes
- #3 So your company has chosen HANA as a PoC or as a Pilot or even you are using it in anger – so Now WhatHow are you going to install it - Back it up - Move transports – Monitor Performance – Manage data loads.Restaurant StoryI am not going tell you how to do it and expect you to follow it to the letter, but hopefully give you some help on achieving your operational goals
- #5 Platform Edition – HANA One (Cloud) and normal database on appliance or on homebrew softwareEnterprise – usually used in Sidecar scenarios – see additional components to get data into the system more effectivelyHANA Solutions – how to get the data out of HANA in a reasonable fashionNot all vendors are created equal, some are better at some things than others – but remember that some HANA skills are very hardware specific, so be care who you engage
- #6 This is the single instance – it is usually reserved for Production systems or HANA One systemsIt is a single Appliance with a single schema will be used for Business Suite on HANAAdvantages – no dependencies HANA Sizing is important – all the data storage sizes within the SAP Quick Sizer are based on Uncompressed data – this means that if you are using database compress at the minute then you need to work out your uncompressed size for your database to get an accurate sizing
- #7 This is the MCOD scenario – 1 HANA Database with multiple schemas and applicationsAdvantages – better hardware utilisation Never really understood this scenario, in any lifetime!Better Backup and restore scenarios
- #8 This is the MCOS scenario – Multiple databases on the same applianceNo virtualisation over head
- #9 At it’s core HANA is an SQL database It has tables, columns, rows – it is not magic!BackInt certified Dec 2012
- #10 HANA is a platform, it has a number of built in capabilitiesIt has a tomcat web server, R statistical engine and a Server side Javascript engineAll of which need supporting – Can be monitored from the HANA Console, Solution Manager or SQL ScriptsHANA Applications will provide new areas of administration headaches around high capacity performance applications and their architecture that we cannot predict yet!Expect more WebDev solutions to enter into SAP World
- #11 Explain a bit more about how it monitors and the Life cycle1 Pilot – no real monitoring required, just snapshot monitoring2. PoC – Turn on initial alerting from and write some scripts for HANA Studio3. Implementation – Turn on Solution Manager alerting – using extended products like LVMDon’t do it – start as you mean to go on in your PoC, use Solution Manager and do not accumulate Technical Debt
- #13 More tools to administrate that you have never heard of or even seen
- #14 Do you Virtualise the BODS, very difficult question to answer without testingProvides good scalability and powerBottle necks on IO and network which degrade performanceScale up as well as out easilyHow many transformations are the developers doing and are they fixing data as well – these all carry performance cost and there will be a tipping pointBe able to show the performance gains with each iteration, and also the degradation if necessary – not everything is going to work every time
- #15 Triggers are only good for Low to medium activity tablesExpect some push back when linking the SLT to non-SAP databases, do your homework and be able to provide volumetrics to the DBAs of the other database – it is professional courtesy!Replication jobs run constantly in the background, and reset the timer after 24 hrs – do not worryThe LTR transaction runs in WBA – so set up Single Sign on
- #16 Never used them in anger, but have had a few conversations with people on them
- #17 In the time available today - we’ve just touched on some of the technical considerations