1. No category

SAP HANA Sizing
HP Partner Training
Cindy Walker / April 14-15, 2015
Hardware Sizing
TRANSLATING BUSINESS REQUIREMENTS
INTO
HARDWARE REQUIREMENTS
Traditional SAP sizing approaches focus on CPU performance (SAPS).
SAP HANA sizing approaches focus on memory.
2
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SAP HANA Sizing Types
Initial Sizing vs. Delta Sizing
SAP distinguishes between two types of sizing:
• Initial Sizing – Greenfield / New Implementation
• Delta Sizing - Migration
With an initial sizing, the sizing is being done from scratch for the first time for a
completely new installation of SAP software.
With a delta sizing, there is a productive SAP solution already running and the
sizing is being performed for new functionality or a migration to a new database,
for instance.
3
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SAP HANA Sizing
Initial Sizing – Greenfield / New Implementation
If you do not have a
NetWeaver-based system,
SAP’s free web-based
Quick Sizer (QS) tool can
be used to initially calculate
sizing requirements for SAP
HANA based on
transactional data input.
SAP QS is accessible at the
following URL:
service.sap.com/quicksizer.
Delta Sizing – Migration
Database-specific scripts, ABAP reports and
SAP Notes provided by SAP.
4
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SAP HANA Sizing - Overview
High-level overview
Source: Sizing Approaches for SAP HANA, Version 2.0, November, 2014, page 4.
Please see the following SAP notes for additional sizing information…
HANA Side-by-Side Sizing
• DB-specific scripts on SAP Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database
BW on HANA
• DB-specific scripts provided on SAP Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database
Describes how to use DB scripts in case the recommended ABAP report described in SAP Note 1736976 cannot be
used.
5
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Sizing BW on HANA (BWoH)
Initial or Delta
Source: Sizing Approaches for SAP HANA, Version 2.0, November, 2014, page 4.
Initial (Greenfield / New Implementation)
• SAP Quick Sizer
Enables you to specify the size of InfoCubes and Data Store Objects, along with average and peak load times, user groups, data
upload information, and row and column footprints and compression, for example.
Delta (Migration)
• Implement ABAP report from SAP Note 1736976.
The SAP note includes background information and documentation for how to run the report.
• DB-specific scripts provided on SAP Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database
Describes how to use DB scripts in case the recommended ABAP report described in SAP Note 1736976 cannot be used.
6
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BWoH Sizing Report Example
Sizing Report for BW on HANA
7
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BWoH Quick Sizer Example
8
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BWoH Sizing Update
PDF from SAP note 1736976 - Sizing Report for BW on HANA
Source: Attachment to SAP Note 1736976 Ver. 71 - SAP_BW_on_HANA_Sizing_V2_1.pdf, page 29.
9
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Alternative – Manual SAP BWoH calculations
SAP Note 1637145
10
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Alternative – Manual SAP BWoH calculations
Example
Variables
Source data footprint (GB)
Approx. data amount for part of DB tables stored in
row store (all tables NOT generated by BW) in
cleansed BW system (GB)
9,000
60
Working memory factor
2
Average compression factor = 4:1
database table size:column store size
Note: This compression factor refers to uncompressed
database tables; Space for database indexes excluded.
4
1)
Formula:
(Source data footprint - 60GB) * 2 / 4 * c1) + 110GB
(Source data footprint - 60GB)
8,940
(Source data footprint - 60GB) * 2
17,880
(Source data footprint - 60GB) * 2 / 4
4,470
(Source data footprint - 60GB) * 2 / 4 * c1)
4,470
c = source database specific compression factor
1
(where applicable – see page 8)
1 if no compr factor used
Compression in source database
The sizing scripts attached to note 1637145 do NOT take into account reduced sizes of the source data due to database intrinsic
compression – except the ones for the IBM DB2 family (DB2, DB4, DB6), where compression factors for each table are contained
in the database dictionary. These scripts deliver correct results also for a compressed database.
If the source database other than from the DB2 family is compressed, you have to adjust the results of the scripts by a database
compression factor. Your DB administrator should be able to help obtaining this factor.
(Source data footprint - 60GB) * 2 / 4 * c1) + 110GB
Sum of memory not covered by column store (GB)
110
4,580
10% Unicode uplift (if required)
11
1.1
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
5,038
Housekeeping
SAP BW
It is very beneficial to make sure the BW system is cleaned up before the migration and corresponding house keeping
tasks are executed frequently. More information about clean-up / housekeeping tasks can be found here:
https://scn.sap.com/docs/DOC-59763.
SAP note 1829728 v22 - BW Housekeeping Task List_30.01.2015
It generates a task list with several common tasks associated with housekeeping/upkeeping an BW system.
General SAP Recommendations:
Intensify housekeeping (e.g. by using SAP Note 1829728 - BW Housekeeping Task List): focus on the RS and CS tables
on the master node.
Migrate to HANA
Move some large CS tables from the master node to the slave node, in order to have sufficient free space on the master
node”
12
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Sizing for Suite on HANA (SoH)
Initial or Delta
Source: Sizing Approaches for SAP HANA, Version 2.0, November, 2014, page 4.
Initial (Greenfield / New Implementation)
• SAP Quick Sizer
• Follow the guidelines provided in SAP Note 1793345.
Delta (Migration)
• Implement ABAP report from SAP Note 1872170.
The SAP note includes background information and documentation for how to run the report.
13
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SoH Sizing Report Example
SAP Note 1872170
As
•
•
•
•
•
14
Added to this workspace
is the “Hybrid LOB
stored on disk”. Large
Objects (LOBs) are often
found in suite systems
and are, for example,
attachments, such as a
long text in a workflow
item.
of SAP HANA SP7, LOBs > 1000 bytes:
not stored in memory (by default) - only on disk
reference marker to LOB kept in memory
Only 20% of LOB records cached in memory
The sizing report allows for what-if analyses, in case you want to cache more LOBs in memory.
Neither LOB cache nor the space for “code, stack and other services” are doubled.
Results always displayed in GB.
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SoH Quick Sizer Example
15
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Alternative – Manual SAP SoH calculations
SAP Note 1793345 - Quick and easy approach
Assume source system is well-maintained and uncompressed
SAP recommendation:
• Take half of size of your disk-based database
• Include a safety buffer of 20%
• Add 50 GB fixed size for code, stack and other services
Example: 2,000 GB DB (tables plus indexes) will require 1,250 GB
2,000 GB/2 * 1.2 + 50 GB
Don’t forget to consider future data growth…
Add 20% memory resources on top if using SAP HANA Enterprise Search.
16
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Alternative – Manual SAP SoH calculations
Example with growth
17
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Sizing for SAP HANA Side-by-Side (Side-car)
SAP HANA Accelerator
SAP HANA Accelerators are pre-defined scenarios that are placed next to existing SAP solutions to
speed them up. Therefore, the Accelerator replicates data into SAP HANA and enables any subsequent
read operation to be routed to the SAP HANA environment instead of the original source database. All
business logic and write operations still operate in the classic way. This procedure helps to speed up
business processes where the read-operation is a bottleneck. As the SAP HANA Accelerator is placed
as a sidecar, this sped-up process can be delivered without a huge change to the original system and a
long project. Implementation time, effort and connected risks are minimal.
• DB-specific scripts on SAP Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database
• Enter output from script in SAP Quick Sizer
‒ Concurrent users (optional)
‒ Source DB footprint in GB
‒ Compression factor
• Average compression factor database table size: HANA memory = 7:1
• Factor in Unicode conversion (if applicable) and current average DB compression
• Factor in future data growth
18
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Don’t forget the completer systems, per landscape
Real-time source system: SLT
server(s)
• Linux/MS-Win64
ERP, CRM,…
users
Data source
systems (Side-car)
SAP ERP, SAP
CRM, etc…
• Estimated start configuration:
DL360/BL460 with 2x top-bin QC
processors, 48 GB RAM, 2x 300 GB
HDD
SBOP
• BI platform
• Explorer
• WebApp server
SBOP BI servers
• Size with SAP Quick Sizer
OR
• Customer may use existing BI 4.0
servers
• Could run on a virtual machine –
4vCPU, 32 GB, 100 GB
BW servers (if BW/SAP HANA)
• BW CS (ASCS, SCS, ERS),
• BW APP, BW JAVA database
• Could run on existing NW7.02 SAP
system
• Size with SAP Quick sizer
OR
• Add second server and failover
clustering if SLA dictates
Business Suite on HANA (SoH)
• ECC /CRM/SCM App Servers
• Size with QS in future
- OR SBOP Data Services 4.0
Non-SAP
System(s)
Batch source system: SBOP DS Server(s)
• Similar to SLT server(s)
SAP HANA database
19
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SAP HANA Deployment
Options
20
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
SAP HANA Hardware Deployment Options
Appliance
Supported for
Prod and
Hardware
Deploymentnon-Prod
Options
TDI
Cost Optimized
Prod and
non-Prod
Non-Production only
(non-performance critical)
Solution components
Single-Vendor
Multi-vendor
Multi-vendor
Server requirements
Must be HANA certified
Must be HANA certified
Must be HANA certified
Memory requirements
Must follow SAP RAM/processor
ratios for each use case
Must follow SAP RAM/processor
ratios for each use case
Can exceed SAP RAM/processor
ratios for each use case
Processor options
Only HANA certified processors
Only HANA certified processors
Flexible processor options
Storage requirements
Must be HANA certified
Must be HANA TDI certified
Can use any storage
Certification
Pre-engineered,
pre-certified
Custom certification
required onsite
No certification required
Implementation
Factory integrated, quick
deployment, packaged service
Several weeks or months
depending on the size, custom
SOW
Several weeks or months
depending on the size, custom
SOW
Support
Integrated SAP appliance support
Faster resolution
HW break-fix
Multi-vendor
HW break-fix
Multi-vendor
21
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Certified SAP HANA® Hardware Directory
• Certified Appliances
http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html#=true
• TDI
‒ Certified Enterprise Storage: http://global.sap.com/community/ebook/2014-09-02-hanahardware/enEN/enterprise-storage.html
‒ Supported Entry-Level Systems (E5 TDI): http://global.sap.com/community/ebook/2014-09-02-hanahardware/enEN/entry-level-systems.html
22
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HANA Technical Deployment Options (up to SPS8)
Classical
Technical
Co-deployment
MCOD “Multiple Components
on one Database”
MCOS “Multiple
Components on one
System”
a.k.a. Multi-SID
Virtualization
HANA DBs
One
One
One
Multiple
Multiple
DB Schema
One
One
Multiple
Multiple
Multiple
SAP application
One
One + 1 Add-on
Multiple
Multiple
Multiple
Supported for
Production
Yes
SCM or SRM co-deployed
with SoH (Add-on)
Not yet for CRM
Defined by White List:
BW: Note 1661202
SoH: Note 1826100
No ,
Non-prod only
(Note 1681092)
Only 1 VM per Host for
Production operations
(Note 1788665),
> 1 VM for NPRD,
CA > 1VM for PRD
Scenario
Source: SAP AG
23
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HP ConvergedSystem for SAP HANA
Built on Next Generation
Intel Ivy Bridge platform
Complete portfolio
CS 500
CS 900
General Purpose (OLAP)
Business Suite (OLTP)
32 to 96 TB
General Purpose (OLAP)
12 TB
6 TB
2 TB
256 GB
512 GB
1 TB
(SoH
only)
(2TB/node,
2 nodes/rack)
(SoH
only)
16 TB
(SoH
only)
(1TB/node,
4 nodes/rack)
Scale Up
- 2x 600GB 6G SAS 10K SFF (OS)
- 8x 600GB 6G SAS 10K
(logs+data)
- 2x 600GB 6G SAS 10K SFF
- 2x 800GB ME SSD (Logs)
- D2700 , 25x 600GB SAS (data)
Scale Out
- 8s(6TB) or 16s(12TB), 3PAR
7400, 96x 900GB SAS SFF
(logs/data) / rack
- 3PAR 7400, 96x 900GB SAS SFF (logs/data) / rack
End to End consulting and deployment services | Single point of contact for solution level support | Factory Integrated | Warranty
HP internal
24
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Scale-up vs Scale-out for SAP HANA
General SAP recommendations
Good argument for CS900 Scale-up
25
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Thank you!
26
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.