AWS fornisce una suite di servizi e tools volti a eseguire workloads SAP HANA business-critical sul Cloud. In questa sessione, discuteremo come integrare i servizi AWS, i tools nativi SAP HANA per la high availability (HA), e software di terze parti per implementare i sistemi SAP HANA in HA sul Cloud AWS. Descriveremo le varie opzioni che fanno uso di diverse features AWS, di multi-Availability Zones, di global regions, e discuteremo i pros, cons, e costi correlati di ciascuna opzione.

1. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Webinar
A n t o n i o D ’ O r t e n z i o – A W S S o l u t i o n s A r c h i t e c t u r e
SAP HANA High Availability on AWS
D e c e m b e r 1 1 , 2 0 1 8

2. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What this session will cover:
• Create awareness about the availability of a SAP system
• Help identify important metrics
• Identify the available architecture patterns on AWS
• Explain the pro‘s and con‘s of the available patterns
What this session will NOT cover:
• Discuss specific applications or databases
• Promote known High Availability solutions
This sessions assumes you have:
• Some basic knowledge (>0) of AWS Cloud core concepts (e.g. Amazon
EC2, Amazon VPC, etc)
• Basic knowledge of SAP and SAP HANA architecture core concepts

3. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• SAP: Impacts from Downtime and Benefits from
High Availability
• AWS Global Infrastructure
• SAP HANA HA Options in AWS
• Lessons Learned
• Discussion with TechEdge
Agenda

4. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
System =
=

5. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
System = precious
=

6. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What is the impact of
downtime?

7. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Impact to customers relying on your business
Impact to business financials
Impact to business reputation and credibility

8. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Position, action, benefit
Choose
HA
design
Build
and
test
Optimize
and
enhance

9. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What is High Availability?

10. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Failure: Something is broken
Mean Time Between Failure: Average
time that something is working
Mean Time To Repair: Time it took to
fix something that broke

11. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Availability
Calculated as:
[ MTBF / (MTBF + MTTR) ]

12. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What does it all mean?
TBF1 + TBF2 + TBF3 + TBF4 + TBF5 + TBF6 = 523,000 mins  MTBF = 523,000/6 = 87,166 mins
TTR1 + TTR2 + TTR3 + TTR4 + TTR5 = 2,600 mins  MTTR = 2,600/6 = 433 mins
Availability = 87,166/(87,166 + 433) = 0.995
99.5% Availability (i.e. about a 7 hours downtime every 60 days)

13. AWS Global Infrastructure
Region -> Availability Zone -> Data Center

14. AWS Global Infrastructure
Region
The AWS Cloud infrastructure:
• A Region (19) is a physical location in the world where we
have multiple Availability Zones
• Availability Zones (57) consist of one or more discrete
data centers, each with redundant power, networking, and
connectivity, housed in separate facilities. Applications and
Data are replicated in real time and consistent in the
different AZs
1
N
2 1
N
2
1
N
2
Low-latency
ensures real
data replication
Distance
ensures
high
availability
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
2
1
N
2 1
N
21
N
2 1
N
2 1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
1
N
2 1
N
2
1
N
2
AWS Regions (19)
AZs (57)
1
N
2 1
N
2
1
N
2
1
N
2
N. Virginia
Ohio
N. California
Oregon
Mumbai
Seoul
Singapore
Sydney
Tokyo
Canada
Beijing
Frankfurt
IrelandLondonSão Paulo GovCloud (US-West)
1
N
2 1
N
2
Ningxia
1
N
2 1
N
2
1
N
2
Paris
1
N
2

15. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SAP Single Points of Failures (SPOFs)
SAP HANA
SAP ASCS
Instance
SAP
WebDisp.
Instance
Shared
Files
Network
Storage
Servers

16. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
Data &
Log
SAP App
Server(s)
SAP HAF
Cluster
Fail-over
SAP HANA
Host Auto-Failover (HAF)
DataCenter
/hana/shared
Stby
SAP HANA
Server
Stby
SAP ASCS
Server
SAP App
Server(s)
Legend
Not Running
Running
SAP HANA H.A. components (on-premises)

17. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SAP HANA H.A. components (on-premises)
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
Disk
SAP App
Server(s)
SAP HSR
Cluster
Fail-over
SAP HANA
System Replication
DataCenter
Disk
Stby
SAP HANA
Server
Stby
SAP ASCS
Server
SAP App
Server(s)
Legend
Not Running
Running

18. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SAP HANA H.A. options in AWS
Amazon
EC2 Auto
Recovery
Warm
Standby
Single AZ
H.A.
Multi-AZ
H.A.

19. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Amazon EC2 Auto Recovery
SAP HANA
Server
Amazon
CloudWatch
1
3
Availability Zone A
2
Detect and
Restart
Availability Zone B
CloudWatch
monitors EC2
instance health
EC2 instance
restarted
1
3
2
Detect and
Restart
SAP HANA
(master)
EC2 instance
restarted
SAP HANA
(worker)
SAP HANA
(worker)
Legend
Not Running
Running
CloudWatch
monitors EC2
instance health
Amazon EC2
instance
Amazon EC2
instance

20. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Uptime: MTTR of minutes
Cost: CloudWatch Alarm only (~$1 per
month/instance)
Complexity: Low. CloudWatch monitor, detects and
responds to failures
Consideration: Systems restart in the same AZ
Does Auto Recovery work for you?

21. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm Standby
Amazon
CloudWatch
Availability Zone A Availability Zone B
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
SAP HSR
x1e.32xlarge r4.8xlarge
(pre-load off)
CloudWatch
monitors EC2
instance health
Amazon EFS
(/sapmnt)
AMI
snapshots
Stby
SAP HANA
Server1
Legend
Not Running
Running
Stby
SAP ASCS
Server

22. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm Standby failover
Amazon
CloudWatch
Availability Zone A Availability Zone B
SAP HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
x1e.32xlarge r4.8xlarge ->
x1e.32xlarge
CloudWatch
monitors EC2
instance health
1
SAP HANA
Server
SAP ASCS
Server
SAP App
Server(s)
Start ASCS
instance
Start PAS+AAS
instance(s)
DNS updates
Re-size + SAP
HSR takeover

23. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Uptime: MTTR can be minutes or longer
Cost: Cost optimized. Low $ for warm resources
Complexity: Use 3rd Party partners solutions or you may
use custom scripting for detection and fail-over
Consideration : HSR take-over and SAP startup required
Does Warm Standby work for you?

24. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Single AZ H.A.
Amazon
CloudWatch
Availability Zone A
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge
3rd Party
Clustering
x1e.32xlarge
1
CloudWatch
monitors EC2
instance health
Stby SAP
HANA
Server
Stby
SAP ASCS
Server
Legend
Not Running
Running
Amazon EC2
instance

25. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Single AZ H.A. failover
Amazon
CloudWatch
Availability Zone A
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge
CloudWatch
monitors EC2
instance health
1
3rd Party
Clustering
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
x1e.32xlarge
CloudWatch
monitors EC2
instance health
1
Start ASCS instance +
ENQ table re-attach
SAP HSR take-over
Amazon EC2
instance

26. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Uptime: MTTR of minutes
Cost: Medium $$. Hot SAP HANA resource.
Complexity: Medium, requires 3rd party clustering.
Consideration : Only fail-over systems in the same AZ
Does Single AZ work for you?

27. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-AZ H.A.
Amazon
CloudWatch
Availability Zone A Availability Zone B
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge x1e.32xlarge
CloudWatch
monitors EC2
instance health
CloudWatch
monitors EC2
instance health
1 1
3rd Party
Clustering
SAP App
Server(s)AAS instances
Stby
SAP HANA
Server
Stby
SAP ASCS
Server
Legend
Not Running
Running

28. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-AZ H.A. failover
Amazon
CloudWatch
Availability Zone A Availability Zone B
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge x1e.32xlarge
CloudWatch
monitors EC2
instance health
CloudWatch
monitors EC2
instance health
1 1
3rd Party
Clustering
SAP App
Server(s)AAS instances
Stby
SAP HANA
Server
Stby
SAP ASCS
Server
Legend
Not Running
Running

29. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-AZ H.A. failover
Amazon
CloudWatch
Availability Zone A Availability Zone B
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge x1e.32xlarge
CloudWatch
monitors EC2
instance health
CloudWatch
monitors EC2
instance health
1 1
3rd Party
Clustering
SAP App
Server(s)AAS instances
Primary
SAP HANA
Server
Stby
SAP ASCS
Server
Legend
Not Running
Running
SAP HSR take-over

30. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-AZ H.A. failover
Amazon
CloudWatch
Availability Zone A Availability Zone B
Primary SAP
HANA
Server
Primary
SAP ASCS
Server
SAP App
Server(s)
3rd Party
Clustering
x1e.32xlarge x1e.32xlarge
CloudWatch
monitors EC2
instance health
CloudWatch
monitors EC2
instance health
1 1
3rd Party
Clustering
SAP App
Server(s)AAS instances
Primary
SAP HANA
Server
Primary
SAP ASCS
Server
Legend
Not Running
Running
Start ASCS instance +
ENQ table re-attach
SAP HSR take-over

31. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Uptime: Low MTTR
Cost: Higher $$$. Hot resources
Complexity: Highly integrated and orchestrated solution
from 3rd party partner
Consideration : Supports Multi-AZ scenarios and is the
most complex architecture
Does Multi-AZ work for you?

32. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Summary of SAP HANA H.A. options
Cost and
Complexity
Failures
Scenarios
covered
Highest Uptime
EC2 Auto
Recovery
Warm
Standby
Single AZ
Multi-AZ

33. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Auto recovery lessons learned
Utilize the AWS SAP HANA Quick Start to automatically set up EC2 Auto
Recovery
The service costs about $1 per month for every EC2 instance activated on
Use on SAP application servers at a bare minimum
Test it—use AWS Business Support or an AWS Technical Account Manager
• Timing
• OS settings
• Cluster configuration

34. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Warm standby lessons learned
Disk size of standby system = disk size of source system
Standby EC2 instance size driven by:
• Row store and/or loaded column tables of the primary HANA DB
• Use SAP DOC-47702 to calculate the standby HANA size
• We’ve seen customer standby systems 15x smaller than the source HANA
system
Procure a separate EC2 instance for a warm standby setup
• Benefit over standard “cost optimized” on premise setup

35. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Single AZ lessons learned
Offers lower levels of HANA DB latency than two AZ setup:
• Useful when using HANA HSR in synchronous mode and high change rates
Does not qualify for the EC2 SLA’s:
• Does not pass AWS Well-Architected
Primary cost difference with multi-AZ is the $00.02 per GB inter-AZ data transfer
cost
Typically we’ve seen total networking costs are well under 5% of your total bill

36. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Multi-AZ lessons learned
Use of overlay IP address is a requirement:
• On premises users can only reach the overlay IP via NLB/ELB or Amazon Route 53
Pay extra care in configuring your cluster:
• There can false positives if a cluster is not configured correctly
• AWS Professional Services or AWS Partner Network can expedite and safeguard
the HA setup

37. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
THANK YOU!