sap hana in data centers

2014 SAP SE. All rights reserved. 1

SAP HANA in Data Centers Dr. Ralf Czekalla

Product & Management Strategy (SAP HANA)

http://www.saphana.com/docs/DOC-2010


Disclaimer

This presentation outlines our general product direction and should not be relied on

in making a purchase decision. This presentation is not subject to your license

agreement or any other agreement with SAP.

SAP has no obligation to pursue any course of business outlined in this

presentation or to develop or release any functionality mentioned in this

presentation. This presentation and SAP's strategy and possible future

developments are subject to change and may be changed by SAP at any time for

any reason without notice.

This document is provided without a warranty of any kind, either express or implied,

including but not limited to, the implied warranties of merchantability, fitness for a

particular purpose, or non-infringement. SAP assumes no responsibility for errors or

omissions in this document, except if such damages were caused by SAP

intentionally or grossly negligent.


SAP HANA in Data Centers: Agenda

Introduction & Overview

Platform & Appliance methodology (Installation & Update)

Persistence

Backup & Recovery (System Copy)

High Availability

Disaster Recovery

Monitoring & Administration

Security & Auditing





Persistence


High Availability

Disaster Recovery


Security & Auditing


Continuous

availability

SAP HANA Continuous Availability Customer Expectation: Planned & Unplanned

Planned downtime

Unp

lan

ne

d d

ow

ntim

e

HANA consumption

Extended SAP backend deployments

Hardware failure / Malfunction

including Networks

Software Malfunction / security

threat / update

Natural / Man-made disasters

Failure of compliance &

operation

Unplanned outages

SAP HANA Revisions & SPSs

Patches for Data Services and SLT

Maintenance Events for OS & Hardware

Custom development & enhancements

Planned outages

.

Data Center

Readiness


SAP HANA Data Center Readiness Quick Overview

Security

Comprehensive

security framework

Fine-granular

authorizations

Encryption

Compliance (SoD,

audit logging, ...)

Secure hardware /

software setup

IDM and GRC

integration

3rd party via

standard /

documented

interfaces

High

Availability

In case of

hardware or

system failure

the standby

system takes

over in the

same data

center

Several options:

storage-based

shadow

databases

Simplification

Several

deployment

options

e.g. NetWeaver

Central

instance on

HANA server

Virtualization

for production

usage

Tailored Data

Center

Integration

Backup &

Recovery

Data & Log

Backup

Point-In-Time

Recovery

3rd-party

backup tool

support

Netbackup,

Tivoli, Simpana,

DataProtector,

Networker

Storage

Snapshots

Point-In-Time

Recovery

Data Center Readiness

SAP HANA

Available today Available today Available today Available today Available today

Disaster

Recovery

Failover to a

different HANA

instance in

another, even

far distant data

center

Automatic and

manual

procedures

possible

Several options:

storage-based

shadow

databases





Persistence


High Availability

Disaster Recovery


Security & Auditing


SAP HANA - Implications of being an Appliance

Classic software delivery

on-premise solutions

SAP ships only the software

Customer is responsible for entire product lifecycle

Appliance delivery

kind of SaaS on-site customer

SAP defines the solution together with its partners

SAP & partners control product lifecycle A

pplia

nce O

pera

tion C

oncepts

Infrastructure *

Operation *

Setup / Consulting

Support (Software, Maintenance and

Infrastructure)

SAP Development Software and Licenses

HW- and Technology

Partners Infrastructure

Operation

Setup/ Consulting

Support (Software, Maintenance and

Infrastructure)

SAP Development Software and Licenses

* Might be outsourced or owned by customer SAP responsibility Customers

responsibility

Partners'

responsibility


SAP HANA Platform

SAP HANA Technology Partners SAP HANA Hardware Partners

Starting with

HANA SPS08:

Linux on IBM Power CPUs possible start of pilot phase after SPS09


SAP HANA scalability Scales from very small servers to very large clusters

Single Server

2 CPU 128GB to 8 CPU 2TB

(Special layout for Suite on HANA

for up to 12TB per host)

Single SAP HANA deployments for

data marts or accelerators

Support for high availability

and disaster recovery

Scale Out Cluster

2 to n servers per cluster

Each server is either 4 CPU/1TB or 8

CPU/2TB

Largest certified configuration: 112 servers

Largest tested configuration: 250+ servers

Support for high availability

and disaster recovery

Cloud Deployment

SAP HANA instances can be

deployed to AWS

Limited to developer license

SAP HANA Enterprise Cloud

12 PetaByte HANA with BW Guinness world record

http://www.news-sap.com/sap-and-partners-set-new-record-for-worlds-largest-data-warehouse


In transition

TB 2 2-4 X X X X X X X X

TB 2 2-4 X X X X planned X X X X X X

TB 2 2-4 X X X X X X X X X X X

>TB 2 2-4 X X X X X


In transition

Scale-Out

512GB 2 2-4 X Existing HW

Extension

512GB 4 4-8 X X planned X

1TB 4 4-8 X X X X X X planned X

2TB 8 8 X X planned planned planned planned

4TB 8 8 R

6TB 8 8 R planned

12TB 16 16 R planned

HA Host Auto-Failover X X X X X X X X X

DR Storage Repl.: Sync X X X X X X X

DR Storage Repl.: Async X X X planned

Certified Intel IvyBridge-EX HANA Hardware October 2014* (available now)

* For most up to date list please go to the Certified SAP HANA Hardware or http://scn.sap.com/docs/DOC-52522

CP

Us

Sockets

Mem

ory

S

izes

BW

or

Da

tam

art

Su

ite

R: restricted availability (Pilot program)

https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396https://service.sap.com/sap/support/notes/1755396http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.htmlhttp://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522


Relaxed HW Specifications for Non-Production

Notes:

Hardware still from PAM or ICC

o SAP Product Availability Matrix or

http://scn.sap.com/docs/DOC-52522

Non-prod: Sizing flexible

o Instances can be combined

o SoH layouts can be used for BW

Intel E7 Processor Family

Westmere Ex or IvyBridge EX

(E7-x8xx, E7-x8xx V2)

128 GB of RAM to

Maximum memory supported on the box

Size: 2x Memory - Any local storage or shared

storage w/ standard disk on proven file systems

GPFS (IBM only),

NFS or XFS w/ Raid 0 and above

Standard networking components

SUSE Linux 11.x or Red Hat 6.5

Virtualized or Bare Metal

Processor

Memory

Storage

Network

Operating

System

Performance related support will only be provided on Production grade

hardware (Certified hardware)

http://service.sap.com/pamhttp://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522http://scn.sap.com/docs/DOC-52522


SAP HANA Tailored Data Center Integration Customer Feedback & Challenges and alternative Concept

SAP HANA tailored data center integration is an additional option to the

existing appliance model

HANA Server

HANA Server

Storage

HANA Server

HANA Server

HANA Server

(Corp.)

Storage

HANA Server

Reduce hardware and operation

cost at installed based customers

Mitigate risk and optimize time to

value by taking more responsibility

Gain additional flexibility in

hardware vendor selection *

Limited flexibility in server/ storage

combinations (well defined packages)

Established IT operation processes

have to be adapted slightly

Well defined HW and performance

KPIs

* Please contact for joining pilot phase: [email protected]

mailto:[email protected]


defined

certified

defined

certified

SAP HANA tailored data center integration The concept

SAP HANA tailored data center integration is an additional option to

the existing appliance delivery model

SAP HANA appliance delivery SAP HANA tailored

data center integration

HANA Server

HANA Server

Storage

HANA Server

Application

Database

Operating

System

Virtualization

Server

Network

Storage Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Virtualization

Server

Network

Storage


SAP HANA tailored data center integration Whats in it for you?

Mitigate risk and optimize time to value by

enabling existing IT Management processes for

SAP HANA implementation

Reduce hardware and operation cost by

reusing existing hardware components and

operation processes

Gain additional flexibility in hardware vendor

selection by

Leveraging the existing ecosystem


SAP HANA tailored data center integration Differentiating Capabilities

Fast Implementation

Support fully provided by SAP

Solution

validation done

by SAP and

partner

Preconfigured

hardware set-up

Preinstalled

software

Installation and

validation needs to be

done by customer

Customer aligns with

the hardware partner

on individual support

model

More Flexibility and Responsibility

Save IT budget and existing investment

SAP HANA appliance delivery SAP HANA tailored

data center integration

HANA Server

HANA Server

Storage

HANA Server

Application

Database

Operating System

Virtualization

Server

Network

Storage Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Virtualization

Server

Network

Storage


SAP HANA tailored data center integration Prerequisites for Enterprise Storage

Server - Only servers listed in the SAP HANA Product Availability Matrix are supported.

Configuration adjustments like:

No local disks, no flash cards required

Additional FibreChannel adapters for SAN boot are

allowed

Storage All storages successfully passed the SAP HANA Hardware Certification.

For more information, see Partner Information Center or contact [email protected]

SAP HANA Installation Needs a certified expert (internal or external) to be executed

The exam SAP Certified Technology Specialist (Edition 2013) SAP HANA Installation

(E_HANAINS131) needs to be passed successfully to perform SAP HANA installations at

customer side.

For more information, see SAP Training and Certification Shop

Requirements:

Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Storage

https://websmp210.sap-ag.de/~sapidb/011000358700000701932011Ehttps://websmp210.sap-ag.de/~sapidb/011000358700000701932011Ehttps://websmp210.sap-ag.de/~sapidb/011000358700000701932011Ehttps://websmp210.sap-ag.de/~sapidb/011000358700000701932011Ehttps://websmp210.sap-ag.de/~sapidb/011000358700000701932011Ehttp://www.sap.com/partners/directories/SearchSolution.epxmailto:[email protected]://training.sap.com/v2/certification/e_hanains131-sap-certified-technology-specialist-edition-2013---sap-hana-installation-g/


SAP HANA tailored data center integration Certified Partner Enterprise Storage Solutions (Oct. 2014)

Storage Partners & certified storage solutions*:

Certified Enterprise Storage for SAP HANA or http://scn.sap.com/docs/DOC-48516

Dell EMC Fujitsu Fusion-IO Hitachi HP Huawei IBM NetApp Violin

Compellent

SC8000

Symmetrix

VMAX

VMAX

10K

ETERNUS

DX

DX200 S3

ION-

Accelerator

R720

Enterprise

Storage

VSP

(2010)

3PAR

StoreServ

7400

OceanStor

Storage

S5500T

Flash-

system

820

E-Series

E-5500

6200

Series

Flash

6264

VNX

Unified

Storage

Systems

VNX 5400

XP

Storage

XP7

Storwize

V7000

(SVC)

FAS Series

FAS 8060

Family

XIV

Storage

2810

DS8070,

DS8000

Family

* For most up to date list please go to Certified Enterprise Storage for SAP HANA or http://scn.sap.com/docs/DOC-48516

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.htmlhttp://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.htmlhttp://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516http://scn.sap.com/docs/DOC-48516


SAP HANA tailored data center integration Data Throughput and Latency KPIs for Production SAP HANA Systems

Source: SAP HANA Administration Guide section 2.7: Hardware Checks for Tailored Data Center Integration

or SAP Note 1652078 SAP HANA database: Hardware check

MB/s == MByte/s

Volume Block Sizes Test File Size KPIs

Initial Write

(MB/s)

Overwrite

(MB/s)

Read

(MB/s)

Latency

(s)

Log 4K 5G n.a. 30 n.a. 1000

16K 16G n.a. 120 n.a. 1000

1M 16G n.a. 250 500 n.a.

Data 4K 5G n.a. n.a. n.a. n.a.

16K 16G 40 100 n.a. n.a.

64K 16G 100 150 250 n.a.

1M 16G 150 200 300 n.a.

16M 16G 200 250 400 n.a.

64M 16G 200 250 400 n.a.

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078http://service.sap.com/sap/support/notes/1652078


SAP HANA Persistence Disk sizing with class. HANA appliance vs. HANA TDI

Classical SAP HANA Appliance

0.5:3:1

Reason for comfortable sizing: Appliance can not always be changed on

short notice (add more disks) depending on the general design, etc. for the HW partner offering of choice.

Source: SAP HANA Administration Guide (to be updated to latest changes)

* Minimum value for every size above 512 GB - more might be necessary depending on very high workload situations (transactional load)

SAP HANA Tailored Datacenter Integration

0.5:1:1

Reason for reduced sizing: Customers can change disk layout (extensions

of disk areas) on short notice because they are responsible for the complete HANA Stack

Source: SAP HANA Storage Requirements Whitepaper (SAP note 1900823)

* Minimum value for every size above 512 GB - more might be necessary depending on very high workload situations (transactional load)

0.5 x RAM

512 GB*

Log 0.5 x RAM

512 GB*

(< 512 GB RAM)

( 512 GB RAM)

3 x RAM Data 1 x RAM

1 x RAM Shared/Trace 1 x RAM

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://service.sap.com/sap/support/notes/1900823


Outlook Next Steps Enterprise Network

Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Storage

Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Network

Next Step Pilot Customer Program Network:

We started a pilot customer program for

SAP HANA tailored data center integration Enterprise Network

for a limited number of customers in December 2013.

Further information will follow soon.

For further questions feel free to contact us:

[email protected].

General Availability Storage:

The storage layer is the first layer to be opened up.

SAP HANA tailored data center integration Enterprise Storage

has already served more than 50 customers during a pilot program

and is generally available since in Q4/2013.

mailto:[email protected]


SAP HANA Tailored Data Center Integration Enterprise Network

1 Application Server Network 2 Client Network 3 Data Source Network

4 Internode Network

6 7 Enterprise Storage Network

5

Backup Network

System Replication Network

Client zone:

Internal zone:

Storage zone:

More details available in

SAP HANA documentation:

SAP HANA Master Guide, chapter 2

"The SAP HANA Network

Data Center 1 Data Center 2

5

Backup

HANA Client (BI client, HANA

Studio, ...)

SAP HANA Server

Node 1

Enterprise Storage

2

6 7

Backup

HANA Client (BI client, HANA

Studio, ...)

Enterprise Storage

2

6 7

SAP HANA Server

Node 3

SAP HANA Server

Node 2

SAP HANA Server

Node 1

SAP HANA Server

Node 4

SAP HANA Server

Node 3

SAP HANA Server

Node 2 4 4

1

Application Server

(ABAP, XS)

3

Data Sources

3

Data Sources

1

Application Server

(ABAP, XS)

SAP HANA Server

Node 4

http://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdf


SAP HANA Tailored Data Center Integration Enterprise Network

Network Segmentation All networks need to be properly segmented and may be connected to the same core/ backbone switch.

Note: Network security and segmentation is a function of the network switch vendor and must be configured according to the specifications of the switch vendor.

For more details on network security see the SAP HANA Security Guide, chapter 4.

Recommendations: All recommendations mentioned refer to the usage in productive environments

Bandwidth 10 GbE for Internode and Backup Network

10 GbE (Ethernet) or 8 GbF (FibreChannel) for Enterprise Storage Network

Redundancy It depends on the customers high-availability requirements if and how to apply redundancy for the different SAP HANA network segments.

SAP strongly recommends to make the following networks redundant:

Internal zone (Internode and System Replication networks)

Storage zone (Enterprise Storage and Backup Storage networks)

Fully redundant switches and routers are recommended.

Enterprise

Storage

HANA Server

HANA Server

HANA Server

Shared Network

Network

http://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdf


SAP HANA Heterogeneous Landscapes

Planned with the following constraints:

Hardware from the same HW partner

Memory area the same on every host (e.g. all L size boxes)

Distributed tables: Slowest part of a cluster will define the overall

performance

Aim is to increase the size of the database, not primarily the performance

Could be a migration step or

path to a future CPU architecture

Mixture of Intel CPU architectures

(Intel Westmere EX or IvyBridge EX)

on different hosts are possible.

old

CP

Us

old

CP

Us

old

CP

Us

old

CP

Us

old

CP

Us

ne

w C

PU

s

ne

w C

PU

s

ne

w C

PU

s x TB

CPU power

Scale-Out cluster members


Fulfilling IT compliance (IT policies) for Data Centers

Data Center compliances usually define specific topics to

Managing, Monitoring and Backup & Restore tools

Central user management with IDM tools

Anti Virus software usage mandates

OS security patches, firewalls

Etc.

Additional 3rd party tools required to complete these

compliances are tolerated with following restrictions

Neither SAP nor hardware vendor offers support for tools which are

not official part of the SAP HANA BOM.

The hardware vendor is tolerating the installation and operation of

this compliance-related software.

Customers might be asked to stop these tools in case of a support

issue and to enable reproduction of the problem

No closed source driver are allowed with these compliance tools

without further support agreement of the vendor with SAP for these

HW Partner

Customer

Tool Vendor

SAP

HW Partner Tool set


Technical Operational Manual for SAP HANA

SAP offers a technical operational manual (TOM) with all kinds of topics about

operating SAP HANA as an appliance (http://help.sap.com/hana_platform).

This manual should be taken as input for further adaptations of the operation of

SAP HANA in customers Data Centers.

The needed regular duties around

the operation of SAP HANA can be

derived from this document.

Usually HANA needs lesser administration

than other databases, typical duties are:

Regular backups (Database, Bare-Metal

software and configuration backup)

Patches; usually on demand in case of

problems or known issues (DB, OS)

Monitoring (automated or manual)

Task Responsible

SAP HANA appliance installation Hardware Partner

Hardware Hardware Partner

OS installation Hardware Partner

OS updates Customer

SAP HANA updates Customer

Data source connectivity Customer

BI Client installation Customer

SAP HANA software support SAP

Table: Cited from SAP HANA TOM

http://help.sap.com/hana_platform


Project Cost Analysis (TCO) by Forrester Cost Savings Enabled By Transitioning to the SAP HANA platform

Further documentation available on:

www.sap.com/innovation-and-me

Unlock business value and deliver

breakthrough innovation while simplifying IT

Executive Summary

Full paper

(with free

registration)

http://www.sap.com/innovation-and-mehttp://www.sap.com/innovation-and-mehttp://www.sap.com/innovation-and-mehttp://www.sap.com/innovation-and-mehttp://www.sap.com/innovation-and-me


Multi-SID on one SAP HANA hardware

MCOS

Multiple Components on one

System, multi-SID

1 x Appliance

n x HANA DB

n x DB schema

n x Applications

E.g. DEV and QA system on

one hardware. See SAP

note 1681092.

Classical scenario

Appliance approach for

optimal performance

1 x Appliance

1 x HANA DB

1 x DB schema

1 x Application

(e.g. ERP, CRM or BW)

Bare-metal or virtualized

SAP HANA

AS ABAP

SID: ABC

Schema ABC

AS ABAP

SID: ABC

SAP HANA SAP HANA

Schema ABC

AS ABAP

SID: XYZ

Schema XYZ

Productive Systems Non-Productive Systems

Virtualization (on premise)

Virtualization technology

separates multiple OS images

each containing one HANA DB

n x Virtualized Appliances

n x HANA DB

n x DB schema

n x Applications

See SAP note 1788665

AS ABAP

SID: ABC

SAP HANA SAP HANA

Schema ABC

AS ABAP

SID: XYZ

Schema XYZ

MCOD

Multiple Components on one

Database

1 x Appliance

1 x HANA DB

n x DB schema

n x Applications

Prod. usage for white listed

scenarios allowed, e.g. SAP

ERP together with SAP Fraud

Management. See SAP notes

1661202 and 1826100.

AS ABAP SID: ABC

Application

SID: XYZ

SAP HANA

Schema ABC

Schema XYZ

White-Listed Scenarios

Virtu

aliz

atio

n

Virtu

aliz

atio

n

Ba

re M

eta

l

Ba

re M

eta

l

https://service.sap.com/sap/support/notes/1681092https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1661202https://service.sap.com/sap/support/notes/1826100


Multi-SID on one SAP HANA hardware

Multi SID for SAP HANA allowed for all non-productively used appliances

Installation process for these additional SIDs is available as Multi-SID Installer

(since SPS5)

For the current status, please check the following SAP notes

1661202 Support for multiple applications on SAP HANA,

1681092 BW on SAP HANA - landscape deployment planning,

1666670 Multiple SAP HANA DBs on one appliance

1826100 Multiple applications SAP Business Suite powered by SAP HANA

Whitepaper about Deployment options SAP HANA System Landscape Guide

Blog about current status of virtualization with HANA for production

https://service.sap.com/sap/support/notes/1661202https://service.sap.com/sap/support/notes/1681092https://service.sap.com/sap/support/notes/1666670https://service.sap.com/sap/support/notes/1826100http://www.saphana.com/docs/DOC-4385http://www.saphana.com/community/blogs/blog/2013/11/05/just-a-matter-of-time-sap-hana-virtualized-in-production


Joined SAP HANA and SAP NetWeaver ABAP Application Server and HANA Database on one hardware

SAP HANA and SAP NetWeaver AS ABAP deployed on one server is a multi-

component, resource and cost optimized deployment approach

SAP HANA

Server

SAP HANA

System

SAP NW AS

ABAP System

SAP HANA and SAP NetWeaver AS

deployed on one server

Hardware resources isolated

Separate hardware

Cost optimized approach

Shared Memory and CPU resources

SAP HANA

Server

SAP HANA

System

SAP NW AS

ABAP Server

SAP NW AS

ABAP System

Separated

deployment approach


Joined SAP HANA and SAP NetWeaver ABAP Application Server and HANA Database on one hardware

SAP HANA and SAP NetWeaver AS ABAP deployed on one system is

available since December 16, 2013.

SAP HANA

Server

SAP HANA

System

SAP NW AS

ABAP System

Availability

For all productive and non-productive SAP HANA SPS7 single node installations. All products based on SAP NetWeaver AS ABAP 7.4 are supported.

Requirements Additive sizing: Additional memory resources for the SAP

NetWeaver AS ABAP system needs to be available on the SAP HANA server. For more information, see memory sizing based on SAP Release Note - 1953429

Separate SIDs for both systems required

SAP HANA software installation

The exam SAP Certified Technology Specialist (Edition 2013) SAP HANA Installation (E_HANAINS131) needs to be successfully passed for a person to perform SAP HANA software installations. For more information, see SAP Training and Certification Shop

https://service.sap.com/sap/support/notes/1953429https://service.sap.com/sap/support/notes/1953429https://service.sap.com/sap/support/notes/1953429https://service.sap.com/sap/support/notes/1953429https://service.sap.com/sap/support/notes/1953429https://service.sap.com/sap/support/notes/1953429https://training.sap.com/v2/certification/e_hanains131-sap-certified-technology-specialist-edition-2013---sap-hana-installation-g/https://training.sap.com/v2/certification/e_hanains131-sap-certified-technology-specialist-edition-2013---sap-hana-installation-g/


Sizing with SAP HANA installations

Sizing notes with attached scripts which measure the source system and

calculates HANA target size even with compressed source databases

Related to used Szenario:

Datamart SAP note: Note 1514966 - Sizing SAP In-Memory Database (Data Mart)

BW SAP note: Note 1637145 - Sizing for BW on HANA

ERP/Suite SAP note: Note 1793345 - Sizing for Suite on HANA

SAP AGS sizing paper for SAP HANA:

https://service.sap.com/~sapidb/011000358700000050632013E

General statement:

Prefer a scale-up before starting to scale-out to multiple boxes

(SAP HANA Scalability document Chapter 4.5)

http://service.sap.com/sap/support/notes/1514966http://service.sap.com/sap/support/notes/1514966http://service.sap.com/sap/support/notes/1514966http://service.sap.com/sap/support/notes/1514966http://service.sap.com/sap/support/notes/1514966http://service.sap.com/sap/support/notes/1514966https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1637145https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/sap/support/notes/1793345https://service.sap.com/~sapidb/011000358700000050632013Ehttp://www.saphana.com/docs/DOC-2022


SAP HANA Variety of deployment options

In the Cloud

HANA developer edition free of charge

SAP HANA One / HANA one premium pay per use

SAP HANA Enterprise Cloud 24/7 mission critical / Enterprise Support

In the Data Center

Bare metal single Server pre-configured & validated stack

Scale-Out / HA & DR cluster scalable from single node to Geo cluster

Virtualized with VMware VMware vSphere 5.1 or newer


http://www.saphana.com/docs/DOC-4184http://www.saphana.com/docs/DOC-4184http://www.saphana.com/docs/DOC-4184


Cloud & Virtualization

SAP HANA in the Cloud SAP HANA Developer Edition

o For product evaluations, trials, students, data exploration projects, etc.

o Software is free, developers pay cloud provider for server usage.

o Community supported through http://saphana.com/cloud

o Available of choice on 4 public cloud providers

SAP HANA One

o Non-productive and productive usage

o Option 1 - with community support according SAP Note 1798212

o Option 2 - with full SAP support through OSS as part of SAP HANA One premium license

o Available of choice on 4 public cloud providers

SAP HANA Virtualization On Premise Productive usage allowed for SingleVMs per hardware

Restrictions

o Vendors (Note 1788665 - SAP HANA running on VMware vSphere VMs)

o Maximum HANA performance is only reached on bare metal (non-virtualized)

o VMware Vmotion (hot move) or VMware-HA are supported

http://saphana.com/cloudhttps://service.sap.com/sap/support/notes/1798212https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665https://service.sap.com/sap/support/notes/1788665



Enterprise-class cloud offering for

mission critical

global 24 x 7 operation

cloud elasticity

o Global Availability (4 data centers in US

and Europe, 2 more planned in APJ)

o Custom data center arrangements for

compliance

o Advanced business continuity and support

o Standards based cloud operation

o Monthly External Penetration Tests

Open for any data footprint

Any valid SAP HANA T-shirt size

Full SAP support through OSS


SAP Business Warehouse BW | BPC

SAP Business Suite ERP | CRM |

Custom Apps Big Data | Consumer

SAP HANA Cloud Platform

Services

Assessment

Onboarding &

Migration

Cloud Hosting &

Managed Services

Custom Services

In-memory Infrastructure


SAP HANA virtualized Current Supported Hypervisors

Currently, the only SAP supported virtualization solutions for running SAP HANA virtualized are

VMware vSphere 5.1 and SAP HANA SPS 05 (or later releases) for non-production use cases.

VMware vSphere 5.5 and SAP HANA SPS 07 (or later releases) for production and non-production use cases.

The following general conditions & constraints do apply while running SAP HANA virtualized:

Limited to single-VM (scale-out / multi-node database installations not supported)

Multi-VMs on one HANA certified host are in controlled availability (SAP note 2024433 )

CPU & memory overprovisioning must not be used

Each SAP HANA instance / virtual machine is sized according to the existing SAP HANA sizing guidelines and VMware recommendations.

SAP HANA system has been either delivered pre-configured on certified SAP HANA appliances with VMware vSphere hypervisor installed by SAP HANA hardware partner, or the SAP HANA installation was done by an SAP HANA certified engineer on SAP HANA certified hardware and successfully verified with the SAP HANA hardware configuration check tool.

See SAP Note 1788665 - SAP HANA Support for VMware vSphere Environments

http://service.sap.com/sap/support/notes/1788665

https://service.sap.com/sap/support/notes/2024433http://service.sap.com/sap/support/notes/1788665


SAP HANA virtualized Controlled Availability of SAP HANA on VMware vSphere in production

SAP has released SAP HANA SPS 07 on VMware vSphere 5.5 for general availability, allowing

to go live with SAP HANA on VMware vSphere 5.5, provided the following conditions have

been met:

Single SAP HANA virtual machine on a dedicated 2 or 4-socket SAP HANA certified server

Multiple SAP HANA virtual machines on a single physical server are in controlled

availability (SAP note 2024433 )

o No SAP HANA multi-node / scale-out deployment configurations

o No 8-socket hardware configurations

Both, SAP HANA appliance and SAP HANA Tailored Datacenter Integration (TDI) delivery

methods are supported for SAP HANA on VMware vSphere.

o The maximum size of a virtual SAP HANA instance is limited by the maximum size of a virtual

machine on VMware vSphere 5.5 release, which is 64 vCPUs and 1 TB of memory (limited by

VMware, not SAP HANA).

o No CPU and/or Memory overcommitting

See SAP HANA Guideline for Being Virtualized with VMware vSphere


https://service.sap.com/sap/support/notes/2024433http://www.saphana.com/docs/DOC-4192http://www.saphana.com/docs/DOC-4192http://www.saphana.com/docs/DOC-4192


SAP HANA virtualized Technology Roadmap (from today to 2015+)

Blog: At the seaside with SAP HANA and Vmware

Single VM production

support

Complement deployment

options

Multi VM support*

HANA scale out

On single host

On vSphere cluster

Extend platform support

8 socket hardware

Future vSphere optimization /

releases

Add variety Support of additional

hypervisors

H1/2014 H2/2014 2015+

This is the current state of planning and may be changed by SAP at any time.

*Controlled availability:

SAP note 2024433

http://www.saphana.com/community/blogs/blog/2014/05/06/at-the-seasside-with-sap-hana-on-vmwarehttp://www.saphana.com/community/blogs/blog/2014/05/06/at-the-seasside-with-sap-hana-on-vmwarehttp://www.saphana.com/community/blogs/blog/2014/05/06/at-the-seasside-with-sap-hana-on-vmwarehttps://service.sap.com/sap/support/notes/2024433


Service Offerings for SAP HANA Customers Help with individualized Services

Partners

HW Partner Service Offerings

3rd Party Service Partner Offerings

SAP

IT Application Operations

AMS Application Management Services

RAO Remote Application Operation

IT Technology Operations

RDO Remote Service for Database Operation

(link)

Business Process

& Strategy

Application

Infrastructure

Business Strategy

Business Process

Application Management

Application Operation

Application Infrastructure

Infrastructure Operation

Base Infrastructure

http://www.sap.com/services-support/svc/data-technology/consulting/info.html


Service Offerings for SAP HANA Customers SAP AMS for HANA

Language

Our network of SAP support especialists spans around the globe.

Therefore, we can support you in multiple languages.

Volume

AMS is typically delivered from our Remote Delivery Centers which gives you a cost-benefit compared to

onsite delivery.

Depending on your needs, we can also design a model with onsite resources (combined with remote).

Even in a remote model, our consultants can come to your locations for special activities. Location

Our SAP AMS service is delivered by shared pool resources,

which means you only pay what you use and not for idle time.

Nevertheless, we ensure named resources that know your

system and landscape by heart.

Components

SAP runs SAP best we can provide you expert SAP support services.

Depending on your requirements, we can support you in all SAP HANA components that you use or only in

selected ones.

I can sleep peacefully at

night knowing that the SAP

Application Management

service is behind us

Wong Voon Pui, Head of IT and Card

Services, Boustead Petroleum

Marketing Sdn. Bhd.


Remote Service for Database Operations (RDO)

RDO provides clients the option to hand over

day to day operational support for their SAP

database environment to SAP

RDO Service includes the following Components

Monitoring and Alerting

Problem Resolution

Proactive Performance Management

Software Infrastructure Maintenance

Services are provided remotely, but can include an onsite presence if customer prefers

RDO is available for

SAP HANA

SAP Sybase ASE

SAP Sybase IQ

SAP Sybase Replication Server

SAP mobile database solutions


Remote Service for Database Operations (RDO)

For further information about this SAP RDO service offering, please visit

http://www.sap.com/services-support/svc/data-technology/consulting/info.html

Customer Pain Points

Lack of staff with skillsets needed

Staff training and retention issues

Operational support needs not being met

Customer Goals/Needs

Provide predictable cost for operational

support needs

Utilize internal staff for strategic work

Ensure 24x7 operational coverage

Improve or maintain quality of service

http://www.sap.com/services-support/svc/data-technology/consulting/info.htmlhttp://www.sap.com/services-support/svc/data-technology/consulting/info.htmlhttp://www.sap.com/services-support/svc/data-technology/consulting/info.htmlhttp://www.sap.com/services-support/svc/data-technology/consulting/info.htmlhttp://www.sap.com/services-support/svc/data-technology/consulting/info.htmlhttp://www.sap.com/services-support/svc/data-technology/consulting/info.html


The Path to BW powered by HANA

1 4

Start:

BW with

any DB

Preparation:

Fulfill HANA-DB

Prerequisites

Target:

BW powered

by HANA

2

HANA any DB

SAP BW

3.x/7.x

SAP BW

7.40 SP6

SAP BW Release

Upgrade: min. Release

BW 7.30 SP5

Release Upgrade for

additional components

(e.g. SEM-BCS)?

Single Stack Separation:

Separate ABAP and

JAVA

Check Modifications

Convert Unicode

JAVA Upgrade

Migrate Authorizations to

7.x-Concept

Link BW-Cookbook

3

Proposed:

Consider Additional

Aspects

a) Sizing of required HANA DB incl. HW/

SW investment

b) Definition of future System Landscape

(incl. DR/ HA Single Node/ Scale Out)

c) Housekeeping: Reduction of to be

migrated data volume

d) Data Aging Concept

NLS/ Archiving + Temperature-Concept

Assess new Release Features

e) Optimize Data Models & Check Native

HANA Data Models

f) Check New Frontends (incl. UI5, Fiori,

Design Studio, Analysis Office,

Mobility)

g) Complete HANA Strategy (BW = EDW,

Operational Reporting, Suite on HANA,

HANA Live, Fiori, UI5, )

5

Future:

Potentials from BW p.b.

HANA using

BWA

https://cookbook.experiencesaphana.com/bw/deploying-bw-on-hana/preparation/ready-system-landscape/https://cookbook.experiencesaphana.com/bw/deploying-bw-on-hana/preparation/ready-system-landscape/https://cookbook.experiencesaphana.com/bw/deploying-bw-on-hana/preparation/ready-system-landscape/


The Path to ERP powered by HANA

1 4

Start:

ERP with

any DB

Preparation:

Fulfill HANA-DB

Prerequisites

Target:

ERP powered

by HANA

2

HANA any DB

SAP

ERP 6.x

SAP

ERP 6.7

Sizing (SAP Note 1872170)

Data Center: Architecture

Archiving: Evaluate potential

of data archiving

Stack Separation: Separate

ABAP and JAVA Stack

Unicode: Unicode Conversion

required

Add-Ons: Verify add-on

compatibility (SAP Notes

1760306, 1855666)

Released Scenarios: Verify

released scenarios (SAP Note

1768031)

Functional Correctness

(SAP Note 1935918)

3

Proposed:

Consider Additional

Aspects

5

Future:

Potentials from ERP p.b.

HANA using

Improved Business Processes:

Evaluate usage of improved standard

transaction (SAP Note 1761546) as well

as Industry specific improvements

Operational Reporting: Leverage SAP

HANA Live Content as the basis for real-

time operational reporting

Custom Code Optimization: Monitor

your system using SQLM / User

Procedure Logging or Individual Traces

Fiori: Improve End-User Experience by

implementing SAP Fiori

Simplify: Reduce complexity & interfaces

by eliminating existing apps and dbs by

moving them to SAP HANA

Search: Evaluate usage of Google-Like

Search Capabilities

Business Re-Engineering:

Redefine existing business

processes

New Business Models:

Establish new business

models using ERP on HANA

https://service.sap.com/sap/support/notes/1872170https://service.sap.com/sap/support/notes/1760306https://service.sap.com/sap/support/notes/1855666https://service.sap.com/sap/support/notes/1768031https://service.sap.com/sap/support/notes/1935918https://service.sap.com/sap/support/notes/1761546https://www.youtube.com/watch?v=HPS2WGFug-g


SAP HANA Release Strategy Retrieve incremental, but non-disruptive SAP HANA innovation

Updates shipped for SAP HANA are strictly downward compatible.

Incompatible changes may be considered due to legal or security reasons, but

follow a strict exception approval process (Time-less Software).

These Updates are shipped with SAP HANA Support Package Stacks (SPS),

delivered from within one delivery stream and without additional ramp-up. SPS are

planned to be released twice per year.

The SAP HANA product stays in mainstream maintenance as long as application

releases that are built on top SAP HANA are in mainstream maintenance, extended

maintenance, or priority-one support (e.g. Release note 69.xx 1935871).

. 68 69 70 71 72 80 81 82

Revisions are cumulative

and strictly downward compatible

http://scn.sap.com/people/vishal.sikka/blog/2008/11/02/timeless-software-part-1http://scn.sap.com/people/vishal.sikka/blog/2008/11/02/timeless-software-part-1http://scn.sap.com/people/vishal.sikka/blog/2008/11/02/timeless-software-part-1http://scn.sap.com/people/vishal.sikka/blog/2008/11/02/timeless-software-part-1http://scn.sap.com/people/vishal.sikka/blog/2008/11/02/timeless-software-part-1http://service.sap.com/sap/support/notes/1935871


SAP HANA Release Strategy Understand the Differences in SAP HANA Revisions

SAP HANA Support Package (SP) Revisions Represents the individual software corrections and updates available for SAP HANA. Revisions are cumulative and strictly downward compatible.

SAP HANA Maintenance Revisions Contain only major bug fixes found in key SAP HANA scenarios. The provisioning of new maintenance revisions ends with availability of SAP HANA production system verified revision, approx. 3 months after release of a successor SPS. From this date, customers must adopt the regular SP revisions to receive further fixes.

SAP HANA Datacenter Service Point Outlines certain revisions which have been running in production enterprise applications at SAP before they are released to customers.

Those revisions are planned approx. 3 months after release of the latest SPS and are intended to allow better planning of maintenance windows for production environments running on SAP HANA.

Datacenter Service Point

Maintenance revisions SP revisions

70 71 73 74

80

76.01 76.xx


SAP HANA Release Strategy Adapt new SAP HANA releases at your own speed

Customers may choose to maintain their SAP HANA system either with the latest SAP HANA SP revision or to stay temporarily on the SAP HANA Maintenance revisions stream:

Running SAP Business Suite, SAP Net Weaver BW or Accelerators, powered by SAP HANA in production customers may choose to stay approx. 3 months longer on an certain SAP HANA SPS by implementing the SAP HANA Maintenance Revisions, while fixing merely major bugs (see SAP Note 1948334).

For all other customers, early birds and pilots who do not run SAP HANA in productive usage, SAP propose an immediate switch to a new SPS by implementing the regular SAP HANA SP Revisions as soon as they are released. This will allow to benefit from incremental, but non-disruptive innovation, provided by the latest SAP HANA features and fixes.

. 68 69

70 71 73 74

80 81

69.xx Recommended revision update / patching path

for key SAP HANA scenarios in production

82

76.xx

http://service.sap.com/sap/support/notes/1948334


SAP HANA Release Strategy Expect stability and predictability for your SAP HANA maintenance

The newly introduced SAP HANA Datacenter Service Point (DC service point) provides SAP HANA customers with more guidance when and based on which SAP HANA Revision to plan their SAP HANA maintenance stack on.

As most customers have to plan their maintenance window between their quarterly end closings, the DC service point had been defined to be between the SAP HANA SPS, at the end of March and at the end of September.

As prove of SAPs commitment in its own software quality, the Revisions referenced by such DC service point will also be running in production enterprise applications at SAP for at least one week before they are finally released, assuring customers even more stability and predictability.

. 68 69

70 71 73 74

80 81

69.xx

Recommended SAP HANA Datacenter

Service Points for planned maintenance

of SAP HANA

82

Recommended revision update / patching path

for key SAP HANA scenarios in production


SAP HANA Platform News with SAP HANA SPS08 and Beyond

Tailored Data Center Integration

For Enterprise Networks

A lot more hardware solutions certified

New operation system platforms

RedHat Linux support for SAP HANA: New release RHEL for SAP applications introduced

HW partner starting to support RHEL for SAP HANA

HANA Studio: Mac OS X Support

Virtualization

Production support for VMware with single VMs per hardware

MultiVMs for production is in controlled availabilty

Planned beyond

Tailored Data Center Integration

o Next level:

Support for IBM Power CPUs with Linux on Power

Topology changes

o removing surplus services (deleting surplus hosts already implemented)

o UI support in SAP HANA Studio for removing services

SAP LVM deeper integration

o Cloning, Renewing, Copying

Data temperature

o Dynamic tiering

SAP HANA Multitenant Database Containers

o formerly known as Multiple Databases



SAP HANA Platform SAP LVM Roadmap for SAP HANA integration

Release 2.1(planned)

SAP Landscape Virtualization Management

Outlook (planned beyond)

Provisioning SAP

Systems*

Support standalone SAP HANA systems:

single host

multiple hosts

SAP application** and SAP HANA system on same host

SAP application** and SAP HANA system on different hosts

Landscape

Management

Basic Management: start/stop/monitor of SAP application and SAP HANA system (multiple host)

Relocate: Multiple hosts SAP

HANA system

Secondary SAP HANA system (HANA system replication)

Take-over procedure for SAP HANA system replication

PLANNED INNOVATIONS FUTURE DIRECTION


* System Provisioning scenarios includes: clone, copy, rename, refresh ** SAP applications: based on SAP NetWeaver Application Server ABAP

Provisioning* based on secondary SAP

HANA system (SAP

HANA system

replication)

Provisioning SAP

Systems*

Enablement of further SAP HANA high availability procedures

Basic Management: start/stop/monitor for Sybase IQ as NLS for SAP application** based on SAP HANA system

Relocate operation for Sybase IQ as NLS for SAP applications** based on SAP HANA system

Landscape

Management


SAP HANA Platform Introducing SAP HANA Dynamic Tiering

Performance

and Price Priority and

Data Volume

In DB

In memory

No restrictions, all features available

External to DB

Near-line Storage

Read access, no updates

In DB

On disk

No restrictions, all features available

Non-Active Data Concept /

Disk store of dynamic tiering

Near-line Storage

HANA column store

External to DB

Archive storage No read access or updates

Traditional Archive

hot

warm

Cold

(NLS)

Archive

HANA

Archive






Persistence


High Availability

Disaster Recovery


Security & Auditing


HANA

SAP HANA Persistence: In-Memory Data Is Regularly Saved to Disk

Data:

SQL data and undo log information

Additional HANA information,

such as modeling data

Kept in-memory to ensure maximum

performance

Write process is asynchronously

Log:

Information about data changes (redo log)

Directly saved to persistent storage when

transaction is committed (synchronous)

Cyclical overwrite (only after backup)

Savepoint:

Changed data and undo log is written from

memory to persistent storage

Automatic

At least every 5 minutes (customizable)

Memory

Data

Persistent Storage

Regular automatic

savepoints

Information about

data changes

Log

Volume Data

Volumes


In-Memory

SAP HANA Database Landscape

Persistence Layer

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

Distributed HANA

database even on a

single host with shared

nothing concept


In-memory computing is secure

The SAP in-memory database holds the bulk of its data in memory for maximum performance, but still uses persistent storage to provide a fallback in case of failure. The log is capturing all changes by database transactions (redo logs)

Data and undo log information (part of data) are automatically saved to disk at regular savepoints

The log is also saved to disk continuously and synchronously after each COMMIT of a database transaction (waiting for end of disk write operation)

After a power failure, the database can be restarted like a disk-based database:

System is normally restarted (lazy reloading of tables to keep the restart time short)

System returns to its last consistent state (by replaying the redo log since the last savepoint)

SAP HANA Persistence Regular Saving of In-Memory Data to Disk, Restart

Savepoint:

Data & undo log is written

to disk (data area)

1 Continously and after each COMMIT,

redo log is written to disk (log area)

2 Power failure

3

Time


SAP HANA Smart Data Access Data virtualization for on-premise and hybrid cloud environments

Benefits

Remote real-time query processing

Smart continuously self-tuning system

Secure access to heterogeneous data

sources

Heterogeneous data sources

SAP HANA to Hadoop (Hive)

Teradata

SAP Sybase ASE

SAP Sybase IQ

Oracle 12c

MS SQL-Server

Transactions + Analytics

Teradata

Hadoop

SAP HANA

ASE

IQ

SAP HANA

Oracle MS SQL


SAP HANA Smart data access Differentiation

The intelligence of knowing when to

delegate query processing or pull the

data into SAP HANA for query

processing, based on the performance

windows

Dynamic query recommendation

To return query results extremely fast.

Capabilities supporting fast processing

leveraging in-memory acceleration

Cost-based query optimization

Data pre-caching

In-flight transformation

Converged data processing

Data

Federation

Data

Virtualization

Smart

Data Access


SAP HANA Smart Data Access Data modeling in SAP HANA studio

Transactions + Analytics Applications

Enables users to develop applications

on SAP HANA,

Allows remote data to be accessed

seamlessly

Heterogeneous data sources

accessed in SQL statements through

a virtual table

Data Sources

SAP HANA

SAP HANA Tables Virtual Tables

Adapter

Framework Built-In

Adapters

Third Party

Adapters

SAP HANA

Studio


SAP HANA Persistence News with SAP HANA SPS08 and Beyond

Persistence development

Deeply involved in several projects, like

new technology integration into SAP

HANA

Smart Data Access

More classical databases are supported:

IBM DB2 and Netezza

SAP HANA SPS09 (current planning)

Smart Data access for SAP MaxDB

Planned beyond

More flexible Data Volume management

with possibility for multiple smaller data

volume files






Persistence


High Availability

Disaster Recovery


Security & Auditing


SAP HANA database Data backups

Contain the current payload of the data

volumes

Any pages that are changed during the data

backup written to different locations in the

data volumes (shadow page concept)

Manual (SAP HANA studio, SQL

commands), or scheduled (DBA Cockpit)

Log backups

Contain the content of closed log segments

Automatic (asynchronous) whenever a log

segment is full or the timeout for log backup

has elapsed

Log Area

(disk)

Data Area

(disk)

Memory

Savepoint COMMIT

Data Backups Log Backups

SAP HANA Backup and Recovery Memory Disk Backup


SAP HANA Backup and Recovery Terminology

Log Area

Data Area

Data

Volume

Log

Volume

Log Volume

Log

Segment

Log volume contains log

segments

o Number of pre-formatted log

segments is configurable

o Log segments are closed when

they are full, or the log backup

timeout has elapsed

o After a log segment has been

successfully backed up, it is

released for overwriting

Data

Data area = all data volumes

1 data volume per service with persisted data

(per node)

Redo log

Log area = all log volumes

1 log volume per service with persisted data

(per node)


Backup and Recovery Advantages for Backups with HANA Kernel involvement

Structural knowledge of data in database kernel

Mini-verify of every page with relevant information during simple data and log backup

Header and Trailer verification of checksums ensures valid data in pages

Hardware problems get soon recognized and can be treated early enough w/o further

implications to general data consistency

OS-related or external tools dont offer this structural knowledge into HANA data types

Performance

Only occupied space is backed up

Throughput of up to 0.5 or 1 TB per hour and per host (scale-out case) reported in an

optimal situation

(There are a lot of ways like bad network throughput, slow NFS storage perf., no hardware

separation etc. to ruin such a good B&R performance)

Check Backup

General possibility to check also backups with data knowledge in kernel available

(please check SAP note 1869119 and 1873247 for further information)

https://service.sap.com/sap/support/notes/1869119https://service.sap.com/sap/support/notes/1873247


SAP HANA Server

SAP HANA Backup/Recovery Data backup: Only payload is backed up

Shared Backup

Directory

(staging area)

Name Server

Data

Index Server

Statistics Server

DATA_BACKUP_0001

DATA_BACKUP_0002

DATA_BACKUP_0003

Data

Backup

Savepoint

Data

Backup

Savepoint

Data

Backup

Savepoint

DATA_BACKUP_0000


Shared Backup Directory

SAP HANA Backup/Recovery Data backup: Single-node and scale-out systems

SAP HANA automatically handles the

synchronization of backups for all nodes

no special user interaction required

All services that persist data are backed up

o e.g. index servers, master name server)

Global data backup savepoint for all these

services

o Synchronized across all nodes and services

o Transactions are paused very briefly

o Savepoint is kept until the backup is finished

for all services. If a page is changed during

the backup, its written to a different location

(shadow page concept)

Data marked in the savepoint is read from

data volumes and written to backup files

o One backup file per service

o Parallelization Backup File

Name

Server

Index

Server

Savepoint

Name

Server

Index

Server

Savepoint

Master

Name

Server

Index

Server

Savepoint

Parallelization

Savepoint

Synchronized

backup

savepoint


SAP HANA Backup and Recovery Destinations for backups (I)

Backups to the file system

For both data and log backups

E.g. to an NFS share

For information on file systems:

SAP Note 1820529

Data backups

triggered/scheduled using SAP

HANA studio, SQL commands,

or DBA Cockpit, log backups

written automatically (unless

disabled)

SAP HANA

Database

Backup

Storage,

e.g. NFS

SAP HANA

studio

Create backup

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


SAP HANA Backup and Recovery Destinations for backups (II)

Backups to 3rd party backup server

For both data and log backups

Backint for SAP HANA API can be

implemented by a 3rd party backup agent

(certification required)

Provides functions for backup, recovery,

query, delete

3rd party backup agent runs on the SAP

HANA server, communicates with 3rd

party backup server

Backups are transferred via pipe

Direct integration with SAP HANA:

o Data backups to Backint can be

triggered/scheduled using SAP HANA studio,

SQL commands, or DBA Cockpit

o Log backups are automatically written to

Backint (if configured)

SAP HANA

Database

3rd Party

Backup

Server

3rd Party

Backup Agent

SAP HANA

studio

Backup/

recovery


SAP HANA Backup and Recovery Backint Certification

In December 2012 SAP released the certification process for Backint for SAP HANA. Certification is an

installation prerequisite for backup tools using the Backint for SAP HANA interface. SAP Note 1730932 (Using backup tools with Backint)

Release announcement

Certified tools (as of 2014-June)

Online listing of certified tools: http://www.sap.com/partners/directories/SearchSolution.epx SAP-Defined Integration Scenarios = "HANA-BRINT 1.1

Information for tool vendors: http://scn.sap.com/docs/DOC-34483

Vendor Certified Backup Tool Support Process

Symantec NetBackup 7.5 SAP Note 1913568

IBM Tivoli Storage Manager for Enterprise 6.4 SAP Note 1913500

Commvault Simpana 10.0 SAP Note 1957450

HP Data Protector 7.0; 8.0 SAP Note 1970558

EMC Data Domain SAP Note 1970559

EMC Networker 8.2 SAP Note 1999166

SEP Sesam 4.4 SAP Note 2024234

Dell Quest Netvault Backup - Planned -

https://service.sap.com/sap/support/notes/1730932http://www.saphana.com/community/blogs/blog/2012/12/18/backint-for-sap-hana-certification-available-nowhttp://www.sap.com/partners/directories/SearchSolution.epxhttp://scn.sap.com/docs/DOC-34483http://scn.sap.com/docs/DOC-34483http://scn.sap.com/docs/DOC-34483https://service.sap.com/sap/support/notes/1913568https://service.sap.com/sap/support/notes/1913500https://service.sap.com/sap/support/notes/1957450https://service.sap.com/sap/support/notes/1970558https://service.sap.com/sap/support/notes/1970559https://service.sap.com/sap/support/notes/1999166http://service.sap.com/sap/support/notes/2024234


SAP HANA Backup Backup in SAP HANA Studio


SAP HANA Backup and Recovery Destinations for backups (III)

1. Using SAP HANA studio, prepare

the database for the storage

snapshot. Technically, this

creates an internal data snapshot

2. Using the storage tool, create a

storage snapshot of the SAP

HANA data area

3. In SAP HANA studio, confirm the

storage snapshot as successful.

An entry including the external

backup ID is written to the backup

catalog

SAP HANA Database

External

Storage

Storage

Tool

SAP HANA

studio

Data Area (Disk)

Data snapshot

Prepare database

Create storage

snapshot

Confirm storage

snapshot

Storage snapshots as backups

SAP HANA also supports the creation of storage snapshots, which can later be

used for recovery


SAP HANA Backup and Recovery Creating a storage snapshot

Creating a snapshot

1. In the Systems view in SAP HANA studio, right-click on the system and choose Storage

Snapshot...

Then choose the Prepare option.

Alternatively, you can use the SQL command: BACKUP DATA CREATE SNAPSHOT COMMENT snapshot_test

2. Using the storage tool, create a storage snapshot of the SAP HANA data area

3. In SAP HANA studio, confirm the successful storage snapshot and enter the external

snapshot ID.

Alternatively, you can use the SQL command: BACKUP DATA CLOSE SNAPSHOT BACKUP_ID 3456789 SUCCESSFUL

'storage_id_12345

Storage snapshots are listed in the backup catalog. You can either display the

backup catalog in SAP HANA studio, or query it using SQL (system view

M_BACKUP_CATALOG).


Backup and Recovery Backups during normal operation of the database: Summary

Data backups

(external backup

destination)

1

Log backups

(external backup

destination)

2

Crash

4

Most recent

log entries

from log area

3

Time

To learn more about Recovery with missing log backups see SAP Note 1816483

or about How to recreate the backup catalog see SAP Note 1812057.

https://service.sap.com/sap/support/notes/1816483https://service.sap.com/sap/support/notes/1812057


SAP HANA Backup and Recovery Backup catalog

The backup catalog provides detailed information on data backups, log backups and storage snapshots, for example start/end time, duration, size, and throughput

The backup catalog is stored within the SAP HANA database, and also backed up as part of the log backup (even in log mode OVERWRITE). This allows for offline access to the backup catalog during recovery.


SAP HANA Backup and Recovery Starting a recovery

In the Systems view in SAP

HANA studio, choose

Recover... from the context

menu of the database and

enter the credentials of the

SAP HANA operating

system user adm

Caution: For a recovery,

the SAP HANA database

will be shut down


SAP HANA Recovery Recovery in SAP HANA Studio

You can use either a data backup

(from the file system or Backint), or

a storage snapshot as the basis for

the recovery


SAP HANA Backup and Recovery Recovery using a specified data backup or storage snapshot

You can use either a data

backup (from the file system or

Backint), or a storage snapshot

as the basis for the recovery


SAP HANA Backup and Recovery Recovery phases

After the initial collection of

system information for the

recovery, the recovery

wizard shows the following

phases:

Phase 1: Data recovery

using data backup or snapshot

Phase 2: Log recovery

using log backups and/or log

that is still available in the log

area

Phase 3: Restart


SAP HANA Backup and Recovery Recovery steps when using a storage snapshot

1. Using the storage tool, transfer

the storage snapshot to the data

area of the SAP HANA database

2. Using SAP HANA studio, recover

the database using the storage

snapshot as basis (available in

the recovery wizard)

Note: All recovery options are

available, including point-in-time

recovery using log backups/log

from the log area

Storage

Tool

SAP HANA

Studio

Recover database

Transfer storage

snapshot to

data area

SAP HANA Database

External

Storage Data Area (Disk)

Data snapshot


SAP HANA Backup and Recovery Database copy from m nodes n nodes

You can use database copies, for example, to create a copy of your

production system for tests on a smaller QA system

Note: If the target system has less resources, e.g. less CPU and RAM, performance

cannot be expected to be the same as in the source system

To copy a database

1. Create a data backup of the source database

2. In the target database, configure (m-n) additional index servers to match the source

system configuration (.ini file parameter). You can choose yourself how you want to

distribute these index servers across the available nodes

3. Recover the data backup of the source database into the target database

Note: Before the recovery is executed on the target system, SAP HANA will check whether

it has been configured appropriately


Storage System

Backup and Recovery Backup-based online database copy

Available since SAP HANA SPS4

SID and hostnames are adapted during the recovery process

Target database is started at the end of the recovery

No impact on in-memory processing on source; executed on persistence level

Storage System

Source Database

online

Database backup files Online

Database Backup

Database Recovery

Target Database

(copy)


Backup and Recovery Internal Snapshots in SAP HANA

SAP note: 1703435

Limitation: One internal Snapshot only right now

Conflicts with Backup Snapshot which is needed during backup execution time.

If an internal snapshot already exists when backup is started, the backup will not be

executed and an error presented.

Roadmap: multiple named internal Snapshots are planned



Backup and Recovery New features for database copies

SAP HANA database copy from PROD to QA or DEV allows to change the

topology in case of a Scale-out setup on PROD side:

Backups which are produced on scale-out landscapes with n hosts can be recovered to

one QA or DEV system.

Purpose is to offer a possibility for a light system copy without the full performance scope

like PROD

Ability to work on that copy limited by performance and restricted by tables/partition sizes

N 1

N M

PROD

QA, DEV

or Sandbox

Node 1 Index Server n

Index Server 2

Index Server 1

Node n

Index Server Node 2

Index Server Node 1

Index Server

Database inside changes


SAP HANA Backup & Recovery News with SAP HANA SPS08 and Beyond

Backup & Recovery

3rd party backup tools (Backint):

o New certifications: Commvault Simpana 10.0, HP Data Protector 7.0 and 8.1, EMC Interface for Data Domain Boost for Databases and Applications 1.0, EMC Networker 8.2, SEP Sesam 4.4

Minor optimizations in all kind of areas securing existing solutions

Involvement in future developments

SAP HANA SPS09 (current planning)

3rd party backup tools (Backint)

o Database copy using 3rd party backup tools

o Improved handling of log backups

o Improved tape handling

Enhanced scale-out support (e.g. remove host without necessity to write data backup)

Integrated support for extended storage in B&R of SAP HANA

Integrated Support for Multiple Database setups

New alerts for B&R operation

o Log backup taking too long

o Storage snapshot prepared

Planned beyond

Restartable recovery

Delta backup (increment/differential)

Additional options for backup staging using 3rd party backup tools

Offline log backup

Partial recovery

Configuration file backup

Further web-based backup/recovery functionality

Support for backup operations on secondary system in system replication scenarios

Additional options for backup lifecycle management e.g. integrity check for the backup catalog, option for manual log backup

Backup compression

Backup throttling






Persistence


High Availability

Disaster Recovery


Security & Auditing


High Availability Disaster Recovery

Business Continuity

High Availability

per Data Center

Disaster recovery

between Data Centers

SAP HANA Host Auto-Failover

(Scale-Out with Standby)

SAP HANA System Replication

SAP HANA Storage Replication

SAP HANA System Replication


SAP HANA High Availability Scale-Out or Host Auto-Failover

Sh

are

d S

tora

ge

SA

N S

tora

ge

Sto

ra

ge

C

on

ne

cto

r A

PI

Server 1

Server 2

Server 3

Server 4

Server 5

Server 6

Standby Server

High Availability configuration

N active servers in one cluster

M standby server(s) in one cluster

Shared file system for all servers

Services

Name and index server on all nodes

Statistics server (only on one active server)

Name server active on Standby

Failover

Server X fails

Server N+1 reads indexes from shared storage and connects to logical connection of server X

Evolution of Host Auto-Failover

Started with shared storage but no necessity since the Storage Connector

Storage Connector API ensures remount of necessary disk areas (Note 1900823 - Storage Connector API Attachments)

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


SAP HANA Architecture

SAP HANA Appliance

Software Update Manager

SAP Host Agent

SAP HANA Studio Repository

SAP HANA Database Node 2 Node n

Name Server

Index Server

Statistics Server*

Preprocessor

Index Server

Preprocessor

Index Server

Preprocessor

Single host configuration

Multi-node cluster configuration

Maintains landscape information

Holds data and executes all operations

Collects performance data about HANA

Text analysis pre-processor

Repository for HANA Studio updates

Enables remote start/stop

Manages SW updates for HANA

Shared storage for fail-over and recovery

SAP Host Agent SAP Host Agent

Name Server Name Server

XS engine XS engine XS engine XS engine


In-Memory

SAP HANA Database Landscape

Persistence Layer

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

LOG

DISK

DATA

DISK

*Standby Host:

Name Server (active)

Index Server (standby)

Distributed HANA

database even on a

single host with shared

nothing concept

Standby without own

persistence


HANA High Availability Host Auto-Failover (standby)

Different implementation of High Availability by HW partners

Using storage solution inside Using internal disk

Name

Server

Index

Server

Standby

Name

Server

Index

Server

Name

Server

Index

Server

Data

Disks

Log

Disks

Data

Disks

Log

Disks

Data

Disks

Log

Disks

GPFS

GPFS


HANA High Availability Video to present functionality of Auto Host Failover

Video: http://www.saphana.com/videos/1417

https://www.experiencesaphana.com/videos/1417https://www.saphana.com/videos/1417


SAP HANA High Availability Minimal Setup for Host Auto-Failover

Minimal setup for a Host Auto-Failover (Scale-Out):

2 Servers including one Standby

External storage or similar technology necessary which ensures the data provisioning to second node via external data location

This setup aims for High Availability not performance scaling or size.

Note: Some use cases (e.g. SAP BW powered by HANA) might have different requirements or recommendations for minimal setups (e.g. BW has a defined setup for SAP HANA Scale-Out SAP note 1736976 attached PDF).

Master

Name

Server

Index

Server

Data

Disks

Log

Disks

active standby

Index

Server

Name

Server



SAP HANA High Availability Client Management with Scale-Out

Clients:

During installation the clients get initial information about how to contact to HANA database often only one host is offered

To prevent single point of failure, more host should be offered in case of Scale-Out

The list is only necessary to establish a first connect to HANA cluster afterwards the client gets the full topology from the database Name Server anyway

The complete list of hostnames including the standby host should be stored

User store:

Contains the list of host names like hana1;hana2;hana3 etc. next to user and encrypted password information

All tools based on this database interface named sqldbc (SAP Appl. Server, hdbsql, ODBC, python, etc.) can use this user store.

Algorithm:

Round robin process is used to find this first contact point

SQL clients:

SAP Appl. Server hdbsql

User Store

hana1;hana2;hana3

round robin hana1 hana2 hana3

HANA Scale-Out

Data

Disks

Log

Disks

hana1

Name

Server

Index

server

hana2

Name

Server

Index

server

hana3 standby

Name

Server

Index

server





Persistence


High Availability

Disaster Recovery


Security & Auditing


HA & DR Concepts in general

RPO RTO

operation resumed

time

Sync or

backup

system operational

design & prepare detect recover perf. ramp

KPIs:

Recovery Point Objective (RPO) = worst-case data-loss

Recovery Time Objective (RTO) = time to recover from outage

*synchronous solution

Solution Used for Cost RPO RTO Perf. ramp

Backup & Recovery HA & DR $ high high med

SAP HANA Host Auto-Failover HA $ 0 med long

SAP HANA Storage Replication w/ QA, Dev. DR $$ 0* med long

SAP HANA System Replication HA & DR $$$ 0* low short

SAP HANA System Re

sap hana in data centers

Technology

Transcript of sap hana in data centers