SAP and SAP HANA on VMware

SAP & VMware – Strategic Partnership

Run SAP on VMware anywhere...simple
• Preferred strategic partnership since Sapphire, 2011 SAP Applications On vCloud Suite
SAP Business Suite
• Entire SAP stack virtualized in production with VMware

SAP Basis

BOBJ
CRM

SCM
ERP
• Common certified Architecture – including SAP HANA in

ETC
BW
production on vSphere 5.5

(Performance Management and Analytic)

Netweaver (ABAP +JAVA)
• Run in production with confidence

vCenter Operations
DBA
®
• Run simple on VMware anywhere Traditional Databases SAP HANA

• Integrated with SAP global support network

OS Adm
vCloud Suite(vMotion, HA, SRM, DRS)

VMware Adm
3rd vSphere (ESX Cluster)
Bus. Party
BA Suite Apps
BW

On Premise Hybrid Cloud

Daimler AG
“AMG-Mercedes is now live in production with SAP HANA and VMware vSphere 5.5 with a 1TB memory configuration, accelerating our move to
a software-defined data center,” said Reinhard Breyer, CIO, AMG. “We believe virtualized SAP HANA with VMware’s vSphere could be the key to
our future, as we move to cut operational costs and simplify our data center operations.”

2
Introducing Production SAP HANA on vSphere 5.5

Automated
Capacity Planning Rapid
Operations
and Optimization Provisioning
Management

>Unify and manage >Live migrate SAP HANA >Deploy SAP HANA
SAP HANA with rest of databases across hosts instances in hours
virtual datacenter in minutes

Virtualization-Aware
Automated Resource High Availability Security and
Allocation Compliance
APP

>Automatically restart >Protect workloads;

>Easily manage peak SAP HANA VMs to
analytic workloads reduce downtime
maximize uptime through rapid issue
resolution

3
SAP HANA on vSphere 5.5 Delivers Material Value

Better Service Levels Faster Time-to-Value Lower TCO

• 99.9%+ availability* • Rapid provisioning: deploy • Reduce CAPEX by 70% and

• Zero downtime and zero data within hours vs. days** OPEX by 56%***
loss with vMotion, enabling • Template provisioning • Unify and manage SAP
business continuity without ensures consistency and HANA with the rest of virtual
compromise scalability across data center
• Automatically restart SAP environments • Greater utilization of existing
HANA VMs to maximize resources and infrastructure
uptime

*EMC IT, 02/14 EMC Perspective, H12853 ** EMC IT internal analysis, ***Taneja Group Research, 2014
SAP HANA Platform on VMware vCloud Suite
Differentiated Solution – Removing the 3 Major Barriers to Database Virtualization

1. Performance Phase I Results Published 2012 – vSphere 5.0/1

SAP benchmarks show physical to virtual delta Sub-

P2V Supported
SAP HANA Platform Capacity
is <10%. Performance not an issue. Delta /Certified
Licensing
SAP HANA Scale Up <10% YES N/A
2. Support SAP ASE < 7% YES YES
SAP IQ < 7% YES YES
SAP HANA Platform fully certified to run on
vSphere. No requirement to reproduce on physical SAP Replication < 5% YES YES
Server
SAP SQL Anywhere < 5% YES YES
3. Licensing

Sub capacity licensing on cores/sockets in use.

No need to license entire host – cloud model;
pay-per-use. Running SAP HANA on vSphere:
- No additional cost or licensed required
- It’s just another virtual machine
5
SAP HANA Production Support – General Availability
SAP HANA on vSphere Production Certification Certification Process

Began 2013 Q3 – Announcement 4/28 2014 and Beyond

SAP HANA Production Support Current Certification
• Scale up support (Up to 1TB) • Production use case vSphere 5.5
• On-line service system note published – SAP HANA SP07 or greater – up to 4 sockets
- 1995460 – SAP HANA on VMware in – SAP HANA Multi VM – Controlled Availability
production – Other VMs consolidation – Fully supported
– All use case – BW, Suite on HANA, & Side Cars
• Supported on SUSE and RedHat Linux
• Non-Production use case vSphere 5.1
• Requires certified hardware (same as physical) - SAP HANA SP05 or greater – up to 8 sockets
Supported VMware Technologies - Multi-VM supported
• Live Migration vMotion After Initial Certification
• Distributed Resource Scheduler (DRS) • No lag – same release cycle as hardware vendors
– DRS business rules • Deeper testing and integration of VMware vClould
• High Availability (HA) (scale up only) Suite
• Creation of SAP HANA Clones/Templates – VMware vCenter Site Recovery Manager
SAP/VMware Joint Support – VMware vCloud Automation Center
• SAP will provide support for SAP HANA issues – VMware vCenter Operations Management Suite
• VMware takes ownership of performance issues – VMware vCloud Director
6
SAP HANA on VMware: Multivm Support Controlled Availability
Straight Forward Application Process
Customers interested in running multiple SAP HANA
VMs on VMware vSphere 5.5 in production can
apply for Controlled Availability of SAP HANA
production support by sending an email to: [email protected]

This email should contain: 1. High-level scenario description and timeline (e.g.
planned Go-live date)
2. Expected database size (compressed HANA DB size,
number of users)
3. Hardware spec (HW vendor, server t-shirt size)
4. Planned HA/DR setup (if applicable)
5. Contact details for further communication

All information given will be kept confidential and is only being used during the selection process. Once
accepted, customer will get access to restricted SAP Note, officially stating SAP HANA support for the
presented scenario.

7
SAP HANA Support Summary
Capability Supported in Production Supported in Test/Dev

HANA Scale up to 1TB of Memory Yes Yes

vCloud Suite Version 5.5 and above 5.1 and above
SAP HANA Version SP 07 and above SP 05 and above
vSphere vMotion Yes Yes
VMware HA Yes Yes
VMware DRS Yes Yes
Server Hardware Certified Appliances Certified Appliances
Storage Certified Appliances or TDI Certified Appliances or TDI
Scale Out Configuration No No
CPU Sockets per server Up to 4 Up to 8
(Intel E7 Westmere EX or Intel E7 v2 Ivy
Bridge EX processor)

8
SAP HANA Sizing Deployment
Considerations

9
Columnar and Row (Traditional) Database Stores
Row Store Table: Logical View and Physical Layer
Order # Last Amount Item # … … State
• Row Stores Name
– Store logically related attributes of different types
1024 Smith $257.97 088-3X … … CA
• Sales Orders, Invoices, etc.
– Insert/update to the row store 1025 Jones $1,122.18 215-4B … … NJ

– Analytic queries reporting; unnecessary scans 1026 Lee $655.43 113-22 … … NY

• Ex: Report/Query Amount and State
– Typically 20 attributes for every 2 of interest
1027 James $919.22 003-44 … … AZ

• Data Warehouses table 100’s of attributes wide

Column Store Table: Physical Layer
• Column Stores – Fully Relational Order # 1024 1025 1026 1027
– “Turns The Tables” on physical layer
Last Name Smith Jones Lee James
– Logical Layer
• Users view is same as row data stores Amount $257.97 $1,122.18 $655.4 $919.22
3
– Physically Layer
Item # 088-3X 215-4B 113-22 033-44
• In-memory or on disk columnar
• Accesses only the attributes of interest … … … … …
– Optimized for analytics and Ad Hoc queries … … … …
….
State CA NJ NY AZ

10
Optimization: Tuning Traditional
Analytic Databases (OLAP) Base Table + Materialized Views + Indices
• DBAs Can Minimize Unnecessary Table Scans
– Materialized View; Partitions (Optimization Objects)
• Tables which reside on disk; can contain own indices
• Pre-Joins; updateable manually, scheduled, triggers
– Complex Subject and Management
• Varies by rdbms vendor Row Store
• Data Warehouses contain100’s of reports
– Typically 30% - 90% of total size of database
Base Table – Requires Data Only
• Columnar Does Not Need Optimization Objects
– Works on Data Only
– Higher Degree of Compression

• Ad hoc Queries
– Cannot be optimized; requires pre-knowledge
Column Store
– Ad Hoc/Data Mining no problem for column stores

11
Row to Column Store: Does The Total Databases Size Matter?
• No Indices, Materialized, Partitions The Question is NOT How Big is My Data Warehouse?
– Inserts/Updates faster
– Faster data loads Base Table + Materialized Views + Indices
• No Dropping/Regeneration
– Indexes, temporary tables
– Reduces time to query
• Phantom results

• Do You Need DBAs? Of Course…

– Frees up DBA for strategic planning/projects
Row Store

• Fundamentals of Columnar Data Stores

– Before Sizing
The Question is
• Reduces overall size of database
• Higher degree of compression ? How Much Data is in My Data Warehouse?
• Significantly less maintenance

SAP Sizing Tools Can Determine That Answer

12
Sizing - SAP HANA Scale Up for vSphere
• Use SAP HANA Specific Tools (same as physical) Controlled
SAP HANA Availability
QuickSizer
– The Criteria for sizing RAM Consists of:
- No different than physical
• Memory sizing for column store (compressed data)
- Total RAM <=1TB then OK to virtualize
• Memory sizing for row store - Total RAM >1TB Use ABAP Based Sizing
• Memory sizing for runtime objects
– The Total RAM determines if SAP HANA is a candidate for
virtualization
ABAP Based Sizing
• Ex: SAP QuickSizer for SAP HANA: SAP HANA Non-Active Data Concept
– If Total RAM <=1TB then Deploy on vSphere

• SAP ABAP Based Sizing Hot

In-memory; with runtime objects
– SAP Preferred method, much more accurate
Warm In-memory; no runtime objects
– Non-active Data Concept
• Hot, Warm, Cold Cold Data can reside on disk
– SAP HANA with >1TB of RAM can be virtualized
 SAP IQ MultiPlex (Scale Out)

SAP IQ: Strategic to HANA Data Discovery

(Data Scientists)
Application
Models
(Biz Analysts)
Reports/Dashboards
(BI Programmers/End Users)

• SAP IQ SAP IQ
– Columnar; shared everything Logical Server 1 Logical Server Logical Server 3
2
– Scale up/out architecture
High Speed Interconnect
– Mature product – large install base
– Many VMware customers in production Administration
(DBAs)

• Complimentary to SAP HANA Load, Prepare, Mine, Report in a workflow

• Heavy Parallelization
– In the moment business decisions; • Worlkload isolation via elastic logical servers
historical data • Collaboration through shared storage
• Unique in the industry for quick time to value for end users

– SP08 – SAP HANA extended tables

Timing Comparison (16 Cores)
– SAP IQ, ASE, and SAP HANA Synchronized Service
Packs 3500

3000
• SAP IQ 15.4 validation testing 2500
– Standard x86 servers 2000 VMDK Multiwriter
– EMC® VNX® 5700 FC Unified Storage System 1500 RDM SCSI Sharing

– 300GB single node and multiplex 1000 Physical

– vMotion < 3 minutes under load 500

0
Load 1 Power Throughput Power Throughput
(DQP) (DQP)

14
SAP IQ For Warm/Cold Data Management
• SAP HANA Real-Time SAP HANA Dynamic Tiering
– Cutting edge, in-memory platform
– Transact/analyze in real-time
SAP HANA
• IQ Warm/Cold Data Management Hot Data

– SAP HANA SP08 & IQ 16

– IQ as NLS for SAP BW
+
Warm Cold
– IQ as ILM for SAP ERP
– Extended storage for SAP BW on HANA

• Future Public Roadmap – Dynamic Tiering

Expand SAP HANA capacity with warm/cold
– Common installer
data in extended store (SAP HANA warm store)
– Single licensing model
– Optimized query processing Tight integration between SAP HANA hot store
and SAP HANA warm store for optimal
– Unified backup/restore performance
SAP HANA Extended Storage - Scaling Beyond 1TB on vSphere
• SAP HANA Extended Storage Queries & Updates
– Query and update data seamlessly are Initiated Via
HANA
– Scales to terabytes or petabytes
– Workload defines Hot/Cold data SAP HANA
HANA Native Table
• Transparent to Application or User SAP IQ
– Intelligent placement of data HANA Native Table

• Cost Effective Scaling vCloud Suite SAP HANA IQ Extended Storage

– Terabyte or Petabyte scaling of cold/warm data

– Standard x86 servers
– Must use SAP sizing guidelines SAP
SAP IQ SAP IQ SAP IQ
HANA

OS OS OS OS

vSphere 5.5 vSphere 5.x

Certified hardware X86 Hardware

SAP HANA Tailored Appliance Model
Data Center Integration (TDI) Application
SAP Database
• SAP HANA Server with customer’s preferred SAP
HANA
SAP
HANA Operation System
storage solution Server
HANA
Server Virtualization
Server
– Same BOM as the certified appliance Server
without storage Network

– Move towards “Open SAP HANA” Storage Storage

• Utilize existing infrastructure investment SAP HANA TDI Model

– Easier and more cost-effective migration SAP Virtualization
to SAP HANA SAP
HANA
SAP
HANA
Server
– SAP provided hardware verification tool HANA
Server Server
Server
• Run SAP HANA on vCloud Suite
Network
– Near native performance; meet KPI’s Shared Network

– Leverage VMware technologies Enterprise Storage

• vMotion, DRS, HA Storage

– OSS note updated to include VMware

17
SAP HANA on VMware
Best Practices

18
SAP HANA on vSphere Best Practices Overview
• SAP HANA on vSphere – It just Runs!
– Phase I Performance Testing:
• All performance results were out of the box; no special tuning required
– For the most part SAP HANA follows general published vSphere Best Practices for databases
– Documented General Best Practices and SAP HANA Optimizations

• Most Support Issues Occur at Storage Layer

– Minimized with in-memory databases

• SAP HANA on vSphere Best Practices Guide and More:

– www.vmware/go/sap-hana
Set Memory Reservations for
SAP HANA Virtual Machines
• Managing Memory Resources for Virtual Machines
– Limits: are the maximum amount of resources a virtual machine
can use
– Shares: proportional allocation of resources when virtual
machines are competing for Memory
– Reservations: a guarantee of resources for a virtual machine
• Used for SAP HANA – Predictable performance; Guaranteed SLA
• Fully Isolated, Independent, Secure SAP HANA Databases
• Different from SAP HANA Multi-SID

• Enable Reserve All Guest Memory Setting

– Linked to the virtual machine memory configuration
– Memory reservation is immediately readjusted when the
• Memory reservation is automatically increased/decreased
– With SAP HANA – won’t forget to adjust reservations when
“Reserve All Guest Memory” is enabled (Check Box)

20
Configuring Paravirtual VMware vSphere Web Client
SCSI Controllers
• Paravirtual SCSI (PVSCSI) controllers
– High performance storage controllers
• Greater throughput
• Lower CPU utilization
– Suited for high-performance storage environments
– Use PVSCI for Data and Log devices
– Can be used for OS/Executable – not bootable from SAN VMware vSphere Client

• Setting SCSI Controller Type

– For both vSphere Web Client and vSphere Client
• Change type to – VMware Paravirtual
– Check support matrix for use of Paravirtual
SCSI adapters
• KB Article 1010398

21
Use VMware VMXNET3 Adapter Type/ VMware vSphere Web Client
Virtual Distributed Switch
• VMXNET Optimized Performance in a Virtual Machine
– Operating system vendors do not provide built-in drivers for
this card
– Must install VMware Tools to have a driver for VMXNET

• When Creating Ethernet Adapters

– Use VMXNET3 Adapter Types Change to “VMware Paravirtual”

• Virtual Distributed Switch (vDS) or

Virtual Standard Switch (vSS) VMware vSphere Client
– vSS resides on single host; vDS centrally managed across all hosts
– vDS simplifies management of complex environments (SAP)
• Shape and manage traffic; isolate database, application, backup servers
– vDS Aligns with SAP TDI Enterprise Network Beta

22
Selection Optimal IO Schedulers; Transparent Huge Pages
• Linux IO Schedulers Check IO :Scheduler In Brackets
– Choosing IO scheduler – NOOP, CFQ, or Deadline
# cat /sys/block/sda/queue/scheduler
– Use NOOP Scheduler
[noop] cfq deadline
• Reduce I/O latency and increase
• Reduce CPU time spent re-ordering I/O requests
– Work with system admin to change and make permanent

Check THP: Policy In Brackets

• Transparent Huge Pages (THP) Support
# cat /sys/kernel/mm/
– Increase Translation Lookaside Buffer efficiency transparent_hugepage/enabled [always]
– Can provide 10% performance boost madvise never
– SLES SP 2 – default configuration THP is enabled
– Work with sys admin to make sure this is the default behavior
– SAP OSS Note provides guidance on when to use THP

23
vSphere Low Latency Setting & vSphere Latency Sensitivity

Guest Memory Pre-Allocation

• vSphere 5.5 New Per-VM feature called Latency Sensitivity
– Allows virtual machines to exclusively own physical cores
– Avoiding overhead related to CPU scheduling and contention
– Positive Performance Impact for SAP HANA
• Set Latency Sensitivity to “HIGH”; with vSphere Web Client
• vSphere Client – add sched.cpu.latencySensitivity = HIGH to .vmx file
– Caution Not always right choice
Guest Memory Pre-Allocation
• vSphere Guest Memory Pre Allocation
– Further reduce latency by memory pre-allocation upon startup of
virtual machine
– SAP HANA pre-allocates and manages its memory pool
– Add following lines to the .vmx file to enable pre-allocation
• sched.mem.prealloc = “TRUE”
• sched.swap.vmxSwapEnabled = “FALSE”

24
NUMA, CPU Affinity, Hyper-threading
• No Over-commitment of CPU resources for SAP HANA production VMs
• SAP HANA has been found to perform optimally with virtual NUMA that
reflects the physical NUMA
– Default behavior of vSphere
– Additional step of using CPU affinity to pin virtual NUMA nodes to physical NUMA nodes improves
performance by preventing any virtual NUMA node migration to different physical NUMA nodes
• vCPUs and Hyper-threading
– Hyper-threading adds a logical thread to each physical core which increases performance by up to 20%
– Best Practice is to have HT enabled
– With HT enabled each Physical Core = 2 logical threads (example – Host with 40 cores has 80 threads)
– vCPU = logical thread
– Important to consider when sizing VMs for HANA and determining how many vCPUs per vNUMA node
– See VMware Best Practices for SAP HANA on vSphere for details.

25
SAP HANA on VMware vSphere Best Practices Guide

• All the best practices are covered in detail in the best practices guide
• http://www.vmware.com/files/pdf/SAP_HANA_on_vmware_vSphere_best_practices_guide.pdf

26
SAP HANA on vSphere
Rapid Deployment and Workload Management
Rapid Deployment of SAP HANA Databases
• VMware Templates and Clones
– A clone is a copy of a virtual machine
– A template is a master copy of a virtual machine
• Used to create many clones

• Ex: SAP HANA Template

– Rapid deployment
• Optimized SLES Environment
• rpms, OSS notes, kernel parameters
– SAP Unified Installer
• SAP HANA, SAP HANA Studio, Life Cycle Manager, Application
Function Library (AFL), SAP HANA Database Client
– SAP HANA Customer Proof of Concepts
• Use of VMware Templates for Multi-VM CA Study
• Some customer slots remain

• Complex Environment: SAP Blueprints

– BluePrinting & Provisioning SAP Using vCloud Automation
Center and Applications Director
• SAPaaS - Session ID MGT1559
Rapid Deployment of SAP HANA Hosts
• VMware host profiles
– Enables you to establish consistent host
configurations
– Automated compliance checks
– Reducing errors caused by misconfigurations
• SAP HANA
– Consistent host configuration critical to
performance
– Check and maintain SAP HANA clusters:
• Compliance
• Attach Host Profiles in SAP HANA Cluster
• Edit Host Profile and update cluster

• Complete Rapid provisioning solution

– VMware templates – SAP HANA VMs
– VMware host profiles – SAP HANA Hosts
Mission Critical: Zero Downtime Migrations
Live SAP HANA Database Migrations
• VMware vMotion
– Move running virtual machines across ESXi Server
vMotion
• Live Migrate SAP HANA Databases
– Zero downtime maintenance
– Migrate live databases
– Little impact to users

• Critical For In-Memory Databases

SAP HANA In-Memory State
– Preserves the entire state of memory
Pool (Free)
– Avoid a database – loses temp tables, computations
Temporary
Computations
• VMware vMotion – All or Nothing
SAP HANA Column Tables
– Like an atomic transaction; completes or does not Memory Pool
Used Memory
complete Row Tables

System Tables
– Does not leave VM in phantom state
Code & Stack
VMware Distributed Resource Scheduler (DRS)
• Distributed Resource Scheduler (DRS)
Automated SAP HANA Management
– Align IT infrastructure with business goals
Infrastructure Abstraction
– Dynamic allocation of compute resources
• Managing SAP HANA databases
– Database workloads are both dynamic
and transient Dynamic
Resource
– Directs compute resources where needed
Scheduling
– Maintain database response times
and SLA’s
• DRS Automation Levels
– Manual – recommend initial placement
and migrations
– Partially automated – initial placement
automated; recommend migrations
– Fully automated – automated placement
and migrations
DRS Affinity Rules – Automated Management of SAP HANA VMs
• Use Affinity Rule to Prevent Migrations
– Non-certified servers
– Resulting in unsupported configurations

• DRS Rule Creation

– Host DRS Groups
• Contains only the hosts vm can run on
– VM DRS Groups
• Group types of VM:
– SAP HANA Group – all HANA VMs
– Other SAP VMs – ASE, SAP Application Servers

– SAP HANA DRS Affinity Rule

• Contains Host Group & VM Group
• SAP HANA VM can only run on certified hosts

32
DRS Anti-Affinity Rules – Automated Management Continued..
• Exclusive Resource Rights
– Separate SAP HANA VMs
– Evacuate VMs other that SAP HANA

• DRS Anti-Affinity Rules

– Only 1 SAP HANA VM per host
• All resources to single HANA VM
– No other VMs on cluster
• All other VMs to standard x86 host group

• Useful For Managing Peaks and Spikes

– End of Month, Quarter, Year

33
Analytics: Transient and SAP HANA Physical
Temporal Workloads Resources Cannot Be Reclaimed / Redirected
SAP HANA Appliance SAP HANA Appliance
• Many Peaks Valleys – End of Month, Quarter, Year 512GB 512GB
– Resources locked into physical servers SAP HANA SAP HANA
• Cannot be reclaimed; regardless of usage characteristics
“Prod-1” “Prod-2”
• Wasted idle resources after EOM, EOQ, EOY

• SAP HANA
– Highly efficient in-memory processing
– Orders of magnitude faster than traditional databases SAP HANA Multi-VM
Reclaim/Redirect CPU Resources
• SAP HANA on vSphere
– SAP HANA databases can reclaim idle CPU resources 2x 510GB SAP HANA Databases
– More efficient use of physical hardware SAP HANA SAP HANA
• VMware Workload Management “Prod-1” “Prod-2”
– SAP HANA “Prod-1” – heavy EOQ processing
– SAP HANA “Prod-2” – completed EOQ
vSphere 5.5
– Redirect CPU resources to SAP HANA “PROD-1”
• Consolidated workloads “Faster Than Physical”
1TB Certified Server

34
VMware vCenter Operations MP Overview
for SAP HANA – Overview • Exposes SAP HANA related performance, health,
and availability metrics within vC Ops
• Includes out-of-the-box dashboards,
supermetrics, metrics, and metrics collections for
SAP HANA
• Provides visibility into SAP HANA workloads
running on VMware vSphere, bare-metal, and
cloud-based deployments
Benefits
• Enables end-to-end views of SAP HANA,
underlying compute resources, and storage
• Gain enterprise-wide visibility into SAP HANA
workloads
• Greatly reduce troubleshooting times, and
simplify security & compliance management
Demo
SAP HANA integration with vCenter Operations delivers
automated correlation of performance, health, and availability • vMotion SAP HANA – vCenter Operations Suite
data for SAP HANA workloads BlueMedora Performance Dashboards
Migrate Live Databases with Zero Downtime
Live SAP HANA Database Migrations
vMotion Infrastructure Abstraction

• Moves live running SAP HANA databases

from one certified host to another
vMotion
• Eliminates downtime from planned server
maintenance
• Maintains entire memory state, data,
temporary tables, statistics
• All or nothing migration-does not leave
virtual machines in phantom state
• No user impact

36
Automatically Balance Workloads Across Hosts
Automated SAP HANA Management
Infrastructure Abstraction
Distributed Resource Scheduler (DRS)
• Scales and manages computing
resources without service disruption
Dynamic
• Automatically balances workloads Resource
across hosts Scheduling

• Use DRS rules to prevent SAP

HANA migrations to non-certified
hosts
• Maintains response times and
service levels

37
Set User-Defined Rules

• Anti-affinity rules
- Single instance per host
- Migrate non-SAP HANA virtual
machines for end of month
processing from host(s)
• Affinity rules
- Runs only on certified hardware

38
Deploy Instances and Hosts Rapidly

• Automatically deploys additional hosts

using a master host profile
• Eliminates need for specialized scripts
• Maintains consistent service levels
• Protects against unauthorized
changed parameters using host profile
compliance checks

39
Deliver Highest Levels of Uptime

High Availability (HA)

• Monitors hosts and virtual
machines to detect system
failures
• Automatically restarts virtual
machines on other certified hosts
when outage is detected
• Ability to set virtual machine
restart priority

40
Increase Productivity

• Runs multiple databases on a single

certified host
• Maintains service levels for
overprovisioned CPUs
– Sets memory reservations
• Speed development and debug
processes

41
Deployment
Considerations
and Options

CONFIDENTIAL 42
SAP HANA: Relevant vSphere Maximums
Deployment considerations scale up or SAP HANA on VMware

VMware vSphere ESX 4.1 5.0 5.1 5.5

Virtual CPUs Per VM 8 32 64 64

RAM Per VM 255GB 1TB 1TB 1TB

Logical Cores Per ESX
320 2048 2048 4096
Host
RAM Per ESX Host 1 TB 2TB 2TB 4TB

Virtual Disk Size 2TB 2TB 2TB 64TB

Virtual Disks Per VM 60 60 60 60

43
SAP HANA Scale Up Model on VMware

Reducing IT footprints – consolidation of SAP HANA databases

• Fully isolated, secure, and encapsulated
• Not SAP HANA Multi SID – can guarantee resources with vSphere
• Right sizing – mixed HANA T-shirt sizes
• ROI – purchase large server rather than multiple smaller server
• vSphere 5.5 – 4 TB per host

Consolidate 1TB SAP HANA VMs Flexible SAP HANA T-Shirt

1TB 1TB 1TB 512GB Sizes
1TB 512GB 256GB 128GB
HANA HANA HANA HANA HANA HANA HANA HANA
SLES SLES SLES SLES SLES SLES SLES SLES

vSphere 5.5 vSphere 5.5

44
Sizing — SAP HANA Scale Up for vSphere
• Use SAP HANA Specific Tools (same as physical)
– The Criteria for sizing RAM Consists of: SAP HANA QuickSizer
• Memory sizing for column store (compressed data)
• Memory sizing for row store • No different than physical
• Memory sizing for runtime objects • Total RAM <=1TB then OK to virtualize
• Total RAM >1TB Use ABAP Based Sizing
– The Total RAM determines if SAP HANA is a candidate for
virtualization
• Ex: SAP QuickSizer for SAP HANA:
– If Total RAM <=1TB then Deploy on vSphere
ABAP Based Sizing SAP HANA
• Ex: SAP ABAP Based Sizing Non-Active Data Concept
– SAP Preferred method, much more accurate
– Non-active Data Concept Hot In-memory; with runtime objects
• Hot, Warm, Cold
– SAP HANA with >1TB of RAM can be virtualized
Warm In-memory; no runtime objects

• Ex: Disk sizing Cold Data can reside on disk

– Log = 1 x RAM
– Disk Persistence = 4 x RAM
SAP HANA Tailored Data Center Integration (TDI)

Application
• SAP HANA Server with customer’s SAP
SAP Database
HANA
SAP
preferred storage solution HANA
Server
HANA
Operation System
Serve
- Same BOM as the certified appliance Serve
r
Virtualization

without storage r Server

Network
- Move towards “Open SAP HANA”
Storage Storage
• Utilize existing infrastructure investment
- Easier and more cost-effective migration
Appliance delivery approach
to SAP HANA
- SAP provided hardware verification tool
• Run SAP HANA on vCloud Suite SAP
SAP
SAP
HANA
Virtualization
HANA
- Near native performance; meet KPI’s HANA
Server
Serve Server
Serve
- Leverage VMware technologies r
r
• vMotion, DRS, HA Network

- OSS note updated to include VMware Shared Network

Enterprise Storage
Storage

SAP HANA tailored data center integration

46