Upload
phamdung
View
222
Download
3
Embed Size (px)
Citation preview
Produced by Wellesley Information Services, LLC, publisher of SAPinsider. © 2015 Wellesley Information Services. All rights reserved.
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 servers
• How the SAP HANA database uses persistent storage to provide a fallback, and how fault tolerance, disaster recovery and high-availability can be set up for your SAP HANA implementation
3
Introduction – Dr. Berg
4
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
5
Hardware Options Sept 2015 Onward
6
Example: IBM 3850 X6
7
Hardware Options Sept 2015 Onward
These systems are based on Intel’s E7 IvyBridge processors with 15 cores per processor, or the newer Hartswell processors with 18 cores.
Scale-out
Scale-up
Business Suite
bullion S2 512-1536 GB 2 x 8890v3 x 2.5 Ghz x xbullion S4 1024-3072 GB 4 x 8890v3 x 2.5 Ghz x xbullion S8 2048-6144 GB 8 x 8890v3 x 2.5 Ghz x x
UCS B260 M4 512-1536 GB 2 x 4890v2 x x x xUCS B460 M4 1024 GB 4 x 4890v2 x 2.8 GHz xUCS C460 M4 128-3072 GB 4 x 8890v3 x 2.5 Ghz x x xUCS C880 M4 2048-6144GB 8 x 8890v2 x 2.8 Ghz x x x
Dell PowerEdge R930 128-3072 GB 4 x 8890v3 x 2.5 Ghz x x
PQ 2400 E/S/L 128-1024 GB 4 x 8890v3 x 2.5 Ghz x xPQ 2800B2/E2 128-6144 GB 8 x 8890v3 x 2.5 Ghz x xRX4770 M2 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x
CS-500 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x xCS-900 1024-12288 GB 8 x 2890v2 x 2.8 GHz x x x
Hitachi CB520X B2 256-6144 GB 8 x 8880v3 x 2.3 Ghz x x x
FusionCube E9000 512-1024 GB 4 x 4890v2 x 2.8 GHz xRH5885H V3 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x xRH8100 V3 128-6144 GB 8 x 8880v2 x 2.5 Ghz x x x
Flex x880 X6 128-6144 GB 8 x 8890v2 x 2.8 Ghz x x xx3850 X6 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x xx3950 X6 512-6144 GB 8 x 8880v3 x 2.3 Ghz x x x
NEC Exp. 5800/A2040b 128-2048 GB 4 x 4890v2 x 2.8 GHz x x
Silicon Graphics UV 300H 256-6144 GB 8 x 8890v2 x 2.8 Ghz x xUnisys Forward! 4150-B 128-3072 GB 4 x 4880v2 x 2.5 GHz x x
Target usage
HP
Huawei
Lenovo
Vendor System Memory(RAM)
Bull SAS
Cisco
Fujitsu
CPUIntel Ivy Bridge EX E7 15 Cores
(2014)
Max Number and Type
CPU Speed
Intel Haswell EX E7 18 Cores
(2015)
8
Cloud Options
9
Support Packages
• SAP has introduced the idea of “production verified revisions” to provide in-depth testing of all service packs for SAP HANA
• Based on the planned releases over the next months, customers should adjust their plans for service packs accordingly
Source: SAP SE
10
Sizing Overview
• There are several sizing options depending on the software components: BW system for HANA
QuickSizer – New implementation only, not migrations BW Automated Sizing Tool in the Migration Cockpit Rule of Thumb T-Shirt Sizing
Business Suite system for HANA QuickSizer for Business Suite on HANA Automated Sizing Tool Vendor Tools
Standalone HANA System
11
SAP QuickSizer for HANA
There are three versions of the tool for each version of SAP HANA
SAP’s QuickSizer for SAP HANA is available at: http://service.sap.com/quicksizer. * Requires login credentials to the SAP Service Marketplace.
The 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)
The second QuickSizer version is for SAP HANA on SAP BW
The QuickSizer for the Business Suite allows you to size for specific modules
12
If you’re using planning in SAP 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.
SAP QuickSizer for New BW HANA Implementations
13
SAP QuickSizer for New BW HANA Implementations (cont.)
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.
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.
14
This SAP HANA sizing example calls for 1.6TB of memory
SAP QuickSizer for BW on HANA — Output
In this case, SAP HANA for BW will deploy the master data, ABAP system tables, and most row store data on the master node. The other connected Index server node(s) will contain the InfoCubes and DSOs.
15
HANA Sizing Tool for Existing BW Implementations
Using the BW Automated Sizing tool in the Migration Cockpit
16
HANA Sizing Tool for Existing BW Implementations
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 databases, 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
To increase speed, you can suppress analysis tables with less than 1 MB size
With 8 parallel processors and 10TB database, it is not unusual to see 4-5 hours runtime
17
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.
This program is referenced in SAP Notes 1909597 and 1736976 on the Service Marketplace
The output is stored in the file you specified and the file can now be emailed to hardware vendors for sizing input and hardware selection
18
Sizing for Business Suite on HANASAP has also created a similar program for sizing HANA for Business Suite:
This should be used for all HANA migration projects of ECC to Business Suite
19
Sizing for Business Suite on HANA (cont.)Some vendors have also created their own sizing programs, which also include hardware prices
20
QuickSizer for Business Suite on HANA
For New BusinessSuite implementations you can use QuickSizer and send the results to SAP for further processing
21
QuickSizer for Business Suite on HANA (cont.)
This is the input screen where you enter the number of expected transactions by module. You are also asked to enter estimated changes and new records as well as operating times of your system.
Here you get the size in SAPS, as well as memory and disk requirements
22
Sizing a Standalone HANA System — Output
This is the input screen
Here you get the size in SAPS, as well as memory and disk requirements
23
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 1637145 to get row and column store sizes for your system
• The 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 Compression
Remember, these are quick rules of thumb, so don’t rely on it for finalized budgeting and hardware purchases
24
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 Memory
Remember, these are quick rules of thumb, so don’t rely on it for finalized budgeting and hardware purchases
25
Rule-of-Thumb Approach to Sizing BW on HANA — CPU
• The CPUs are based on the number of cores that you include. For example, 18 core CPUs now exist (depending on when you bought your system).
• If you have a single node with 8 x 18 cores, you will have 144 cores and can handle 720 active BW users on that hardware node, and quite a larger number of named users.
CPU = 0.2 CPU cores per active user
26
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 like
While very inaccurate for sizing, it provides basic information for those just starting to consider SAP HANA
Data -Compression (from)
Working Memory
Processors SAS/SSD (for data)
Replication Speed (per hour)
Extra Large (XXL)
7000–-100,000 GB
3072 GB
to 20+ TB
(multi node)
12+ Intel E7 2.4 Ghz
10+ TB 20+ GB
Very Large (XL)
3500–-7000GB
2048 GB
(multi node)
8+ Intel E7 2.4 Ghz
5 – 10 TB 20+ GB
Large (L) 2000–-3500GB
1024GB 4 x Intel E7 2.4 Ghz
4 - 5 TB 5–20GB
Medium (M)
1250–2000GB
512GB 4 x Intel E7 2.0+ Ghz
2048GB 5–20 GB
Small (S) 500–1250GB
256GB 2 x Intel E7 2.0+ Ghz
1024GB 5GB
Extra Small (XS)
256–500GB
128GB 2 x Intel E7 2.0+ Ghz
1024GB 5GB
The number of processors are largely driven by the number of
users and usage patterns. Serious consideration should be made before buying hardware.
27
Summary of HANA Sizing Approaches
• Work with your preferred vendor before ordering your hardware or finalizing your budgets
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/Low
SAP Note 1736976 (ABAP report to help with BW on HANA Sizing) SAP Note 1909597 (SAP BW Migration Cockpit for SAP HANA) SAP Note 1729988 (SAP BW Checklist for Migration)SAP Note 11855041 (Sizing the Master node)
28
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
29
1. Buy Hardware Early
1. The typical lead time for basic HANA appliances is as little as 4-8 weeks
2. However, for large scale environments, or multi-node environments, the lead times can sometimes be as long as 10-14 weeks
3. This is particularly true for virtualized systems managed by a third-party who has to set them up, configure backup and learn the new technology
Get 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
30
2. Get the Right Team Members
1. While there are many with basic certifications in HANA, the pool of qualified experienced resources is limited
2. Great HANA resources are most likely working on another project already
3. So, if you want the best, be prepared to give your implementation partner several weeks lead time
Do 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.
31
3. Include Training for Your Staff
1. There are a lot of “myths” and beliefs about HANA that you have to address early
2. Before you start the project, make sure your implementation partner has a formal written training plan on how they will provide knowledge transfer
3. Include your support staff and Basis people in all project discussions from the first planning session
Many 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.
32
4. Hardware Sizing Should Include Growth
1. Some customers forget that sizing would be for 3 years out and not based on current system size alone
2. You should have a sizing estimate that includes new projects, data growth and data retention policies, as well as periodic scheduled clean up activities
Funding 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
33
5. “Master-Node” Size for Scaleout BW on HANA
1. 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.
2. The drawback is that most of your row data and master data 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.
34
6. Create an Ecosystem of Experts
1. Having access to the best and brightest within SAP, consulting firms, and industry experts is key when issues or questions arise
2. These 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.
35
7. Think BIG
1. A HANA implementation should not be treated as a replacement project. It is an enabler …
2. 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 …
36
8. Plan for Reporting and System Consolidation
1. After go-live you should have planned for how you 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 vision
2. You will most likely have to do some “selling” to your fellow employees and be prepared to give them “free access” to your HANA system
HANA 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.
37
9. Near-Line Storage Can Save Millions
1. Removing data that is not needed on a daily basis from your system and placing it on near-line storage (NLS) instead of in-memory can save you millions
2. In one project a customer took his system from 112TB to 38TB by simply moving data to near-line storage.
3. An Asian firm took a 3.8TB BW system to “only” 900GB after cleanup and an NLS implementation.
There are many NLS solutions available that can save you lots of money 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.
38
10. Save Money with MCOD and MCOS
1. You may not need separate hardware for sandbox and development environments
2. Using Multiple Components One Database (MCOD) and/or Multiple Components One System (MCOS) you can simplify the number of hardware environments you needa) SAP BW on SAP HANAb) SAP Finance and Controlling Accelerator for the material ledgerc) ERP operational reporting with SAP HANAd) SAP Finance and Controlling Accelerator: Production Cost Planninge) SAP Rapid Martsf) SAP COPA Acceleratorg) SAP Operational Process Intelligenceh) SAP Cash Forecastingi) SAP Application Accelerator/Suite Acceleratorj) Smart Meter Analytics
In addition to custom developed datamarts, all items above can run in an MCOD setup (see SAP Note 1666670 for more details)
39
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
40
Landscape Deployment Planning
Virtualization MCOS MCOD Technical Co-Deployment
DeploymentScenario
HANA DBs Multiple Multiple One One
DB Schema Multiple Multiple Multiple One
Availability Supported for DEV & QA systems
Supported for DEV & QA systems
Defined by:White List 1661202 for BW
White List 1826100 for Suite
Business Suite components SCM and/or SCM co-deployed with
ERP
Source: SAP SE 2015
41
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 Appliances• n x HANA DB• n x DB Schema• n x Applications
Strengths• Only one HANA system needed• Resource mgmt per virtual instance possible (RAM, CPU, Storage)• Easy scalability• Different Server Level Agreements per virtual machine possible• Independent deployment and maintenance per instance (OS, HANA)
Weaknesses• Performance impact• Virtualization overhead
Source: SAP SE
42
Landscape Deployment Planning
• One database schema per database• Separate virtual machine and OS• Separate SAP HANA databases per SAP system• Shared hardware and storage• Currently supports VMware 5.5 and higher
• Usage Scenarios Non-production systems Single-node SAP HANA databases up to 1TB
See SAP Note 1788665
43
Multiple Components One System (MCOS)
• Share hardware for HANA among multiple Suite system to reduce TCO 1 x Appliance n x HANA DB n x DB Schema n x Applications
• Strengths Only one HANA system and one OS required HANA software can be individually maintained per DB instance Dedicated memory assignment per instance
• Weaknesses Shared HANA hardware – Risk of performance issues since no dedicated CPU assignment per instance No separate Service Level Agreements on database level
SAP currently does not support MCOS configuration on a production system (SAP Note 1681092)
Source: SAP SE 2015
Source: SAP SE
44
Multiple Components One Database (MCOD)
• Provides the ability to install several components independently on a single database 1 x Appliance 1 x HANA DB n x DB Schema n x Applications
• Strengths Versatility through components and only one HANA instance necessary Cross-schema reporting supported and separate upgrades possible Different operating systems and databases Highest scalability possible
• Weaknesses Maintaining different operating systems and databases Shared HANA software version and maintenance processes Risk of performance issues – Lack of resource management capabilities Complex high availability solutions Synchronizing backup and restore
Source: SAP SE 2015
Source: SAP SE 2015
See SAP Notes: 1661202 – HANA MCOD scenario whitelist1826100 – SoH MCOD scenario whitelist1666670 – BW specific considerations
45
Classical Technical Co-Deployment• Appliance approach for optimal performance
No additional system required and a reduction of operations effort Cross-application reporting possible
1 x Appliance 1 x HANA DB 1 x DB Schema 1 x Application (e.g., ERP, CRM, or BW)
• Strengths• Coordinated start-stop functionality• Reduced operation exertion for DB/OS/Backup/Basis• Multiple application servers can be shared• Simplified application landscape setup, deployment and maintenance• Option to scale out into separate deployment• Reduced TCO on application level
• Weaknesses• Restrictive enhancement package dependencies Source: SAP SE 2015
Source: SAP SE 2015
46
Landscape Deployment Planning- BusinessSuite on HANA
• Classical Technical Co-Deployment One SAP HANA database and one database
schema One AS ABAP application server/SID Available for SRM and SCM as ERP add-on
• Usage Scenarios Production and non-production systems Can be combined with Virtualization or MCOS
47
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
48
Backup
• Supports synchronous backup between production system and backup storage• Alerts can be setup to monitor whether backups are being done as expected• Two primary methods of backing up:
Traditional File BACKINT API for third-party vendors
49
Backup (cont.)
• There are 4 basepath options for traditional file backups in HANA Basepath data backup – Standard backups to external mount point Basepath data volumes – Permanent location for data volumes Basepath log backup – External mount point for logs segment to be copied Basepath log volumes – Permanent location for log volumes
• IBM offers a backup management solution called Tivoli Storage Manager
• SAP provides a script in SAP Note 1651055 to help clean up log files
• Many backup features are now automated including removal of log segments after backup
These basepath options are available in the Configuration tab in HANA Studio
Source: SAP SE 2015
50
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 failure
• Hosts can also be on standby in the event of host issues• HANA includes a service auto-start that restarts any service that may fail
Alerts can be set to monitor to see if the backups are being successful inside the admin console under the Alerts tab
51
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
52
High Availability (HA)• SAP HANA supports HA and recovery measures ranging from faults and software errors to disasters that decommission an entire data center• HA 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 basically a service auto-restart• In 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 process
High Availability is a set of techniques, engineering practices and design principles for Business Continuity
53
High Availability (HA) (cont.)
• Additional SAP HANA appliances used in standby mode for failover
• You have the capability to assign up to three master servers as the name server (one is selected as the active server)
• Active server assigned master index server
• If active master name server fails, the systems restores itself to available standby master
The number of standby servers defined during installation cannot subsequently be reduced, but standby servers can be added after installation
54
Scale Out — High Availability
• High Availability Configuration N active servers in one cluster M standby server(s) in one cluster Shared file system for all servers
• Failover• Server X fails• Server N+1 reads indexes from shared storage and
connects to logical connection of server X• SAP HANA cold standby host
• Standby host is kept ready for the event that a failover situation occurs during production operation
• Standby host is not used for database processing• All the database processes run on the standby host, but
they are idle and do not allow SQL connections
Source: SAP SE 2015
Source: SAP SE 2015
55
What We’ll Cover
• Hardware sizing, planning and the cloud• Top 10 lessons learned from SAP HANA implementations• Landscape deployment planning• Backup • High availability• Wrap-up
56
Where to Find More Information
• www.sap-press.com/sap-hana_3687 Bjarne Berg and Penny Silvia, SAP HANA: An Introduction (3rd edition, SAP PRESS –
English and German Editions).• www.saphana.com/welcome
SAP’s main page for all SAP HANA-related information• www.saphana.com/community/try
SAP HANA demos
• http://scn.sap.com/community/bw-hana
SAP BW Powered by SAP HANA Community
57
7 Key Points to Take Home
• There are programs to do pre-readiness checks for an ERP and BW system for migration to HANA
• A BW Migration Cockpit is now available to assist in the tasks• While one is more common, there are actually four possible approaches to the HANA
migration project• There are currently seven different certified HANA vendors and many options for small,
medium, and large systems — Make sure you get a competitive bid• Budgeting should include HANA training and system cleanup, as well as support staff
required or reorganized• Most HANA projects can be done in a matter of weeks• Only extremely large systems may require 4-7 months
58
Your Turn!
How to contact me:Dr. Bjarne Berg
Please remember to complete your session evaluation
59
Disclaimer
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP SE.