HANA Volumes & Sizes under considerationHPE’s proposes deploying the following infrastructure based on Philips inputs and some assumed sizes

1

Environment Location Application Servers/VMs SAPS

HANA Capacity in TB assumed (to be verified before Go-Live)

Production (PR4) Primary DC 48000 8

Dual Purpose DR (PR4) Secondary DC 48000 8Pre-production (TP4) Primary DC 2000 1

Quality Assurance (TQ4) Secondary DC 8000 1

Prod Dev (TD1)Runs on Dual

Purpose in Secondary DC

4000 2 (runs on Dual Purpose DR)

o Dual Purpose DR for HANA Appliance where the DR HANA Appliance will run/ host couple of Non-prod environments thereby saving Customers additional costs for such HANA HW needed to host Non-production environmentso For Non-Production HANA instances, leverage SAP’s MCOS (Multiple Components on One Systems) where single appliance (Dual Purpose DR) will host Pre-prod & Quality.o Incase customer opts for Dedicated DR, then customer will need to order more Non-Production Capacity as HPE won’t

be in a position to accommodate Non-Prod on DR HANA HW.o Propose 2 separate 100% Application Servers/VMs for Production and DR to ensure 100% DR capacity on both fronts i.e.

Application Servers and HANA Appliances.o However customer can opt for cluster of Application Servers of 50%-50% spread across Production and DR sites. But

in this case, if there is DR, Philips Lighting will only be able to utilise 50% of the SAPS capacity.

High Availability & Dual Purpose DR solution with transport pathsPrimary DC Prod & Pre-prod

Secondary DC Dual Purpose DR (Dev) & QA

Pre-ProdHANA

DataVolumes

QA HANA

DataVolumes

QA App ServerPre-prod

App Server

Dev App Server

Prod App Server

DR App Server

Potential HANA HA/DTS Scenarios with Serviceguard

Sing

le-h

ost:

war

m

cold

war

m

war

m

cold

cold

idle

idle

idle

Scal

e-ou

t: HANA System Replication: 3par Storage Replication: HA (w/o replication):

cold

or id

le

cold

idle

LAN

SAN

DWDM

*

DWDM

*

Quorum Server (at 3rd Site)

Site 1 Site2*

0 - ~50 km: sync or async

> ~50km: async

Primary SAP HANA Package

Secondary SAP HANA Package

Local Storage HP D2700

Local Storage HP D2700

HANA system replication

HANA system replication HA/DTS cluster

*=optional

data LANreplication LAN

Dual purposing HANA system

PrimaryHANA

Instance(active)

primarypackagehdbprimary hdbinstance

hdbdualpurpose

relocatable ipprios & deps

sapstartsrv

SYS

data/log ofprimary

SecondaryHANA

Instance(replicating)

secondarypackagehdbinstance prios & deps

sapstartsrv

SYS

data/log of secondaryQuoru

mService SYS

non-prodHANA

Instance(s)(active)

sapstartsrv

data/log of non-prod

cluster node A cluster cluster node B

Failover

Halt

Start

Stop

TakeoverRole-reversal

Production replication & non-production use

SAP Requirements to supportdual purposing configurations:

- shutdown of non-production instances before takeover needs to be ensured

- deactivation of table pre-load- separate i/o subsystem

for non-production instances

Serviceguard for Linux

Q

Primary SAP HANA Package

SecondarySAP HANA Package

sync SAP HANA System Replication

0 - ~50 KM: sync or async

>~50KM: async

Single-Host HP AppSystem

Data LAN

Quorum Server

Replication LAN

Single-Host HP AppSystem

HP D2700

HP D2700

Ack

local instance restart in case of failurefailover & takeover in case of failure

Synchronous HANA system replication clusterStandard operation with consistent failover mechanism (RPO=0)

DC 1

Single-host HANA system replication HA cluster

Shared under CDA

SGeSAP Cluster

PrimaryHANA

Instance(active)

hdbprimary

hdbinstance

package_ip

prioritydependenc

ysapstartsrv

SYS

data/log of

primary

SecondaryHANA

Instance(replicating)

hdbinstance priority

dependency

sapstartsrv

SYS

data/log of

secondary

Package 2Package 1

Quorum

Service

failover

takeover

• the HANA instances are installed on fixed hostnames• the HANA instances use direct-attached storage,

replicated via LAN using SAP HANA system replication• the solution configures two Serviceguard failover

packageswith mutual exclusion dependency

• one of the packages represents the primary token- it automatically triggers actions to ensure that the node-local HANA instance is up and running as primary system- it triggers HANA takeover operations and promotes a sync’ed secondary system in case of primary failure- it ensures client-access to the primary via a relocatable ip

• one of the packages represents the secondary token- it automatically triggers actions to ensure that the node-local HANA instance is up and running as secondary system

• Serviceguard quorum services must be connectedfrom separate hardware

Token failover with identity switch instead of instance failover

The content of this slide is subject to change without notice.

SGeSAP Cluster

Single-host HANA system replication HA cluster

PrimaryHANA

Instance(active)

primarypackagehdbprimar

y hdbinstanc

er-ip/prio/de

psapstartsrv

SYS 1

data/log ofprimary

SecondaryHANA

Instance(replicating)

secondarypackage

hdbinstance prio/dep

sapstartsrv

SYS 2

data/log of secondaryQuoru

mService

failover

takeover

demotion

• the HANA instances are installed on fixed hostnames• the HANA instances use direct-attached storage,

replicated via LAN using SAP HANA system replication• the solution configures two Serviceguard failover

packageswith mutual exclusion dependency

• one of the packages represents the primary token- it automatically triggers actions to ensure that the node-local HANA instance is up and running as primary system- it triggers HANA takeover operations and promotes a sync’ed secondary system in case of primary failure- it ensures client-access to the primary via a relocatable ip

• one of the packages represents the secondary token- it automatically triggers actions to ensure that the node-local HANA instance is up and running as secondary system

• Serviceguard quorum services must be connectedfrom separate hardware

Token failover instead of instance failover

The content of this slide is subject to change without notice.

DC St. Leon-Rot (Active)DC 1

SG Concept for 2nd gen HANA Scale-Out, HA & DT

locallysharedstorageSYS

DC St. Leon-Rot (Active)

HANANode Iactive

HANANode IIactive

HANANode

IIIactive

HANANode

IVstandb

ySG HAProvide

r

SG HAProvide

r

SG HAProvide

r

SG HAProvide

rhdbrole

storage I

hdbrole

storage II

hdbrole

storage III

affinityhdbshare HA NFS SYS

storage Istorage II

storage III

affinityhdbshare HA NFS

locallysharedstorage SYS

hdbinstance multinode packageHA APIHA APIHA APIHA API

hdbrole

hdbrole

hdbrole

HANANode Iactive

HANANode IIactive

HANANode

IIIactive

HANANode

IVstandb

y SG HAProvide

r

SG HAProvide

r

sapstartsrv

sapstartsrv

sapstartsrv

sapstartsrv

SG HAProvide

r

SG HAProvide

r

hdbprimary

hdbip hdbip hdbip hdbip hdbip hdbiphdbip hdbip

hdbinstance multinode packageHA APIsapstar

tsrv

HA APIsapstartsrv

HA API HA APIsapstartsrv

sapstartsrv

storage I storage II

storage III

hdbprimary

DC 2Quorum

Service

Serviceguard for Linux

Q

Primary SAP HANA Package

SecondarySAP HANA Package

sync SAP HANA System Replication

0 - ~50 KM: sync or async

>~50KM: async

Single-Host HP AppSystem

Data LAN

Quorum Server

Replication LAN

Single-Host HP AppSystem

HP D2700

HP D2700

Ack

local instance restart in case of failurefailover & takeover in case of failure

Synchronous HANA system replication cluster (I)Standard operation with consistent failover mechanism (RPO=0)

Impact of packaging options and configuration awareness on deploysappkgs

Architecting the Netweaver Package Topology

Scenario:

Packaging Option:

Software component

No constraintsSAP configuration

awareness example:SCS and ASCS on same virtual

hostname

SG configuration awareness example:

SCS and ASCS already in different packages

Multiplepackage

s

Combined

packages

Multiplepackages

Combined

packages

Multiplepackages

Combined

packages

Standard hardware

Database PKG1

PKG1

PKG1

PKG1

PKG3

PKG1 NFS PKG2 PKG2 PKG4 ABAP Central

Services PKG3PKG3

PKG1

JAVA Central Services PKG4 PKG2 PKG2

Replication of ABAP CS PKG5

PKG2 PKG4 PKG2PKG5 PKG3

Replication of JAVA CS PKG6 PKG6 PKG4

Enqor MNPPKG7 PKG3 PKG5 PKG3 PKG7 PKG5

AppSystem

Primary HANA db PKG1 PKG1 PKG1 PKG1 PKG1 PKG1Secondary HANA

db PKG2 PKG2 PKG2 PKG2 PKG2 PKG2

Shared under CDA