SAP HANA in Data Centers

(1)

SAP HANA in Data Centers

Dr. Ralf Czekalla

Product & Management Strategy (SAP HANA)

(2)

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

(3)

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

(4)

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

(5)

availability

SAP HANA Continuous Availability

Customer Expectation: Planned & Unplanned

Planned downtime Unp la n n e d d o w n ti m 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

(6)

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

(7)

SAP HANA in Data Centers:

Agenda

Introduction & Overview

Platform & Appliance methodology (Installation & Update)

Persistence

Disaster Recovery

(8)

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 p p lia n ce O p e ra tio n C o n ce p ts 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

(9)

SAP HANA Platform

SAP HANA Technology Partners SAP HANA Hardware Partners

Starting with HANA SPS08:

Linux on IBM Power CPUs

(10)

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

(11)

© 2014 SAP SE. All rights reserved. 16 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 <1TB 4 4-8 X X X X X X X 1TB 4 4-8 X X X X X X X X X X X 1.5TB 4 4-8 X X X X X 2TB 4 4-8 X X X X X X X X X 3TB 4 4-8 X X X X X X <2TB 8 8 X X X X X X 2TB 8 8 X X X X X X X X X 4TB 8 8 X X X X X X 6TB 8 8 X X X X X X X 12TB 16 16 X controlled _available

Inst. image with virtualization X X X X X planned

Support for SUSE SLES‡ X X X X X X X X X X

Support for RedHat RHEL‡ X X X X X

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

C P U s S o c k e ts M e m o ry S iz e s B W o r D a ta m a rt S u it e

(12)

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)

C P U s S o c k e ts M e m o ry S iz e s B W or D at am ar t S uit e

(13)

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)

(14)

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 _ServerHANA

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

(15)

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

(16)

SAP HANA tailored data center integration

What‘s 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

(17)

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

(18)

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 HWC@sap.com

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

(19)

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

(20)

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.

(21)

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

(22)

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:

sap_hana_tailored_data_center_integration@sap.com

.

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.

(23)

SAP HANA Tailored Data Center Integration

Enterprise Network

1 Application Server Network 2 Client Network 3 Data Source Network

4 Internode Network

6 Enterprise Storage Network 7

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

(24)

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 customer’s 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

(25)

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 C

PU s o ld C PU s o ld C PU s o ld C PU s o ld C PU s n e w CPUs n e w CPUs n e w CPUs x TB CPU power

(26)

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

(27)

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

(28)

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)

(29)

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 <HDB> 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 <HDB> <HDB> “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 <HDB> Schema XYZ White-Listed Scenarios V ir tu a liza ti o n V ir tu a liza ti o n B a re M e ta l B a re M e ta l

(30)

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

(31)

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

(32)

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 SID‘s 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

(33)

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)

(34)

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

(35)

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)

(36)

SAP HANA Enterprise Cloud

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 HANA Enterprise Cloud

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

(37)

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

(38)

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 http://www.saphana.com/docs/DOC-4192

(39)

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:

(40)

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

(41)

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 run‘s 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.

(42)

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

(43)

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

(44)

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

(45)

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

(46)

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

(47)

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 …

(48)

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

(49)

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 SAP’s 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

(50)

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

(51)

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

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

* 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

(52)

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)

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

(55)

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

(56)

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 1

Continously and after each COMMIT, redo log is written to disk (log area)

2

Power failure

3

(57)

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

(58)

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

(59)

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 Adapters Built-In

Third Party Adapters

SAP HANA Studio

(60)

SAP HANA Persistence

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

(61)

SAP HANA in Data Centers:

Agenda

Platform & Appliance methodology (Installation & Update) Persistence

Backup & Recovery (System Copy)

High Availability Disaster Recovery

(62)

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

(63)

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)

(64)

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 don’t 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)

(65)

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

(66)

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, it’s 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

(67)

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

(68)

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

(69)

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

(70)

SAP HANA Backup

(71)

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

(72)

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

(73)

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

(74)

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.

(75)

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 <SID>adm

Caution: For a recovery, the SAP HANA database will be shut down

(76)

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

(77)

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

(78)

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

(79)

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)

(80)

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

(81)

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)

(82)

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.

(83)

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

(84)

SAP HANA Backup & Recovery

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 backu}