Managing on-premise infrastructure for SAP workloads is challenging and costly. Learn how to bring agility, elasticity, cost savings, and scalability to new and existing SAP workloads with X1 instances, which offer 4x the memory of any other public cloud instance in the market today. In this session, you will learn the benefits and best practices for implementing high availability (HA), data recovery (DR), and migration for common SAP use cases on X1 instances. Learning Objectives: • The benefits and running SAP on X1 instances • Learn the ideal use cases and scenarios for using X1 for SAP • Best practices for migrating SAP workloads from on-premises to AWS • How to get started with migrating to AWS with X1

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Best Practices for Running
SAP HANA Workloads with
Amazon EC2 X1 Instances
Steven Jones – Sr. Manager, Solutions Architecture

2. Reduce Costs Increase Speed Improve Agility
Why are Enterprises Moving to the Cloud?

3. Move from risk-laden
up-front expense to
flexible variable expense
Stop guessing
at capacity planning
Go global in
minutes
Remove complicated infrastructure
management that adds little
business value
GE Oil & Gas is migrating 500 applications, and more than 750TB of data, to
the cloud by the end of 2016 as part of a major digital transformation, helping it
attain a 52% reduction in TCO and greater speed to market.
Get rid of time-consuming, expensive tasks

4. Lower the time spent
on infrastructure
Dedicate more
resources to innovation
Concentrate on new
business initiatives
“Our goal is to move at the speed of business. Our customers’ needs
change constantly, and we need to be able to adapt to that.”
Keith Homewood – Cloud Product Owner, Nordstrom
And focus on your core mission

5. SAP on AWS Driving benefits for you

6. SAP has been an AWS customer since 2008
AWS has worked closely with SAP to certify SAP solutions for production
deployment on AWS
AWS / SAP Alliance
AWS has been an SAP Global Technology Partner since early 2011

7. CustomerAdoption
2008
SAP as a Customer
S/4 HANA
SAP IQ / ASE
SAP HANA Platform Edition
SAP Afaria
SAP Business Suite
HANA One
HANA Developer Edition
SAP Cloud Appliance Library (CAL)
A1 / B1
RDS Solutions
BOBJ
SAP HANA for B1
BW on HANA
BW on HANA (4TB)
Today
AWS & SAP Key Milestones
X1 (2TB instance)

8. Databases
SAP HANA Editions
SAP MaxDB Database (7.8+)
SAP ASE (15.7.0.051+)
IBM DB2 (9.7+)
Microsoft SQL Server (‘08 R2+)
SAP Business
Applications
S/4HANA
SAP Business Suite*
SAP Business Warehouse
SAP Business All-In One
SAP Business One
SAP BusinessObjects
SAP Database &
Mobile Solutions
SAP Adaptive Server Enterprise
SAP IQ
SAP Replication Server
SAP Mobile Secure
Sybase Unwired Platform
*SAP ERP, SAP CRM, SAP SCM, SAP PLM, and SAP SRM applications, and apps based on Java or ABAP programming language
SAP Solutions on AWS

9. What customers are doing now

10. http://www.businesswire.com/news/home/20160516006767/en/SAP-Business-Critical-Applications-Gaining-Momentum-AWS
SAP Customers’ deployments on AWS now!
 S/4 HANA
 Business Suite on HANA
 BW on HANA
 SAP hybris
 SAP CRM on HANA
 Business Suite

11. Kellogg produces breakfast foods for more
than 180 companies worldwide, with annual
revenue of almost $15 B.
Using AWS saves us $900,000 in
infrastructure costs alone, and lets us
run dozens of simulations a day so we
can reduce trade spend. It’s a win-win.
 Needed a better way to track and model promotional costs (“trade
spend”) to improve the bottom line—and needed to be able to run
more than 1 trade-spend simulation/day
 Running SAP Accelerated Trade Promotion Planning (TPM) –
Powered by SAP HANA
 By using SAP HANA on AWS, Kellogg estimates it will save $900,000
over 5 years versus traditional on-premises infrastructure alternatives
 Increased business agility: Company can run dozens of trade spend
simulations each day, and decreases deployment time by 30x
 Leveraged existing SAP HANA software license investment on AWS
 Familiarity and Accessibility of the AWS platform enabled engineers
to easily apply their existing knowledge and infrastructure skills
Stover McIlwain
Senior Director of IT Infrastructure Engineering
Kellogg Uses AWS to Save $900,000 over 5
Years Over Using On-premises Infrastructure

12. Using AWS ... we can be more
nimble, which opens up many more
possibilities for our business.
Sahal Laher
Executive Vice President and CEO,
Brooks Brothers is a leading U.S.
retailer of fashion and accessories.
Brooks Brothers runs mission-critical
SAP Solutions on AWS
 Needed a more agile way of testing and implementing new business
ideas.
 Needed the ability to deliver solutions globally
 Leadership team worked with the IT organization to help them
understand their cloud journey and get their buy-in
 Launched new SAP HANA systems in hours instead of weeks using
AWS SAP HANA Quick Start Reference
 Running SAP Customer Activity Repository (CAR) and SAP CRM in
production – Powered by SAP HANA
 Saved thousands in data center costs, freeing up capital to invest
back into the business
 Secured highly sensitive customer data

13. X1 IS HERE!
2TB IN MEMORY CLOUD INSTANCE
13

14. “X1 instances offer more memory than any other SAP-certified cloud instance available today”
Designed for SAP HANA
Amazon EC2 X1 Instances
 Powered by four Intel® Xeon® E7 8880 v3
(Haswell) processors (64 cores / 128 vCPUs)
 2TB of DDR4 RAM per instance
 High memory bandwidth and larger L3 caches
 20 Gbps of network bandwidth
 10 Gpbs of dedicated bandwidth to Amazon EBS
Specifications
http://www.businesswire.com/news/home/20160518005520/en/Amazon-Web-Services-Announces-Availability-X1-Instances

15. Amazon EC2 X1 Instances
Intel® E7 performance features on X1
 Intel® AES-NI feature.
 Transactional Synchronization Extensions (Intel® TSX)
 Advanced Vector Extensions 2 (Intel® AVX2)
Intel® RAS feature on X1
 Single Device Data Correction (SDDC +1)
Specifications cont..

16. https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/iaas.html
http://scn.sap.com/community/hana-in-memory/blog/2016/05/16/sap-hana-on-aws-certified-for-high-memory
 S/4HANA
 SAP Business Suite on HANA
 SAP Business Warehouse on HANA
 DataMart / OLAP Scenarios
 SAP HANA Integrated Livecache
 SAP Business Planning and Consolidation
 Other SAP NetWeaver based applications
 Benchmarked @ 131,500 SAPS!
Amazon EC2 X1 Instances

17. 1952 GiB RAM
128 vCPU’s spread across 4 sockets
Amazon EC2 X1 Instances - Designed for SAP HANA

18. Confi
g
EBS Volume Type
Size
(GiB)
Combined
Throughput
(MiB/s)
Total
IOPS
Recommendation
#1 General Purpose SSD (gp2) * 3 x 1024 480 9000 Non-Production & Production
#2 Provisioned IOPS (io1) ** 3 x 1024 960 15000 Production
SAP HANA data and log area (striped with LVM)
* gp2 volumes balance price and performance for a wide variety of workloads
** io1 volumes provide the highest performance consistently for mission-critical applications
Non-database areas
Filesystem EBS Volume Type
Size
(GiB)
/ General Purpose SSD (gp2) 1 x 50
/usr/sap General Purpose SSD (gp2) 1 x 50
/hana/shared General Purpose SSD (gp2) 1 x 1024
/backup Throughput Optimized HDD (st1) 1 x 4096
SAP Supported EBS Storage Configurations
for HANA on x1.32xlarge (2TB)

19. Data
Area
Log
Area
Name Server
Index Server
Statistic Server
SAP HANA
(Master)
Name Server
Index Server
SAP HANA
(Worker)
Data
Area
Log
Area
…
Name Server
Index Server
SAP HANA
(Worker)
Data
Area
Log
Area
Backup
HANA
Shared
EBS Persistence Layer
Memory Layer
Common Backup and HANA Shared storage accross all
nodes via NFS
 Production configuration leverages SAP certified EBS for
SAP HANA Data, Log, and Backup areas
 Backed by solid-state drives (SSD)
 Single-digit millisecond latency
 Each Amazon EBS volume data is replicated across
multiple servers in an Availability Zone
 Each SAP HANA node carries the same Amazon EBS
configuration regardless of whether it is configured as
master or worker node
 Shared nothing storage concept for the SAP HANA data
and log areas
 Backup area is shared amongst all members of a cluster
EBS Storage Architecture for HANA

20. X1 is available in …
 US East (N. Virginia)
 US West (Oregon)
 EU (Ireland)
 EU (Frankfurt)
 Asia Pacific (Tokyo)
 Asia Pacific (Singapore)
 Asia Pacific (Sydney)
AWS Region Availability

21. Memory Optimized
Name vCPU
Memory
(GiB)
Network
Bandwidth
SAP
S
x1.32xlarge* 128 1952 20 Gigabit 131,500
r3.8xlarge* 32 244 10 Gigabit 31,920
r3.4xlarge 16 122 High 15,960
r3.2xlarge 8 61 High 7,980
r3.xlarge 4 30.5 Moderate 3,990
r3.large 2 15 Moderate 1,995
 Use in 2-tier and 3-tier configurations up to
hundreds of thousands of SAPS
 *Certified instances for SAP HANA
 Amazon EBS-optimized instances
 Enhanced networking (SR-IOV)
Check SAP Note 1656099 for more information
General Purpose
Name vCPU
Memory
(GiB)
Network
Bandwidth
SAPS
m4.10xlarge 40 160 10 Gigabit 47,320
m4.4xlarge 16 64 High 17,712
m4.2xlarge 8 32 High 8,856
m4.xlarge 4 16 High 4,428
m4.large 2 8 Moderate 2,214
Compute Optimized
Name vCPU
Memory
(GiB)
Network
Bandwidth
SAPS
c4.8xlarge 36 60 10 Gigabit 37,950
c4.4xlarge 16 30 High 19,030
c4.2xlarge 8 15 High 9,515
c4.xlarge 4 7.5 High 4,758
c4.large 2 3.75 Moderate 2,379
Wide Selection of SAP Supported Instances

22. Getting Started with SAP
HANA on AWS

23.  New implementation: Use the SAP Quick Sizer
http://service.sap.com/quicksizer
 Migrating an existing SAP Netweaver Business Warehouse System:
Use the ABAP sizing report for SAP NetWeaver BW described in SAP
note 1736976.
 Migrating an existing SAP Business Suite System to HANA: See
SAP note 1872170 to estimate the main memory requirements of the
HANA virtual appliance.
http://bit.ly/sap_sizing_on_aws
Sizing for SAP HANA on AWS
When sizing the HANA appliance, main memory is the most important
resource. Sizing methods vary depending on the implementation scenario.
In general, the following methods apply:

24.  SAP HANA Virtual appliance delivery
 Automated infrastructure provisioning for
SAP HANA
 Follows AWS and SAP best practices
 Self service and customizable
 AWS Quick Start reference deployments are
free - pay only for the resources you use.
 Provision Infrastructure and deploy SAP
HANA in minutes vs weeks or months.
https://aws.amazon.com/quickstart
SAP HANA Quick Start Reference Deployment

25.  SAP Implementation  AWS Onboarding  SAP OS/DB Migrations
 SAP POCs  SAP Sizing  Architecture Planning
 SAP Evaluations  Performance Tuning  SAP High Availability
 SAP Hosting  Backup & Recovery  Account Management
 Disaster Recovery  DB Administration  SAP BASIS
 24/7 Help Desk  OS Admin & Patching  SAP Upgrades
APN SAP partners provide a variety of SAP specific services on top of AWS
Consulting Services:
Managed Services:
AWS Partner Network: SAP Partners

26. Migrating SAP HANA to X1 on AWS

27. Common Migration Scenarios
 Migrate from existing EC2 instances
 Migrate from anyDB to an SAP HANA database on AWS
 Migrate an SAP HANA based installation from another
platform/on-premises to X1 on AWS
Tools and Methodologies
 Amazon EC2 instance type resizing
 Backup and restore
 SAP HANA classical migration
 SAP HANA system replication (HSR)
 SUM DMO
Migrating SAP HANA to X1 on AWS

28. Scenario Source Target Example
1 Scale-up
One existing instance
(HANA scale-up)
One X1 instance
(HANA scale-up)
Migrating one R3 instance to one X1 instance
2 Scale-out
Multiple existing
instances
(HANA scale-out)
One X1 instance
(HANA scale-up)
Migrating multiple R3 instances to one X1 instance
3 Scale-out
Multiple existing
instances
(HANA scale-out)
Multiple X1 instances
(HANA scale-out)
Migrating multiple R3 instances to multiple X1
instances
Migrating SAP HANA from R3 to X1

29. Physical Host (R3)
AWS Hypervisor
Virtual Machine
Physical Host
Physical Host: (X1)
AWS Hypervisor
SAP HANA
• Running • Shutdown
• SAP virtual
machine is
unavailable
• Issue API call to start
virtual machine
• SAP virtual machine
started on a new
physical host
• Amazon EBS
persistent volumes
are mapped by
default
SAP HANA
Physical Host: (X1)
AWS Hypervisor
SAP HANA
• Running (new host)
Change
instance type
using AWS
console or API
call
Physical Host (R3)
AWS Hypervisor
SAP HANA
 Best for scaling within an instance family
 Perform hardware upgrades in minutes
 Retain same IP addressing/hostnames (VPC)
Scenario #1 - Scale-up from R3 to X1

30. Benefits
 Allows for deployment on new
OS/Kernel version necessary for
ENA support
 Allows for use of optimized EBS
storage configurations for SAP
HANA on X1
Additional Cutover Steps
 Replicate any other SAP HANA
configurations on target system
 Repartition data (if needed)
 Update DNS and/or hosts file of
interfacing systems
 Apply a new license (if necessary)
 Resume operation
Scenario #1 - Scale-up from R3 to X1 (recommended)

31.  Additional Cutover Steps
 Replicate any other SAP HANA
configurations on target system
 Repartition data (if needed)
 Update DNS and/or hosts file of
interfacing systems
 Apply a new license (if necessary)
 Resume operation
Important: SAP Note 2093572
SAP HANA Migration from
Multi-Node to Single-Node
Scenarios #2 & 3 – R3 scale-out to X1

32.  Tools and Methodologies
 The SAP HANA classical migration makes use of the SAP heterogeneous system copy
process and tools. See http://scn.sap.com/docs/DOC-49744
 SAP Software Update Manager (SUM) Database Migration Option (DMO). See
http://scn.sap.com/docs/DOC-49580
Special Considerations
 Migrating from anyDB to HANA many times involves operating system and database
platform changes
 SAP ABAP code changes
 Operating system-specific dependencies
 Operating system tuning (i.e. Kernel Parameters, etc)
 Technology expertise such as Linux administration and support
 Network bandwidth and latency between on-premises and AWS
Migrating to SAP HANA AWS from
a different platform

33. Migrating AnyDB to SAP HANA on
AWS X1 (SAP SUM DMO)
1
2
3
SAP’s recommended option
 Combines Unicode Conversion + Upgrade + Migration
 Does not SAP require certified migration consultant
 Target environment must be available for data transfer
 Does require minimum support pack levels (See OSS
note 2161397)

34. Migrating AnyDB to SAP HANA on AWS X1
(SAP HANA Classical Migration)
 Good option for those that can’t use DMO due
incompatible software versions
 Based on Software Provisioning Manager
(SWPM) common for system copies / refreshes
 Requires SAP certified migration consultant
 Allows for offline data transfer
1
2
3
4
AnyDB
Amazon
S3
AWS
Storage
Gateway
AWSImport/
Export
Snowball

35. Migrating SAP HANA with Backup/Restore
1
2
3
4
Transfer HANA Backup
Amazon
S3
AWS
Storage
Gateway
AWSImport/
Export
Snowball
 4 distinct phases: Backup, Transfer, Restore, Recover
 Good option for initial seed of target environment or
system refreshes
 Helpful when network is constrained
 Approach is applicable to AnyDB

36. Migrating SAP HANA using HANA HSR
1
2
3
4
HANA System Replication
 SAP’s recommended approach
 Starting with SP12, SAP HANA allows for
target to be instantiated from a backup
 Allows for continuous replication of changes
from source system
 Ease of cutover to AWS

37. High Availability and Disaster
Recovery options

38. SAP HANA HA/DR – Unprecedented Flexibility
High Availability
• Amazon EC2 Auto Recovery
• Synchronous – HANA System
Replication to second AZ*
Disaster Recovery
• Backup/recovery in remote
region
• Asynchronous – HANA system
Replication to remote region
SAP HANA on AWS High Availability and Disaster Recovery Guide at aws.amazon.com/sap
For additional information see:
*HSR Options
• Replicate to non-prod
instance
• Replicate to same sized
instance and preload data for
fast recovery
• Replicate to smaller instance
and turn of preload option.
Resize secondary on failure &
save $$.

39. Solutions
High Availability (Multi-AZ) Disaster Recovery (Multi-Region)
RPO RTO Annual Cost RPO RTO Cost
Auto Recovery & HANA Backup/Restore Medium High Low
Auto Recovery & HSR without Data Preload (Warm Standby) Low Medium Medium
Auto Recovery & HSR without Data Preload (Warm Standby + Dev/QA) Low Medium High**
Auto Recovery & HSR with Data Preload (Hot Standby) Low Low High
Auto Recovery & Multi Tier HSR (Hot Standby + OOR DR) Low Low High Low Medium High
Auto Recovery & HSR with S3 Cross-Region Replication (Hot Standby + OOR DR) Low Low High Medium High Low
** Cost savings achieved by co-hosting Dev/QA
 Choose strategy based on your business drivers & budget
 Switch between options based on changing business
requirements
 Leverage 3rd party solutions for automated failover (SUSE &
NEC) or create your own custom scripts and hooks.
Partner Failover Solutions for SAP HANA on AWS
• SuSE – SLES HA Extension for AWS
2309342 - SUSE Linux Enterprise High Availability
Extension on AWS for SAP HANA
• NEC – NEC Express Cluster for SAP HANA on AWS
302728 - Supported scenarios with NEC
Expresscluster on Amazon Web Services
HA/DR - Unprecedented Flexibility

40. Physical Host X
AWS Hypervisor
Virtual Machine
Physical Host
Physical Hardware Y
AWS Hypervisor
SAP
Virtual Machine
• Running • Host/hypervisor
failure or loss of
network connectivity
• SAP virtual machine is
unavailable
• SAP virtual machine
started on a new physical
host
• Amazon EBS persistent
volumes are mapped by
default
SAP
Virtual Machine
Physical Host Y
AWS Hypervisor
SAP Virtual
Machine
• Running (new host)
Physical Hardware X
AWS Hypervisor
SAP
Virtual Machine
Result:
• Better uptime numbers, no waiting for hardware repairs
• Leverage hardware spares at no additional cost
Amazon CloudWatch
Alarm
Detect & Trigger
Automatic recovery of an EC2 instance when underlying checks fail, due to,
among other things, loss of network connectivity, loss of system power, software
issues on the physical host, and hardware issues on the physical host
Amazon EC2 Auto Recovery

41. Auto Recovery & HSR without Data Preload
(Warm Standby)
 Use HANA System Replication (HSR)
in Synchronous mode
 Turn off preload option.
 Replicated data/changes are
persisted to disk
 Use same size EBS volume
configuration as primary Memory
requirements for secondary instance
drastically reduced
 Use an smaller instance type with at
least 64GB of RAM or row store +
20GB (whichever is higher)
 During a failover event, resize
secondary instance to X1 and
resume operation
 RTO is slightly increased over hot
standby due to stop/resize/start
process.

42. AWS Quick Start for SAP HANA
(deep dive)

43. A virtual appliance delivery method to configure and install all
key components of the SAP HANA solution on AWS
SAP HANA Cluster
Public Subnet Private Subnet
CloudWatch Alarm
IAM Role / Instance Profile
security group
EBS VolumesBucket containing SAP
HANA software
NAT Gateway Bastion Host and/or RDP instance
(optional)
AWS CloudFormation
AWS Quick Start for SAP HANA – Deeper Dive

44. AWS Quick Start for SAP HANA Design
 Choose single or multi-node
depending on your total
memory requirements and
SAP HANA use case
 Deploy into an existing VPC if
desired
 Control connectivity entirely
through on-premises if
desired.
 Customizable through
parameters or template
modification

45. AWS Quick Start for SAP HANA
(Demo)

46. Unprecedented
Flexibility for HA/DR
Scale to meet
actual demand
Improve operational
reliability
Deploy in minutes vs.
week/months
End to End Automated
SAP HANA Deployments
Focus on your core
competency
Integrate SAP workloads into
your broader cloud strategy
Flexible Pricing Models
Running SAP HANA on AWS

47. Sample SAP S4/HANA POC system:
 1 X1 EC2 instance (VM): 128 vCPUs x 1962 GB memory
 Online M-F 8AM-5PM:40 hours / 1 week
 Persistent storage: ~4TiB
 Backup storage: ~4 TiB
* Pricing based on US-East region as of 08/14/2016
Component AWS Resource Quantity Unit Cost*
Weekly
Cost
Virtual Machine x1.32xlarge - SLES 12 40 hrs $13.438** p/hour $537.52
Primary Storage
EBS General Purpose SSD
(GP2) volumes
4196 GB $0.100 p/GB
p/month
$105.00
Backup Storage EBS Streaming Magnetic (ST1) 4096 GB $0.045 p/GiB
p/month
$46.08
Network Data Transfer Out 50 GB $0.090 p/GB $4.50
$693.10
** Save up to 43% over on-demand pricing with 1 Year RI purchase and up to 72% with 3 Year RI purchases
1-week POC pricing example

48.  Contact your AWS account team
 Deploy SAP HANA in minutes using SAP HANA Quick
Start Reference Deployment:
http://docs.aws.amazon.com/quickstart/latest/sap-hana/
 Apply for up to US$1,000 in AWS Promotional Credits to
evaluate SAP HANA on AWS X1 instances
 Come talk to us during SAP Tech Ed Las Vegas, Sept
19-23, 2016 @ booth #405
 Join us for an exciting new announcement with SAP
taking place on Sept 7: http://events.sap.com/sap-
amazon-web-services/en/home
Learn more about the Pilot offer, including
terms and how to apply for up to US$1,000
in AWS Promotional Credits at
http://aws.amazon.com/sap/saphana/pilot/
Getting started is easy

49. EC2 X1 Instances:
https://aws.amazon.com/ec2/instance-types/x1/
SAP on AWS Information:
https://aws.amazon.com/sap/
AWS Quick Start Release Features:
http://aws.amazon.com/quickstart/
SAP HANA Quick Start Reference:
http://docs.aws.amazon.com/quickstart/latest/sap-hana/
Other SAP HANA on AWS resources:
http://aws.amazon.com/sap/solutions/saphana/
Further Information

50. Thank You