SGI SAPPHIRE 2016 Presentation: Optimal Scale-up HA/DR Landscape

1 SGI May 2016 SGI May 2016

Peter Put

SAP Architect

Optimal Scale-Up HA/DR Landscape

2 SGI May 2016 2 SGI May 2016

SGI HA/DR Solutions

• Tailor solutions to match your budget and SLA requirements

– From Simple Backup to 5 nines with 3-Site Replication

• Maintain SLA as you scale without adding complexity or operational cost

– Scale solutions with a single node environment.

• Simplify HA/DR deployment with native tools

– No need for third party storage replication (HANA System Replication)

– Automate Failover (SUSE Auto Failover)

– No additional cost for replication licenses

3 SGI May 2016 3 3 SGI May 2016

Measuring HA/DR Optimization Backups Storage Replication Host auto-failover

System Replication

Cost Lowest 2x Storage + Rep SW Shared Storage/Standby node

2x System Cost

Complexity Low High Medium Medium

RPO Most recent BU Zero/Low - with (sync/async) Medium Zero

RTO Configure/Restore/Cold Boot/Load Days to Hours

Configure/Cold Boot /Data Load time 15 minutes to an hour

Data Load time Near Immediate - Preload

Performance Gap (brownouts)

Can take hours to load column data and reach full performance

Can take hours to reach full performance

Yes No

Network Requirements Medium High Bandwidth Dedicated Link between storage systems, less efficient than system rep.

Medium Medium

Storage Complexity Uses existing BU System 2x Shared Storage Shared Storage Direct Attached*

3rd Party Tools Required Recommended 3rd Party Replication required Native Native

Live Standby System No Yes, one or more shared Yes, one or more shared

Yes, Dedicated

Synchronous Supported Distance

N/A Up to 100km 50km 50km

4 SGI May 2016 4 SGI Confidential – April, 2016 4 SGI May 2016

HA/DR for SAP® HANA®

Sync or Backup

Sync or Backup

System Operational

RPO

System Operational

Prepare

RTO

Performance Ramp

Recover Detect

time

Solution Use Cost Complexity RPO RTO Perf. Ramp

Backup and Recovery Local, DR $ Low Med – High High N/A

SAP HANA Host Auto-Failover* HA $ Med 0 (sync) , Low (async Med Long

SAP HANA Storage Replication DR $$ Med 0 (sync) , Low (async) Med Long

SAP HANA SN System Replication HA & DR $$ Low 0 (sync) , Low (async) Low Short

SN = single node; *applicable to clusters

• Recovery Point Objective (RPO) = Worst Case Data Loss • Recovery Time Objective (RTO) = Time to completely recover from outage

http://www.google.com/url?url=http://blog.zenoss.com/2013/02/4-non-obvious-costs-of-downtime/&rct=j&frm=1&q=&esrc=s&sa=U&ei=HjW0U-fbO6HJsQTBiYGIAw&ved=0CCoQ9QEwCg&usg=AFQjCNHZSx_mISuDr5Kp0yx-_TU7jNzEvg

5 SGI May 2016 5 5 SGI Confidential – March, 2015

• Intel and SGI RAS

• Component redundancy

• SGI Memlog

• SGI NUMAlink resilience

• Widely proven/stress-tested

Maximize Service Levels

75+ SGI UV 300H systems deployed with 99.996% uptime

6 SGI May 2016 6 6 SGI May 2016

Transient Error Filter

Predictive Failure

Analysis

Proactive Action: Data moved from

bad to healthy memory

System Log

SGI® MEMlog™ Software


Alerts to System Admin & SGI

Remote Services

Replace memory at

next scheduled

maintenance window

7 SGI May 2016 7 7 SGI May 2016

Maximize Capacity

vs. consuming capacity with DIMM sparing or mirroring

Lower Costs

avoid unnecessary time and expense replacing DIMMs

Maintain Uptime

minimize planned and unplanned

downtime


8 SGI May 2016 8 8 SGI May 2016

HA/DR for SAP® HANA®

Sync or Backup

Sync or Backup

System Operational

RPO

System Operational

Prepare

RTO

Performance Ramp

Recover Detect

time

Solution Use Cost Complexity RPO RTO Perf. Ramp

Backup and Recovery Local, DR $ Low Med – High High N/A

SAP HANA Host Auto-Failover* HA $ Med 0 (sync) , Low (async Med Long

SAP HANA Storage Replication DR $$ Med 0 (sync) , Low (async) Med Long

SAP HANA SN System Replication HA & DR $$ Low 0 (sync) , Low (async) Low Short

SN = single node; *applicable to clusters

• Recovery Point Objective (RPO) = Worst Case Data Loss • Recovery Time Objective (RTO) = Time to completely recover from outage

http://www.google.com/url?url=http://blog.zenoss.com/2013/02/4-non-obvious-costs-of-downtime/&rct=j&frm=1&q=&esrc=s&sa=U&ei=HjW0U-fbO6HJsQTBiYGIAw&ved=0CCoQ9QEwCg&usg=AFQjCNHZSx_mISuDr5Kp0yx-_TU7jNzEvg


UV 300H HA Implementation HANA DB Replication with SUSE or Red Hat Auto Failover

SYSTEM BENEFITS

• RTO = 2 mins

• RPO = zero data loss

• Low complexity

Failover Node

Primary Node

Data Log

Linux Auto Failover

Synchronous Replication

Persistent storage for Data (if power loss) and Log files

• SGI storage in rack (appliance)

• 3rd party storage (SAP TDI)

Data Log


UV 300H 3-Tier HA/DR Implementation HANA DB Replication with SUSE or Red Hat Auto Failover (local)

HA Failover

Node Primary Node

Data Log

Linux Auto Failover





Data Log

DR Failover

Node

SYSTEM BENEFITS

• RTO

− 2 mins (HA)

− Minutes (DR)

• RPO

− Zero data loss (HA)

− Near zero loss (DR)

• Low complexity

• Ideal for near zero

downtime SLA target

Asynchronous Replication

Data Log


UV 300H 3-Tier HA/DR Implementation HANA DB Replication with SUSE or Red Hat Auto Failover (local)

HA Failover

Node Primary Node

Data Log

Linux Auto Failover





Data Log

DR Failover

Node

Data Log

SYSTEM

BENEFITS • RTO

− 2 mins (HA)

− Minutes to hrs (DR)

• RPO

− Zero data loss (HA)

− Near zero loss (DR)

• Low complexity

• Ideal for near zero

downtime SLA target

• Maximize resources

Asynchronous Replication

Data Log

Test / Dev

Production

Test/ Dev

~10% system

overhead

Utilize system for Test & Development

12 SGI May 2016 12 SGI May 2016

• Data Replication

– SAP HANA System Replication

– HANA Studio (or command line)

– After full backup, configure replication

Implementing HA Protect Against System Failure for Five 9’s Availability

13 SGI May 2016 13 SGI May 2016




– After full backup, begin replication


14 SGI May 2016 14 SGI May 2016






15 SGI May 2016 15 SGI May 2016





• Failover

– Trigger “takeover” using

HANA Studio or CL

– Automate using SUSE or RHEL

HA tools


www.sgi.com/products/servers/uv/uv_300h.html

16 SGI May 2016 16 SGI May 2016

Implementing DR Protect Against Site Failure


– Similar process as HA, enabling

HANA system replication from

secondary server


17 SGI May 2016 17 SGI May 2016





secondary server


18 SGI May 2016 18 SGI May 2016





secondary server


• Failover

– Trigger “takeover” using

HANA Studio or CL

– Reassign vIP manually

>100 KM - Asynchronous

19 SGI May 2016 19 SGI May 2016

Re-establish Primary System/Site HA/DR Configurations

• Configure System Replication

– Replicate from “secondary” to primary

– HANA will replicate data since last

backup/snapshot on primary (delta)

– Can “seed” new system with backup

(ship media and upload data), then

replicate delta

• Trigger takeover

– Re-establish HA and DR environment

as necessary

20 SGI May 2016 20 SGI May 2016

White Paper

at sgi.com

21 SGI May 2016 21 SGI May 2016

HA/DR Solutions Meet Mission Critical SLA’s

• Tailor to your SLA requirements

– From simple backup to 3-way replication and Five 9’s availability

• Maintain SLA as you scale without adding complexity

or operational cost

– Simplicity of single-node environment

• Simplify HA/DR deployment with native tools

– SAP HANA Studio

– Automate Failover (SUSE HA tools)

– No additional licensing costs

22 22 SGI/SAP Confidential – March 2015 22 SGI May 2016

SGI Advantage

• In-memory computing experts

• Proven, 7th generation

technology

• Seamless, near-limitless

capacity in a single node

• THE mission-critical platform

• Future-ready design

• Rapid, high-touch deployment;

HANA appliance or TDI

• On-premise or in the Cloud

23 23 23 SGI May 2016

Devices & Hardware

SGI SAPPHIRE 2016 Presentation: Optimal Scale-up HA/DR Landscape