Presentation on theme: "Preparing Your Technical Landscape for an SAP HANA Installation"— Presentation transcript:
1 Preparing Your Technical Landscape for an SAP HANA Installation Dr. Bjarne BergCOMERIT
2 In This Session … This session examines, in detail: The most critical sizing, integration and performance factors you must address when adopting SAP HANA.Trends amongst hardware vendors for virtualization, cloud, and hosted systems, including options, requirements, and costs associated with network, backup, and application serversHow the SAP HANA database —uses persistent storage to provide a fallback, and how fault tolerance, disaster recovery, and high-availability can be setup for your SAP HANA implementationWhat is covered in this session?Advanced tips and trick in Query designer and BEx AnalyzerThe advanced tips and tricks are explained using business scenariosOverlooked and obscure features are brought to limelightLots of demos to explain BExGetData and other topics
3 What We’ll Cover … Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsLandscape Deployment PlanningBackupHigh AvailabilityWrap-upLet’s begin with features of Query Designer
6 Hardware Options 2014 Onward These systems are based on Intel's E7 IvyBridge processors with 15 cores per processor (the old had only 10).UPDATE: Hitachi Servers and Dell (R920) are now also available
8 Support PackagesAs of 2014, SAP introduced the idea of “production verified revisions” to provide in- depth testing of all service packs for SAP HANABased on the planned releases over the next 24 months, customers should adjust their plans for service packs accordingly
9 Sizing OverviewDepending on the software components there are several sizing options:BW system for HANAQuickSizer – New implementation only, not migrationsBW Automated Sizing tool in the Migration CockpitRule of ThumbT-Shirt SizingBusinessSuite System for HANAQuickSizer for BusinessSuite on HANAAutomated Sizing toolVendor ToolsStandalone HANA System
10 SAP QuickSizer for HANA There are three versions of the tool for each version of SAP HANAThe QuickSizer for the Business Suite allows you to size for specific modulesThe second QuickSizer version is for SAP HANA on SAP NetWeaver BWThe last is for those who want to use SAP HANA as a standalone platform for in-memory data (i.e., using SAP Data Services to load data to)SAP’s QuickSizer for SAP HANA is available at
11 SAP QuickSizer for New BW HANA Implementations If you’re using planning in SAP NetWeaver BW, enter the info here. The fields marked with * are mandatory.For H-PLAN-1, enter the maximum concurrent users in the USERS field. The S.T. and E.T. fields are the start and end times for the processing.By entering this type of information, you’ll get estimates of loads on the SAP HANA system by time periods at the end of the sizing exercise.Enter the estimated number of information consumers (H-BW-INFO), business users (H-BW-BUSI.), and experts (H-BW-EXPER). SAP suggests a ratio of 71%, 26%, and 3% for each user group, but you can enter your own mix if you have better estimates.
12 SAP QuickSizer for New BW HANA Implementations (cont.) Enter the InfoCube and DSO information. The max number of dimensions (DIM) you can enter for the InfoCube is 13. The three fixed dimensions of BW are already included, so just enter the free dimensions.The field KEYF. refers to the number of key figures in the fact table of your InfoCube, while the field COM. is the estimated compression.If you don’t have better estimates, a rate of 5 may serve for the initial sizing before you refine the estimates with your hardware vendor.In the INITIAL LOAD field, you enter the number of records in the existing InfoCube, and in the PERIOD. UPLD field, you enter the number of records you estimate will be loaded periodically.
13 SAP QuickSizer for HANA — Output This SAP HANA sizing example calls for 1.6TB of memory.In this case, SAP HANA for BW will deploy the master data, ABAP system tables, and row store data on the master node. The other connected server node(s) will contain the InfoCubes and DSOs.
14 HANA Sizing Tool for Existing BW Implementations To increase speed, you can suppress analysis tables with less than 1 MB size.SAP has released an updated tool that generates a report significantly better for sizing SAP BW than using the QuickSizer. This tool should be used by all existing BW implementations for sizing (QuickSizer is only for new implementations).This program takes into consideration existing database, table types, and includes the effects of non-active data on the HANA system.The higher precision you run the estimate at, the longer the program is going to run.With 12 parallel processors and 10TB database, it is not unusual to see minutes runtime
15 SAP BW on HANA Automated Sizing Tool Since timeouts are common when running the sizing program, you can temporarily change the parameter in rdisp/max_wprun_time to 0 in BW transaction RZ11. Finally, you estimate the growth for the system as a percentage, or as absolute growth.The output is stored in the file you specified and the file can now be ed to hardware vendors for sizing input and hardware selection.This program is referenced in SAP Notes and on the Service Marketplace
16 Sizing for BusinessSuite on HANA SAP has created a program for sizing HANA for BusinessSuite:This should be used for all HANA migration projects of ERP/ECC/BusinessSuite
17 Sizing for BusinessSuite on HANA Some Vendors have also created their own sizing programs, that also include hardware prices.
18 QuickSizer for BusinessSuite on HANA For New BusinessSuite implementations you can use QuickSizer and send the results to SAP for further processing
19 QuickSizer for BusinessSuite on HANA This is the input screen where you enter the number of expected transaction by module. You are also asked to enter estimated changes and new records as well as operating times of your systemHere you get the size in SAPS as well as memory and disk requirements
20 Sizing a Standalone HANA System - Output This is the input screenHere you get the size in SAPS as well as memory and disk requirements
21 Rule-of-Thumb Approach to Sizing HANA — Memory Memory can be estimated by taking the current system size and running the programs in “get_size.zip” in SAP Note to get row and column store sizes for your systemThe 50GB is for HANA services and caches. The 1.5 is the compression expected for rowstore tables and the 4 is the compression expected for column store tables. The 2-factor refers to the space needed for runtime objects and temporary result sets in HANA. Finally, the term “existing DB compression” is to account for any compression already done in your system (if any).Memory = 50GB +[ (rowstore tables footprint / 1.5) +(colstore tables footprint * 2 / 4) ] * Existing DB CompressionRemember, these are quick rules of thumb, so don’t rely on it for finalized budgeting and hardware purchases
22 Rule-of-Thumb Approach to Sizing HANA — Disk The next item you need is disk space, which can be estimated by the following:In this example, you need 4 x 710GB disk for the persistence layer and about 710GB for the logs. This equals around 3.5TB (don’t worry, disk space of this size is now almost “cheap”).The persistence layer is the disk that keeps the system secure and provides for redundancy if there are any memory failures, so it’s important not to underestimate this.Disk for persistence layer = 4 MemoryDisk for the log = 1 MemoryRemember, these are quick rules of thumb, so don’t rely on it for finalized budgeting and hardware purchases
23 Rule-of-Thumb Approach to Sizing HANA — CPU The CPUs are based on the number of cores that you include. For example, 10 core CPUs now exist (depending on when you bought your system).If you have a single node with 4 x 10 cores, you will have 40 cores and can handle 200 active users on that hardware node, and quite a larger number of named users.CPU = 0.2 CPU cores per active userRemember, these are quick rules of thumb, so don’t rely on it for finalized budgeting and hardware purchases
24 A T-Shirt Model for Sizing HANA on BW A T-shirt model is a quick way to get some basic ideas on what a system may look likeWhile very inaccurate for sizing, it provides basic information for those just starting to consider SAP HANAThe number of processors are largely driven by the number of users and usage patterns. Serious consideration should be made before buying hardware.
25 Summary of HANA Sizing Approaches Approach Quality of Estimate Effort RequiredT-Shirt Sizing Sort of “OK” Very LowRule of Thumb Better LowSAP QuickSizer Much better (new implementations only) HighSizing for programs Excellent (for existing BW systems) Moderate/LowWork with your preferred vendor before ordering your hardware or finalizing your budgetsSAP Note (ABAP report to help with BW on HANA Sizing)SAP Note (SAP NetWeaver BW Migration Cockpit for SAP HANA)SAP Note (SAP BW Checklist for Migration),SAP Note (Sizing the Master node)
26 What We’ll Cover … Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsLandscape Deployment PlanningBackupHigh AvailabilityWrap-upLet’s begin with features of Query Designer
27 1. Lessons Learned: Buy Hardware Early The typical lead time for the basic HANA appliances is as little as 4-8 weeksHowever, for large scale environments, or multi- node environments, the lead times can sometimes be as long as weeksThis is particularly true for virtualized systems managed by a third-party who has to set them up, configure backup, and learn the new technologyGet a small team on site early for planning, budgeting, and sizing; and hold off staffing all team members from the business until you get a confirmed hardware delivery date
28 2. Lessons Learned: Get the Right Team Members While there are many with basic certifications in HANA, the pool of qualified experienced resources is limitedGreat HANA resources are most likely working on another project alreadySo, if you want the best, be prepared to give your implementation partner several weeks lead timeDo you want “who is available” or “who should be available” on your project? Be prepared to give your implementation partner longer lead times than usual.
29 3. Lessons Learned: Include Training for your Staff There are a lot of “myths” and beliefs about HANA that you have to address earlyBefore you start the project, make sure your implementation partner has a formal written training plan on how they will provide knowledge transferInclude your support staff and Basis people in all project discussions from the first planning sessionMany are “fearful” of a new technology and are unsure how this will change their work. You should provide real demos and workshops early so that everyone knows what is happening and how HANA will change their day-to-day jobs.
30 4. Lessons Learned: Hardware Sizing Should Include Growth Some customers forget that sizing would be for 3 years out and not based on current system size aloneYou should have a sizing estimate that includes new projects, data growth, and data retention policies, as well as periodic scheduled clean up activitiesFunding for hardware is sometimes easier in a project mode, and many companies plan for 30-50% more capacity as part of the initial rollout if they can afford it
31 5. Lessons Learned: “Master-Node” Size Some hardware vendors want to maximize the number of processes available to the users. They can do this by using multiple smaller nodes with many processors in each.The drawback is that all of your row and master data stores may not fit on the small node as you grow.Pay very careful attention to the row-stores sizes and the master data growth when buying hardware. You don’t want to have to upgrade shortly after go-live.
32 6. Lessons Learned: Create an Ecosystem of Experts Having access to the best and brightest within SAP, consulting firms, and industry experts is key when issues or questions ariseThese people are very busy and are often engaged on many projects as “supporters”Formally assign a team of 2-3 experts to come in and meet with your team a few times during the project planning and execution. Make sure these project advisors are hands-on and that they can act as technical go-to resources for your team if questions arise.
33 7. Lessons Learned: Think BIG A HANA implementation should not be treated as a replacement project. It is an enabler …Plan ahead on what you are going to do with the new technology, e.g., mobile, forecasting, planning, BI dashboards, customer and vendor facing analytics, market basket analysis, stratification, data visualization, etc.Early in the project create a 2-3 year strategic plan that demonstrates to the leadership what you are going to do with this new technology. Present it as new capabilities not just how fast it is …
34 8. Lessons Learned: Plan for Reporting and System Consolidation After go-live you should have planned for howyou are going to migrate all reporting and management analytics on to HANA and away from datamarts and standalone expensive systems that are not integrated into the long-term visionYou will most likely have to do some “selling” to your fellow employees and be prepared to give them “free access” to your HANA systemHANA is not just for BW or Business Suite. It is an enterprise platform for integrated analytical and data processing. You can give developers access to your system and they can build their own Agile marts inside HANA, even if they don’t want to use BW.
35 9. Lessons Learned: Near-Line Storage Can Save Millions Removing data that is not needed on a daily basis from your system and placing it on near-line storage instead of in-memory can save you millions.In one project a customer took his system from 112TB to 38TB by simply moving data to near-line storage (NLS)An Asian firm took a 3.8TB BW system to “only” 900GB after cleanup and an NLS implementationThere are many NLS solutions available that can save you big bucks by reducing the need for multi-node, multi-terabyte HANA systems. Take a serious look at SAP IQ solution for NLS. It is tightly linked with HANA already.
36 10. Lessons Learned: Save Money with MCOD and MCOS You may not need separate hardware for sandbox and development environmentsUsing Multiple Components One Database (MCOD) and/ or Multiple components One System (MCOS) you can simplify the number of hardware environments you needSAP NetWeaver BW on SAP HANASAP Finance and Controlling Accelerator for the material ledgerERP operational reporting with SAP HANASAP Finance and Controlling Accelerator: Production Cost PlanningSAP Rapid MartsSAP COPA AcceleratorSAP Operational Process IntelligenceSAP Cash ForecastingSAP Application Accelerator / Suite AcceleratorSmart Meter AnalyticsIn addition to custom developed datamarts, all items above can run in an MCOD setup (see SAP Note for more details)
37 What We’ll Cover Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsHardware TrendsLandscape Deployment PlanningBackupHigh AvailabilityWrap-up
38 Landscape Deployment Planning Virtualization MCOS MCOD Technical Co-DeploymentDeploymentScenarioHANA DBsMultipleOneDB SchemaAvailabilitySupported for DEV & QA systemsDefined by:White List for BWWhite List for SuiteBusiness Suite components SCM and/or SCM co-deployed with ERP
39 Landscape Deployment Planning - Virtualization (on premise) Share hardware resources for multiple Suite systems and HANA instances with virtualization techniques. Virtualization technology separates multiple OS images each containing one HANA DB.n x Virtualized Appliancesn x HANA DBn x DB Scheman x ApplicationsStrengthsOnly one HANA system neededResource mgmt per virtual instance possible (RAM, CPU, Storage)Easy scalabilityDifferent Server Level Agreements per virtual machine possibleIndependent deployment & maintenance per instance (OS, HANA)WeaknessesPerformance impactVirtualization overhead
40 Landscape Deployment Planning One database schema per databaseSeparate virtual machine and OSSeparate SAP HANA databases per SAP systemShared hardware and storageCurrently supports VMware vSphere 5.1Usage ScenariosNon-production systemsSingle-node SAP HANA databases up to 1 TBSee SAP note
41 Multiple Components One System (MCOS) Share hardware for HANA among multiple Suite system to reduce TCO1 x Appliancen x HANA DBn x DB Scheman x ApplicationsStrengthsOnly one HANA system and one OS requiredHANA software can be individually maintained per DB instanceDedicated memory assignment per instanceWeaknessesShared HANA hardware – risk of performance issues since no dedicated CPUassignment per instanceNo separate Service Level Agreements on database levelSAP currently does not support MCOS configuration on a production system (note ).
42 Multiple Components One Database (MCOD) Provides the ability to install several components independently on a single database.1 x Appliance1 x HANA DBn x DB Scheman x ApplicationsStrengthsVersatility through components and only one HANA instance necessaryCross schema reporting supported and separate upgrades possibleDifferent operating systems and databasesHighest scalability possibleWeaknessesMaintaining different operating systems and databasesShared HANA software version and maintenance processesRisk of performance issues - lack of resource management capabilitiesComplex high availability solutionsSynchronizing backup and restore
43 Multiple Components One Database (MCOD) Multiple database schemas per databaseShared SAP HANA databaseDedicated application servers per applicationShared hardware, OS and storage poolUsage ScenariosNon-production systemsProduction systems for applications on whitelists and custom data martsNot multiple BW production systemsSee SAP notes:– HANA MCOD scenario whitelist– SoH MCOD scenario whitelist– BW specific considerations
44 Classical Technical Co-Deployment Appliance approach for optimal performance.No additional system required and a reduction of operations effortCross application reporting possible1 x Appliance1 x HANA DB1 x DB Schema1 x Application (e.g. ERP, CRM, or BW)StrengthsCoordinated start-stop functionalityReduced operation exertion for DB/OS/Backup/BasisMultiple application servers can be sharedSimplified application landscape setup, deployment, and maintenanceOption to scale out into separate deploymentReduced TCO on application levelWeaknessesRestrictive enhancement package dependenciesApplication specific middleware (CIF, BDOC) still being used. Not yet available for CRM.
45 Landscape Deployment Planning Classical Technical Co-DeploymentOne SAP HANA database and one database schemaOne AS ABAP application server/SIDAvailable for SRM and SCM as ERP add-onUsage ScenariosProduction and non-production systemsCan be combined with Virtualization or MCOS
46 What We’ll Cover Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsHardware TrendsLandscape Deployment PlanningBackupHigh AvailabilityWrap-up
47 BackupSupports synchronous backup between production system and backup storageAlerts can be setup to monitor whether backups are being done as expectedTwo primary methods of backing up:Traditional FileBACKINT API for third party vendors
48 BackupThere are 4 basepath options for traditional file backups in HANABasepath data backup – Standard backups to external mount pointBasepath data volumes – Permanent location for data volumesBasepath log backup – External mount point for logs segment to be copiedBasepath log volumes – Permanent location for log volumesIBM offers a backup management solution called Tivoli Storage ManagerSAP provides a script in SAP Note to help clean up log filesMany backup features are now automated including removal of log segments after backupThese basepath options are available in the Configuration tab in HANA Studio
49 Standby Systems and Backup Monitoring It is possible to keep a “warm” standby system that is ready to come online in the event of a failureHosts can also be on standby in the event of host issuesHANA includes a service auto-start that restarts any service that may failAlerts can be set to monitorIf the backups are being successfulinside the admin console under theAlerts tabStandby host can provide fault-tolerance recovery
50 What We’ll Cover Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsHardware TrendsLandscape Deployment PlanningBackupHigh AvailabilityWrap-up
51 High Availability (HA) SAP HANA supports HA and recovery measures rangingfrom faults and software errors, to disasters that decommission an entire data centerHA can be achieved by eliminating single points of failure (fault tolerance)Providing the ability to rapidly resume operations after a system outage with minimal business loss (fault resilience).The SAP HANA database provides several features in support of high availability, one of which is service auto-restartIn the event of a failure or an intentional intervention by an administrator that disables one of the SAP HANA services, the SAP HANA service auto-restart function automatically detects the failure and restarts the stopped service processThe number of standby servers defined during installation cannot subsequently be reduced. Standby servers can be added after installation.
52 High AvailabilityAdditional SAP HANA appliances used in standby mode for failoverCapability to assign up to three master servers as the name server (one is selected as the active server)Active server assigned master index serverIf active master name server fails, the systems restores itself to available standby masterHigh Availability is a set of techniques, engineering practices and design principles for Business Continuity
53 Scale out – High Availability High Availability ConfigurationN active servers in one clusterM standby server(s) in one clusterShared file system for all serversFailoverServer X failsServer N+1 reads indexes from shared storage and connects to logical connection of server XSource: SAP AG 2014SAP HANA cold standby hostStandby host is kept ready for the event that a failover situation occurs during production operationStandby host is not used for database processingAll the database processes run on the standby host, but they are idle and do not allow SQL connectionsSource: SAP AG 2014
54 What We’ll Cover Hardware Sizing, Planning, and The Cloud Top 10 Lessons Learned from SAP HANA ImplementationsHardware TrendsLandscape Deployment PlanningBackupHigh AvailabilityWrap-up
55 7 Key Points to Take HomeThere are programs to do pre-readiness checks for an ERP and BW system for migration to HANAA BW Migration Cockpit is now available to assist in the tasksWhile one is more common, there are actually four possible approaches to the HANA migration projectThere are currently seven different certified HANA vendors and many options for small, medium, and large systems — Make sure you get a competitive bidBudgeting should include HANA training and system cleanup, as well as support staff required or reorganizedMost HANA projects can be done in a matter of weeksOnly extremely large systems may require 4-7 months
56 Where to Find More Information https://www.sap-press.com/sap-hana_3687Dr. Bjarne Berg and Penny Silvia, SAP HANA: An Introduction (3rd edition) SAP PRESS, 2014).SAP’s main page for all SAP HANA-related informationSAP HANA demosSAP NetWeaver BW Powered by SAP HANA Community
58 DisclaimerSAP, R/3, mySAP, mySAP.com, SAP NetWeaver®, Duet®, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP.
Your consent to our cookies if you continue to use this website.