The document discusses topics related to designing and implementing an SAP HANA infrastructure, including the hardware and software components required for the SAP HANA server, storage, network, backup, and disaster recovery systems. It provides information on sizing SAP HANA systems, certified hardware partners, storage options like TDI, network requirements, security best practices, backup methods, and high availability and disaster recovery strategies. The presentation aims to help with planning and designing the various elements of an SAP HANA infrastructure.

2. DC Specialist, Cisco Systems
SAP HANA infrastructure
Jarut Nakaramaleerat
9-Dec-2016
http://bit.ly/2gfzVhg

3. สิ#งที#จะพูดคุยกันวันนี3
• 11.00 – 12.30
• การทํางานของ SAP HANA
• อุปกรณ์ที#ต ้องมี (หรือควรมี) สําหรับระบบ SAP HANA
• การออกแบบระบบ Server
• การออกแบบระบบ Storage
• การออกแบบระบบ Network
• การออกแบบระบบ Backup
• การออกแบบระบบ DR Site

4. SAP HANA 101

5. Instances of a SAP-System
Web Browser / Fiori
Server A Server CServer B
Central
Instance 00
Central Services
Instance 01
Dialog
Instance
02
Dialog
Instance
03
Server D DB

6. What is SAP HANA?
SAP HANA
•Stands for “SAP High Performance Analytic Appliance”
SAP Definition
•SAP HANA is a multipurpose, data source-agnostic in-memory appliance software that combines
SAP software components optimized on proven hardware and delivered by SAP’s leading hardware
partners.
•SAP in-memory computing technology accelerates access to data by storing databases in the main
memory of a computer.
•SAP HANA is a data platform developed by SAP. At the core of SAP HANA is a relational database,
which supports a wide range of Business Intelligence, ERP and other enterprise applications.

7. What is In-Memory Computing?
Source: SAP SE

8. Faster Access with a Column-Based Approach
• Data is stored vertically and serves as the index
• Columns are stored separately
• Retrieve only columns used in the query
• Reduces I/O dramatically
Results
• Data is stored horizontally
• Querying without indexes and views is I/O intensive
• Building indexes and views is time consuming
• Requires an expanded database footprint
Row-Based
1
2
3
5
… Column-Based
1 2 3 4 5 6 7 8 9 …
Results Results

9. What Makes SAP HANA So Fast?
Vs.
Transactions Reports
Database
ETL
Transactions Reports Spreadsheet
External
Resources
Persistent Storage
• Planning
• Modeling
• What-
if…
Business Intelligence

10. SAP HANA & SAP S4/HANA

11. S/4HANA = Next Gen Business Suite
HANA = Next Gen Platform

13. • SAP HANA appliance or TDI (server, storage, virtualization)
• Network Switch
• Security and Patching
• Backup & HA & DR
• Upgrade plan
อุปกรณ์ที#ต ้องมี (หรือควรมี) สําหรับระบบ SAP HANA

14. Server and Storage

15. SAP HANA Scalability
Scales from very small servers to very large clusters
Single Server
• 2 CPU 128GB to 8 CPU 8TB
(Special layout for Suite on HANA or
S/4HANA with up to 20TB+ per host)
• Single SAP HANA deployments for
data marts or accelerators with performance
demands (Socket to Memory ratio)
• Support for high availability
and disaster recovery
Scale Out Cluster
• 2 to n servers per cluster
• Each server is either 4 CPU/2TB or 8
CPU/4TB
• Largest certified configuration: 112 servers
• Largest tested configuration: 250+ servers
• Support for high availability
and disaster recovery
Cloud Deployment
• SAP HANA instances can be
deployed to public clouds
• BYOL
• Pay-per-use
12 PetaByte Data Warehouse with SAP HANA ð Guinness world record
OLTP/OLAP
OLAP only
OLTP/OLAP

16. defined
certified
defined
certified
SAP HANA Deployment Model
SAP HANA tailored data center integration is an additional option to the existing appliance delivery model
SAP HANA appliance delivery SAP HANA tailored data center integration
HANA
Server
HANA
Server
Storage
HANA
Server
Application
Database
Operating
System
Virtualization
Server
Network
Storage
Enterprise
Storage
HANA
Server
HANA
Server
HANA
Server
Shared Network
Virtualization
Server
Network
Storage

17. List of certified Hardware
http://global1.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html

18. HANA Appliance
HANA
Appliance
HANA
Appliance
HANA
Appliance
Pros
• Small footprint
• Individual boxes
Cons
• Silo
• Difficult to recover
HANA
Appliance

19. 16 x 4 TB C880 w/ TDI
16 x 2 TB B460/C460 w/ NTAP TDI
16 x 2 TB B460/C460 w/ EMC TDI
SAP HANA Certified Solution Portfolio
768 GB 1.5 TB 3 TB
768 GB B260
2 TB C460
4 TB C880 w/ JBOD
2 TB B260 w/ TDI
4 TB C460
4 TB B460 w/ TDI
8 TB C880 w/ JBOD
2 TB B460 w/ TDI
AnalyticsSoH
32 TB6 TB 24 TB
16 x 2 TB C460 w/ C240M4 and MapR

20. HANA TDI Storage
Pros
• Advance Data
Management
• Simplified architecture
Cons
• Initial investment
• Need to meet SAP KPIEnterprise
Storage
HANA Appliance

21. HANA TDI Virtualization
Pros
• Virtualization & Mobility
• Easy to move to cloud
Cons
• Beware the overhead
• Limit max capacity
Enterprise
Storage
VMware vSphere
vHANA vHANA vHANA vHANA

22. Hyperconverged Infra for SAP HANA?
Certified Solution by using HCI for SAP app tier
And HANA appliance
Non-production only
(For Production is in review)
Fully Virtualized HCI with SAP HANA
http://www.cisco.com/c/dam/en/us/products/collateral/hyperconverged-infrastructure/hyperflex-hx-series/white_paper_c11-738214.pdf

23. Software Defined Storage as HANA TDI
`
CVD
• UCS Managed
• 40G network
• Scalable C240 storage
• 24x 1.8T HDD
• RHEL or SLES
• MapR Data Platform
• NFS attach storage
• Cert completed
• CVD in production
• Roadmaps in
development

24. 1) Determine the size of your future SAP HANA system
Ÿ SAP Quick Sizer tool is a quick and easy way for customers to
determine the CPU, memory, and SAPS requirements for running
their workloads on SAP HANA.
Ÿ Consider involving SAP Active Global Support for IT landscape
planning
2) Check the offerings of SAP‘s HANA Hardware Partners
Ÿ See the Certified SAP HANA Hardware Directory site
3) Order your SAP HANA server hardware
Ÿ If you decided to follow the TDI approach, please note:
o You do not need to order the local disks/integrated storage - these are
only required for appliances
o If you want your SAP HANA system to boot from SAN, additional Fibre
Channel adapters are allowed
4) Check the offerings of certified storage vendors
Ÿ Select one from the list of certified storage families
Ÿ If your preferred storage is not yet on the list, contact the vendor
on their plans to get certified
5) Set up your SAP HANA hardware infrastructure
Ÿ Make yourself familiar with SAP HANA’s IO patterns and the
impact of SAP’s data throughput KPIs during daily SAP HANA
operation
Ÿ Configure the storage system following the vendor’s directions
and recommendations
o Ask your storage vendor for a copy of their Configuration Guide for
SAP HANA
Ÿ Optional: Check the data throughput and the latency times
using HWCCT
o SAP’s KPIs are listed in the tool documentation
Ÿ Contact your storage vendor if the KPIs are not met
6) Install SAP HANA software
Ÿ Make sure that only certified personal do the SAP HANA
installation
Ÿ See SAP’s installation guides and related SAP notes at
help.sap.com
7) Go Live
Ÿ Consider involving SAP Active Global Support to perform a
HANA Go-Live Check prior to going productive
Going Live with SAP HANA TDI
High-level Process

25. All Applications – One Platform
SAP BW on HANA (PRD)
• 4+ Node Scale-out Cluster
SAP BW on HANA (PRD, virtual)
• Small scale-up HANA systems
SAP Suite on HANA (PRD)
• 2+ Node Scale-up HA Cluster
Non-SAP Applications
• VDI, SharePoint, Exchange, etc.
Storage Pools for HANA Persistence
Aggregation and Out-of-Band
Management for SAP
(Cisco Nexus and UCS Fabric)
Hadoop Cluster
SAP Applications (Non-PRD)
SAP Applications (PRD)
Shared Storage

26. Network Requirement

27. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0bf7501-
e4bd-3210-9e82-
c7e200e7943a?QuickLink=index&overridelayout=true&60125247183720

28. SAP HANA in Data Centers
Bandwidth considerations for System Replication
• SAP How-To Guide:
Network requirements for System Replication (Link)
• 1. “Throughput”: Out of practical reason it must be
possible to transport the size of the persistently stored
data within one day from the primary to the secondary.
• 2. “Latency”: In case of SYNC operation:
The redo log shipping wait time for 4 KB log buffers
must be less than a millisecond or in a low single-digit
millisecond range – depending on the application
requirements (relevant for synchronous replication only).
Baseline
Average bandwidth need
Time
Bandwidth
Peaks
Delta-Data continuous Log
Ÿ Example for a bandwidth calculation:
Given: 4.3 TB of persistently stored data (sum of
data backup file sizes).
Throughput: 4.3 TB per day ð ~ 50 MByte/s
ð ~0.5 GBit/s minimum connection required
ð More info with SAP HANA Network Requirement Paper or
ð SAP note 1969700 contains among others an SQL statement
(in zip archive attached) to estimate the average (per day)
bandwidth required for SAP HANA System Replication
depending on the data and log amount per day

29. Security

30. SAP HANA Security – data center integration
• User and role provisioning
• Out-of-the-box connector for
SAP NetWeaver Identity
Management
• SQL interface for integration
with other identity management
solutions)
• Compliance infrastructure
• Out-of-the-box connector for
SAP Access Control 10.1
• Standards-based single sign-on
infrastructure
• E.g. Microsoft Active Directory
• Logging infrastructure
• Database audit trail written via
Linux syslog
SecurityInfrastructure
Logging
Infrastructure syslog
Single Sign-On
Infrastructure
Kerberos
SAML
Identity
Management
Infrastructure
SQL
SAP HANA
Compliance
Infrastructure SQL
Antivirus
NW-VSI
compatible
XS

31. SAP HANA – security patching
• Operating systems
• SUSE Linux Enterprise and RedHat Enterprise Linux
• Security patches
• SAP HANA security patches are published as part of the SAP Security Patch strategy (SAP Security Notes)
• Delivered as SAP HANA revisions
• Operating system security patches are provided and published by SUSE/RedHat
• SAP HANA security documentation
• General information on SAP HANA security: SAP Help Portal
• Security whitepaper: http://www.saphana.com/docs/DOC-3751
• Best practice document on SAP HANA roles (incl. role templates): https://scn.sap.com/docs/DOC-53974
• Important SAP Notes
• 1598623: SAP HANA appliance: Security (Central Security Note)
• 1514967: SAP HANA appliance (Central Appliance Note)
• 1730929: Using external tools in an SAP HANA appliance
• 1730930: Using antivirus software in an SAP HANA appliance
• 1730999: Configuration changes in HANA appliance

32. Backup & HA & DR Requirement

33. SAP HANA Backup and Recovery
Options for backup: Comparison
File system Backint Storage snapshot
Advantages Ÿ Consistency checks on block level Ÿ Consistency checks on block level
Ÿ Ease of use – no explicit backup files management,
integrated into Studio
Ÿ Data center integration
Ÿ Additional features, e.g. encryption or de-duplication
Ÿ After completion, backups immediately available for
recovery
Ÿ Fast (usually seconds to minutes)
Ÿ Negligible network load
Ÿ First storage partners offer integration in their
tools
Disadvantages Ÿ Additional storage required
Ÿ File system fill level needs to be monitored
Ÿ Additional time needed to make backups
available for recovery
Ÿ Network load
Ÿ In case of recoveries, backup files must be
returned to staging area
Ÿ Network load
Ÿ 3rd party backup tool necessary
Ÿ No consistency checks on block level
Size Ÿ Payload only: Current data (backup size)
usually smaller than the data area)
Ÿ Payload only: Current data (backup size) usually
smaller than the data area)
Ÿ ~ Size data area, but usually compressed/de-
duplicated by storage
Duration Ÿ IO-bound (reading from data volume, writing
to target)
Ÿ Network-bound (writing to file system)
Ÿ IO-bound (reading from data volume)
Ÿ Network-bound (writing to backup server)
Ÿ Usually negligible (logical pointers are
replicated)

34. SAP HANA Backup and Recovery
Destinations for backups (I)
SAP HANA Database
Backup
Storage,
e.g. NFS
Create backup
hdbsql
SAP HANA
studio
• Backups to the file system
• Data backups can be triggered using
• SAP HANA Cockpit
• SAP HANA Studio
• SQL commands
• Scheduled with
• DBA Cockpit
• Standard scheduling tools
o starting SQL commands to initiate operations
• Log backups
• written automatically
• Triggered every 15 Minutes or by finished Log segment
• More information:
• File systems that are not supported: SAP Note 1820529
• Scheduling using the XS scheduler: SCN blog

35. SAP HANA Backup and Recovery
Destinations for backups (II)
Backups to 3rd party backup server
Ÿ For both data and log backups
Ÿ SAP HANA provides an API “Backint for SAP HANA” via
which 3rd party backup tools can be connected
Ÿ Provides functions for backup, recovery, query, delete
Ÿ 3rd party backup agent runs on the SAP HANA server,
communicating with 3rd party backup server
Ÿ Backups are transferred via pipe
Direct integration with SAP HANA:
Ÿ Data backups to Backint can be triggered/scheduled using
SAP HANA studio, SQL commands, or DBA Cockpit
Ÿ Log backups are automatically written to Backint (if
configured)
SAP HANA Database
3rd
Party
Backup Server
3rd
Party
Backup Agent
hdbsql
SAP HANA
studio
Create backup

36. SAP HANA Backup and Recovery
Backint Certification
• Certification is an installation prerequisite for tools using the “Backint for SAP HANA” API
• SAP Note 1730932 (“Using backup tools with Backint”)
• Certified tools (as of 2016-Jun)
Online listing of certified tools: Application Development Partner Directory
Ÿ Enter the search term HANA-BRINT and click on a partner name ð ”SAP Certified Solutions” for further details
Vendor Backup tool Intel
Arch.
Power
Arch.
Support
process
Allen Systems ASG-Time Navigator 4.4 ü 2212571
Commvault Simpana 10.0, Hitachi Data Protection Suite 10 (via Simpana Backint interface) ü 1957450
EMC Networker 8.2 ü 1999166
Interface for Data Domain Boost 1.0 ü 1970559
HP Data Protector 7.0, 8.1, 9.0; StoreOnce Plug-in for SAP HANA 1.0 ü 1970558
IBM Tivoli Storage Manager for Enterprise 6.4 ü 1913500
Spectrum Protect for Enterprise Resource Planning 7.1 ü 1913500
Libelle BusinessShadow 6.0.6 ü 2212575
Mindtree NBU CONNECTOR for SAP HANA ü 2330945
SEP Sesam 4.4 ü ü 2024234
Veritas (Symantec) NetBackup 7.7 ü 1913568
New
New
New
New

37. SAP HANA Backup and Recovery
Recovery steps when using a storage snapshot
1. Using the storage tool, transfer the
storage snapshot to the data area of the
SAP HANA database
2. Using SAP HANA studio, recover the
database using the storage snapshot as
basis (available in the recovery wizard)
Note: All recovery options are available,
including point-in-time recovery using log
backups/log from the log area
Note: All recovery options are available,
including point-in-time recovery using log
backups/log from the log area
hdbsql
SAP HANA
Studio
Recover database
Transfer storage
snapshot to
data area
SAP HANA Database
External
Storage
Data Area (Disk)
Data snapshot
Storage
Tool

38. HA & DR Concepts in general
RPO RTO
operation resumed…
time
Sync or
backup
…system operational
design & prepare detect recover perf. ramp
KPIs:
• Recovery Point Objective (RPO) = worst-case data-loss
• Recovery Time Objective (RTO) = time to recover from outage
*synchronous solution
Solution Used for Cost RPO RTO Perf. ramp
Backup & Recovery HA & DR $ high high med
SAP HANA Host Auto-Failover (Scale-out only) HA $ 0 med long
SAP HANA Storage Replication w/ QA, Dev. DR $$ 0* med long
SAP HANA System Replication HA & DR $$$ 0* low short
SAP HANA System Replication w/ QA, Dev. HA & DR $**/$$ 0* med long
** single host installations

39. System Replication
*Source: SAP website

40. System Replication Modes
*Source: SAP website

42. Worldwide Data Center Setups
Multi Tier System Replication – Cascading Systems
Production Local shadow
with data preload
Remote system/shadow
with or without preload
(mixed usage together with non-prod.
operation)
Data CenterData Center
Sync
Tier 1 Tier 2 Tier 3
SAP Note 2303243 – SAP HANA Multitier System Replication – supported
replication modes between sites with SPS11: ASYNC&ASYNC, SYNCMEM&SYNC
(Of course, distance (latency) will rule the use of replication mode options!)
Tier 1 ð 2 Tier 2 ð 3
SYNCMEM SYNC
ASYNC ASYNC

43. Backup & HA & DR Requirement

44. SAP HANA Timeline
The journey so far
SPS2
27. June 2011
SPS4
11. May 2012
SPS3
7. Nov. 2011
SPS5
29. Nov. 2012
SAP BW powered
by SAP HANA
SAP HANA Data Marts Round-Off Release
SAP Suite powered
by SAP HANA
SPS6
Mid 2013
SPS7
End. 2013
Real Time Data Platform
Core Topics
Innovations

47. Transition to HANA 2.0

48. Cisco for SAP HANA

49. Cisco and SAP
Infrastructure
Cisco Advanced
Services
Cisco SAP Managed
Services
Cloud
• End-to-end infrastructure
for SAP (Compute,
Network, Security,
Storage, Backup)
• Top SAP HANA success
cases in Thailand
• Assessment Service
• Planning and Design
Service
• Implementation Service
• Data Load Service
• Optimization Service
• Remote Management of
the SAP Solution
• 24x7 Solution Monitoring
• Patching Service
• Cisco Powered Service
Provider to host the
Application(s) and SAP
HANA
Contact: ciscoth-sap@cisco.com

50. Example Design
Fabric
Interconnect
LAN/SAN
frontend
Backup
Appliance
HX Data Platform
Fabric
Interconnect
LAN/SAN
frontend Cisco UCS C460 M4 as
SAP HANA Production
(4TB)

51. Q&A