Data Center Readiness for HANA Part 2 DR and BC

Place photo here

© 2013 IBM Corporation

Richard T. Travis Data Center Readiness for HANA

1

Place photo here

© 2013 IBM Corporation

Oliver Rettig Richard Travis

Architecture Options for Business Continuity of SAP HANA systems

2

© 2013 IBM Corporation © 2013 IBM Corporation

Topics

•  The SAP HANA Project Process –  How we get into trouble from the outset.

•  SAP HANA Use Cases: –  Why they are important

•  Data Center Critical Considerations –  Backup and Recovery

–  High Availability –  Disaster Recovery –  Business Continuity

•  Q & A

3


The SAP HANA Project Process

Functional Business IT and Facilities

Engage All Parties in Parallel

FIRST EARLY

ALWAYS


SAP HANA Deployment Options for Different Use Cases

5

Technology Platform

SAP HANA

BI Clients

SQ L MD

X BIC

S 3rd Party

Non SAP Data Source

In-Memory

Compu?ng Engine

Data Modeling

ETL

Reporting

Accelerators

SAP HANA

BI Clients

SQL

MD

X BICS

3rd Party

Replica?on

SAP Business Suite

Tradi?onal DB

In-Memory

Compu?ng Engine

Data Modeling

SAP HANA

Read

SAP Business Suite

SAP UI

Tradi?onal DB

In-Memory

Compu?ng Engine

Data Modeling

Replica?on

e.g. Demographics & Google Maps

e.g. SAP ERP: Operational reporting

e.g. SAP ERP: CO-PA


SAP HANA Deployment Options for Different Use Cases

6

Products on In-Memory DB

SAP HANA

BW

Tradi?onal Extractors

SAP Business Suite

Tradi?onal DB

In-Memory

Compu?ng Engine

e.g. SAP BW -7.3 SP8- on HANA

Products on In-Memory DB

SAP HANA

ERP, SCM, CRM

In-Memory

Compu?ng Engine

e.g. SAP ERP 6.0, EHP6, CRM 7.0, EHP2, SCM 7.0 EHP2, Version for HANA


Use Case Deployment

• Use Cases Have Different Requirements –  Scale Up –  Scale Out –  Master Node Consideration

• Requirements Determine Architecture/Deployment –  Standalone/Scale up –  Multinode/Scale out –  High Availability Design –  Disaster Recovery Approach –  –  – 


High Availability


HDD replica (Disk)

- index server - statistic server

- SAP HANA® DB worker node

Standby Node 512GB

Production Node 2 512GB

FAILED Node 2 512GB

- SAP HANA® DB standby node - SAP HANA® DB worker node

X3950 7143-HBU (512GB)



shared filesystem - GPFS

HDD flash

data02 log02

data03(3)

log01(1)

log03(3)

data01(1)

data03(3)

log01(1)

log03(3)

data01(1)

HDD flash

data02 log02

data01(1)

data03(3)

log01(1)

log03(3)

HDD flash

log01

DB partition 1

- index server - statistic server - SAP HANA® studio


HDD flash

log03(3) log03

DB partition 3

flash



data03

HDD flash


X3950 7143-HBU (512GB)

X3950 7143-HBU (512GB)

X3950 7143-HBU (512GB)

Production (scale to 56 Nodes)

data01(2) data01(3) data02(1) data02(3)

data03(1) data03(2)

Log Replica (SSD)

log01(2) log01(3) log02(1) log02(2) log02(3)

log03(1) log03(2)

data01(2) data01(3) data02(3)

data03(1) data03(2)

log01(2) log01(3) log02(1) log02(2) log02(3)

log03(1) log03(2)

data02(2) data02(2)

log02(2) log02(1) log02(3)

data02(3)

data01(1) data01 Primary Data (SSD & Disk)


data02(1)

SAP HANA Appliance – Scale Out with High Availability

9





DB partition 2

SAP HANA® DB

System Memory

X3950 7143-HBU (512GB)


Datacenter 2

Datacenter 1

HANA Standby node

Stretched HA (single node), up to metro distance

•  Two data centers in metro distance (dependent on network latency and bandwidth)

•  1 + 1 + quorum, no non-prod system allowed on secondary site

•  Quorum node ideally at third location, frequently installed at primary location

•  Automatic failover with GPFS functionality, one GPFS cluster

•  For BW on HANA and Suite on HANA

10

HANA Worker node

Primary replica

Secondary replica

Quorum


HANA Stretched HA with GPFS – Network setup

11

SAP HANA ACTIVE NODE SAP HANA

STANDBY NODE

QUORUM NODE ISL

HANA cluster network GPFS network

Datacenter 1 Datacenter 2

Datacenter 3


HA for single node configs in one DC SAP HANA system replication

•  Low RTO, because the data is already active in memory in the secondary system

•  Independent of the HW implementation

• Manual failover or additional cluster failover functionality

• Applicable for all use cases

12


Disaster Recovery Business Continuity


Datacenter 1

Datacenter 2

DR Single node: with GPFS (synchronous)

•  Two data centers in metro distance (dependent on network latency and bandwidth)

•  1 + 1 + quorum (one GPFS cluster) On the secondary site the HANA instance is not started, secondary site can be used for ONE different SAP HANA system (e.g. Non-prod) with storage expansion (EXP2524)

•  Quorum node ideally at third location, frequently installed at primary location

•  Manual failover

•  For BW on HANA and Suite on HANA

14

HANA Worker node

Quorum

HANA Standby node

Non-prod HANA

Primary replica

Secondary replica


DR Scale out: GPFS Replication (synchronous) aka. Storage Replication

•  SAP Note 1755396 •  Synchronous replication •  Secondary site (identical setup active + standby) can be used for a

different SAP HANA system (e.g. Non-prod) with storage expansion •  Not applicable for Suite on HANA

15

Datacenter 1

Datacenter 2


DR Scale out: SAP HANA Synchronous System Replication

•  Low RTO, because the data is already active in memory in the secondary system


•  Independent of the use case

16


DR Scale out: SAP HANA Synchronous System Replication (available with SPS 6)

• Similar as before, but on the secondary site a non-prod system can run (duplicate persistence required)

•  Higher RTO, because „Table pre-load“ is turned off


•  Independent of the use case

17


DR Single Node and Scale Out: SAP HANA Asynchronous System Replication (available with SPS 6)

• 

18

Long distance


GPFS and Disaster Recovery


GPFS introduced concurrent file system access from multiple nodes.

Evolution of the global namespace: GPFS Active File Management (AFM)

Multi-cluster expands the global namespace by connecting multiple sites

AFM takes global namespace truly global by automatically managing asynchronous replication of data

GPFS GPFS

GPFS

GPFS

GPFS

GPFS

1993 2005 2013


AFM Mode: Single-Writer

• Data written to a cache • Asynchronous replication back to home

• Can have multiple read-only caches

RW

Single-Writer

RO RO RW


AFM Mode: Asynchronous Replication (GPFS TL-2)

• Asynchronous Replication in HA Pair – Cache site does the writing – Home site is failover

• Cache Fails – New cache can be defined

• Home Fails – New Home can be defined

High Availability

RW

RO


Q & A


Thank you for your Attention

24

•  IBM's SAP Alliance page – http://www.ibm-sap.com

•  SAP’s IBM Alliance page – http://service.sap.com/ibm

Richard T. Travis SAP Infrastructure Architect!"!IBM ATS!

4 Center Court!Bay City, MI!!

Phone (720) 395-1579!Mobile (989) [email protected] !

© 2013 IBM Corporation © 2013 IBM Corporation 25

IBM Systems solution for SAP HANA sizes / building blocks / upgrade path

Size XS S S+ M L

Building Block x3690 X5 x3690 X5 x3950 X5 x3950 X5 x3950 X5

Part Number (Sys x - config)

7147-HAx 7147-HBx 7143 - HAx 7143 - HBx 7143 – HBx + 7143 – HCx

Intel CPU 2 x E7 2870 2 x E7 2870 2 x E7-8870 4 x E7-8870 8 x E7-8870

RAM 128 GB DDR3 (8 x 16GB)

256 GB DDR3 (16 x 16GB)

256 GB DDR3 (16 x 16 GB)

512 GB DDR3 (32 x 16 GB)

1 TB DDR3 (64 x 16 GB)

Log Storage 10 x 200 GB 1.8‘‘ MLC SSD

10 x 200 GB 1.8‘‘ MLC SSD

1.2 TB ioDrive2 FusionIO 1.2 TB ioDrive2 FusionIO 2 x 1.2 TB ioDrive2 FusionIO

Data Storage - - 8 x 900 GB 10k SAS HDD 8 x 900 GB 10k SAS HDD 16 x 900 GB 10k SAS HDD

Storage Ctrl 2 x M5015 2 x M5015 1 x M5015 1 x M5015 2 x M5015

Data / Log Storage Summary

1.6 TB RAID 5 data and log storage

1.6 TB RAID 5 data and log storage

5.4 TB RAID5 data storage 1 TB log storage



Ethernet 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 4 x 10 GbE, 6 x 1 GbE 8x 10 GbE, 12 x 1 GbE

Upgrade Option Scale Up or Scale out

XS - > S Up to 16 node scale out with HA, SAP certified

S+ à M M à „XM“ and L (with L-option) Up to 56 node scale out with HA, SAP certified

L à XL or XXL Up to 56 node scale out with HA, SAP certified

Software Preload: SLES4SAP GPFS SAP HANA

Preload: SLES4SAP GPFS SAP HANA



Preload: Addtl. GPFS lic.

© 2013 IBM Corporation © 2013 IBM Corporation 26

IBM Systems solution for SAP HANA

Size „XM“ XL XXL

Building Block x3950 X5 x3950 X5

Part Number (Sys x - config)

7143 - HDx 7143 – HDx + 7143 – HEx

7143 – HDx + 7143 – HEx + add. storage

Intel CPU 4 x E7-8870 8 x E7-8870 8 x E7-8870

RAM 1 TB DDR3 (64 x 16 GB or 32 x 32 GB)

2 TB DDR3 (128 x 16 GB or 64 x 32 GB)

4 TB DDR3 (128 x 32 GB)

Log Storage 1 x 1.2 TB ioDrive2 FusionIO

2 x 1.2 TB ioDrive2 FusionIO 4 x 1.2 TB ioDrive2 FusionIO

Data Storage 8 x 900 GB 10k SAS HDD

16 x 900 GB 10k SAS HDD 24 x 900 GB 10k SAS HDD

Storage Ctrl 1 x M5015 2 x M5015 2 x M5015, 1 x M5025

Data / Log Storage Summary




Ethernet 4 x 10 GbE, 6 x 1 GbE 8 x 10 GbE, 12 x 1 GbE 8x 10 GbE, 12 x 1 GbE

Upgrade Option Scale Up

„XM“ à XL XL à XXL (with additional memory, ioDrive2, M5025, EXP 2524)

Software Preload: SLES4SAP GPFS SAP HANA



Single node only for SAP Business Suite on HANA

Date post:	11-Nov-2014
Category:	Travel
Upload:	sap-community-network
View:	1,582 times
Download:	2 times

Data Center Readiness for HANA Part 2 DR and BC

Travel