Migration to SAP HANA: Overview of Migration Options for ... · SAP HANA Either without changing existing solutions (greenfield) Or for transforming existing solution to SAP HANA

Boris Zarske – Product Manager for System Provisioning at SAP

May 2014

Overview of migration options for ABAP-based SAP systems to SAP HANA

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 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 intentionally or grossly negligent.


Migration options Overview

Option 1:

New installation

You install new system on

SAP HANA

Either without changing existing

solutions (greenfield)

Or for transforming existing

solution to SAP HANA by

performing (selective) data

migration

Option 2:

Classical migration

To bring original system on

release supported by SAP HANA,

you perform update/upgrade

(if required)

Then, you classically migrate

your traditional database to

SAP HANA

Option 3:

One-step upgrade and

migration with DMO

You use database migration

option (DMO) that combines

upgrade and database migration

in one step

One process, one tool, one

downtime

Migration

1 2 3

SAP

System Traditional

DB


Migration options & tools 1. New installation for transformation

Overview

Address changes to existing solution landscape by transformation with

SAP Landscape Transformation software with reduced effort to build targeted landscape

(such as via shell creation with carve-out options + system consolidation)

Complemented by transformation services (such as Data Management Services

or System Landscape Optimization consulting services)

Benefits

Provides opportunity to correct design issues

– System consolidation

– Harmonize data as part of the migration (chart of account, master data)

Leveraged flexibility by offering selective migration

– Migrate only specific data without business disruption (such as of last two years)

– Combine data cleansing – leave unused master data behind

– Smoothly introduce new business processes (for example, new general ledger)

Minimized downtime service available

1

Challenges

Increased effort to deploy

(addressed by services)

For more information:

• See SAP Service Marketplace at:

http://service.sap.com/sapLT

• Contact: [email protected] –

subject: HANA

http://service.sap.com/sapLT

mailto:[email protected]


Migration options 2. Classical migration: overview

Overview

You perform upgrade (if required) + heterogeneous system copy with classical migration tools

Benefits

Results in nearly identical system

Minimal impact on functional teams

Separation of concerns

Challenges

Typically requires extended downtime (depending on DB size) and several downtime windows (depending

on scope)

With inclusion of upgrade, fallback to original state only possible via restore

1:1

Application

data, …

Repository

SAP

System Traditional

DB

Application

data, ...

Repository

SAP

System

1

2

2


Migration options 2. Classical migration: phases

Prepare Update/ Upgrade

Migrate

Split dual-stack

Convert to Unicode

Plan maintenance

Perform

maintenance

Migrate to

SAP HANA

Post-activities

SAP

System

1 SAP

System 3

2

SAP

System

SAP

System

2

For more information, see SAP

Service Marketplace at:

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





Involved migration tools 3. One-step upgrade and migration with DMO: overview

Prepare Update/ Upgrade

Migrate

Database Migration Option (DMO) of Software Update Manager (SUM)

Overview

Relevant steps in one tool and one process, “big bang” approach

Benefits

Manual effort and error-proneness reduced

Lower prerequisites for SAP and DB start releases

Only intermediate fallback effort, as original database could be reactivated

Downtime optimized (depending on scenario)

Only one downtime phase

3


Migration options 3. One-step upgrade and migration with DMO – phases during the procedure

Setup SAP HANA specifics (client, schema …)

6 Start SAP HANA-based system

4 Migrate application data (incl. data conversion)

5 Finalize upgrade

Downtime

Traditional

DB

Tim

e

Uptime

Switch database connection 3

1 Upgrade “Prepare”

2 Execute Upgrade (until downtime phase)

SAP

System

SAP

System

3

For more information, see SAP

Service Marketplace at:







Choosing the right option Standard recommendation

General Recommendation

DMO

is the standard procedure for

migrations to SAP HANA –

profit from a simplified

migration to SAP HANA with

minimized overall project costs!

Reasonable Alternative

Classical migration

If DMO does not fit your

requirements, consider to use

classical migration with

software provisioning manager

(continuously improved for this

migration use case)

Possible Exception

New installation for

transformation

In addition, there are further

migration procedures for special

use cases, such as system

consolidation or carve-out with

SLO Shell Creation

Use as starting point for

your individual assessment

For more information, see end-to-end implementation guides available at:

• http://help.sap.com/nw74/#section7 (SAP NetWeaver ABAP 7.4)

• http://help.sap.com/nw731bwhana#section2 (SAP NetWeaver BW)

http://help.sap.com/nw74/

http://help.sap.com/nw731bwhana


Migration service offerings SAP Rapid Deployment solutions and SAP Active Global Support offerings

For more information, approach

your local AGS contact person

For more information, see

SAP Service Marketplace at:

http://service.sap.com/rds

http://service.sap.com/rds


Summary

Database Migration Option has become the standard SAP HANA migration

option – one tool for an optimized migration procedure to SAP HANA

In case of special requirements (for example, in terms of landscape

transformation), SAP offers additional options to come to SAP HANA

1

3

2

Service offerings allow a rapid and risk-mitigated migration to SAP HANA

© 2014 SAP AG or an SAP affiliate company. All rights reserved.

Thank you

Contact information:

Boris Zarske

Product Manager for System Provisioning

[email protected]

mailto:[email protected]

© 2014 SAP AG. All rights reserved. 43

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft

Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,

z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered

trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or

registered trademarks of Adobe Systems Incorporated in the United States and/or other

countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are

trademarks or registered trademarks of Citrix Systems, Inc.

© 2014 SAP AG. All rights reserved.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World

Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, and other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG in Germany and other

countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,

Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and

services mentioned herein as well as their respective logos are trademarks or registered

trademarks of Business Objects Software Ltd. Business Objects is an

SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase

products and services mentioned herein as well as their respective logos are trademarks or

registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational purposes only. National

product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be

reproduced, copied, or transmitted in any form or for any purpose without the express prior

written permission of SAP AG.

Documents

Migration to SAP HANA: Overview of Migration Options for ... · SAP HANA Either without changing existing solutions (greenfield) Or for transforming existing solution to SAP HANA