#SAPWEEK - Stockage de données, infrastructures ... · EMC CONFIDENTIAL—INTERNAL USE ONLY 3 HANA INFRASTRUCTURE : THE KEY DESIGN TOPICS HANA instances size and usage Disaster (BW

#SAPWEEK

PARIS, LE 7 APRIL 2016

REPENSEZ VOTRE STRATÉGIE SAP ET ENTREZ DANS LE CLOUD

HYBRIDE Paul Dunon – SAP Champion Cisco Dimitri Catanese – Consultant EMC

2

AGENDA

MÉTHODOLOGIE & EXPÉRIENCES SAP HANA TDI

QUESTIONS & RÉPONSES

3 EMC CONFIDENTIAL—INTERNAL USE ONLY EMC CONFIDENTIAL—INTERNAL USE ONLY

HANA INFRASTRUCTURE : THE KEY DESIGN TOPICS

HANA instances size and usage

(BW or SoH)

Scale-up or scale-out ?

Mutualization (MCOS, MDC, VMWare) ?

Appliance or TDI ?

Data Tiering ?

External Storage choice ?

Backup

Strategy ?

High Availability

and Disaster

Recovery ?

Certified server (E7)

or supported server (E5) ?


HANA INSTANCES SIZE AND USAGE

• Usage : BW or SoH ?

• Environments: production, pre-production, integration, test, dev, …

• How are the non-prod environments refreshed ?

• Include growth

• Archive old data before migrating to HANA ?




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




SCALE-UP OR SCALE-OUT

• The rule « Scale-up first, then Scale-out » is not automatically the best technical and economical choice

• Cisco UCS greatly simplify deployment and operation of HANA Scale-Out

• HANA Scale-out natively includes H/A (host auto-failover)

• SoH scale-out is in controlled availability

• Beyond 4 sockets, server price is exponential

• Large server = long boot time




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




HANA HARDWARE MUTUALIZATION TECHNIQUES

standard MCOS

(Multiple Component – One System

Virtualization VMWare

MDC (Multi-tenant

Database Container)

MDC-enabled

Tenant Tenant


HANA HARDWARE MUTUALIZATION TECHNIQUES

• Carefully evaluate operational constraints before choosing a mutualization technique !

• Multiple productive HANA VMs now supported on Vsphere 5.5

• HANA MDC still has limitations




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




APPLIANCE OR TDI ?

• Understand the differences

• HANA TDI on Cisco UCS is similar to a Converged Infrastructure (vBlock)

• Cisco offers the same support service for appliance and TDI




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




DYNAMIC TIERING

• HANA Dynamic Tiering requires external storage

• Proper sizing of extended storage host is difficult




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




SAP HANA

System Throughput

Latency

Cost CAPEX + OPEX = ROI ???

RTO & RPO

Manageability / Automation

TODAY LATENCY & THROUGHPUT ARE “NON-NEGOTIABLE” REQUIREMENTS

SAP HANA TDI RULES FOR STORAGE

SAP’s Requirements Link: SAP Note 1943937

https://service.sap.com/sap/support/notes/1943937


THE BROADEST PORTFOLIO IN THE INDUSTRY

EMC SOLUTIONS FOR SAP HANA


WHAT NEEDS TO BE BACKED UP?

• HANA System Backup includes:

– HANA Data Backups

– HANA Log Backups

– HANA Backup catalog

• But does not include:

– Content of the HANA Log files for the last transactions not yet backed up

– HANA Configuration files

– OS Image + OS configuration files + HANA binaries

• What about applications other than HANA? – Currently possible to have Netweaver and HANA on the same server

WHAT IS INCLUDED IN THE HANA SYSTEM BACKUP


EMC BACKUP SOLUTIONS FOR HANA


FACTORY BUILT, SINGLE POINT OF SUPPORT… IN A SHARED INFRASTRUCTURE!

VBLOCK SYSTEMS FOR SAP HANA

TDI




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




HIGH-AVAILABILITY AND DISASTER RECOVERY

• HA and/or DR are always required for HANA

• Define RTO and RPO for each HANA instance, for HA and DR separately

• What is the current H/A and DR strategy ?

• Techniques available: Host Auto-failover, System Replication, Storage Replication, VMWare H/A

• Re-use pre-production H/W for DR ? Easier with UCS Service Profile !

• Automatic H/A failover ?

• H/A and load balancing (VMWare)




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




HANA SERVER :CERTIFIED OR SUPPORTED ?

Cisco UCS Certified servers (Haswell E7)

Server CPU Memory

Storage SLES RHEL Virt.

Option Cert.

Status Deployment

Mode min BWoH SoH

B260 2 128 GB 768 GB 1.5 TB - ● ● ◐ (TDI) certified TDI only

B460 4 128 GB 2 TB 3 TB - ● ● ◐ (TDI) certified TDI only

C460 2 128 GB 768 GB 1.5 TB 12 x 1.2 TB RAID5

● ● ● certified Appliance

C460 4 128 GB 2 TB 3 TB 12 x 1.2 TB RAID5

● ● ● certified Appliance

C880 8 (4) 2 TB 4 TB 6 TB ● ● ○ certified Appliance

B260-M4 B460-M4 C460-M4 C880-M4


HANA SERVER :CERTIFIED OR SUPPORTED ?

• Cisco UCS Supported Servers (Haswell E5)

• Supported as per TDI rules

• Best economical choice for HANA non-prod instances up to 768 GB RAM

B200-M4 C220-M4 C240-M4




(BW or SoH)



Appliance or TDI ?

Data Tiering ?


Backup

Strategy ?

High Availability

and Disaster

Recovery ?




CUSTOMER EXAMPLE SITE 1 SITE 2

1x HANA 2x vHANA

ERP BW

Solman

Non-SAP

1x HANA 2x vHANA

ERP BW

Solman

Non-SAP

HANA pool

vHANA pool

VNX 5400

Virtual volumes

VNX 5400

HANA pool

vHANA pool

UCS UCS

Data Domain Data Domain

VPLEX VPLEX

NEXUS 5548 NEXUS 5548

27 © Copyright 2015 EMC Corporation. All rights reserved.

Documents

#SAPWEEK - Stockage de données, infrastructures ... · EMC CONFIDENTIAL—INTERNAL USE ONLY 3 HANA INFRASTRUCTURE : THE KEY DESIGN TOPICS HANA instances size and usage Disaster (BW