Onboarding: How to Successfully Move SAP to the Cloud · PDF fileNew installation with data migration (with or without ongoing replication) ... SAP Migration Monitor, R3Load, custom

© Copyright 2016 Virtustream, Inc. All Rights Reserved.

Kausik Chaudhuri

Director & Practice Lead, Global SAP Onboarding & Migration Services

Onboarding: How to Successfully Move SAP® to the Cloud



Onboarding Mission

To provide the efficient

migration of new workloads

to the Cloud, improving

speed and reducing risk

Virtustream onboarding and migration services

Primary Services Provided

3

New customer setup

• Connectivity Establishment

• Storage and Compute Platform Provisioning

Project management and implementation

• Physical-To-Virtual Migrations

• Virtual-To-Virtual Migrations

• New (“greenfield”) Implementations

• SAP-Specific Migrations (HANA, OS/DB Platform

Changes, Unicode Conversions, Upgrades, etc.)

© Copyright 2016 Virtustream, Inc. All Rights Reserved.3

Virtustream-led onboarding services include:

• Detailed project planning

• Technical project management partnered with customer project management

• Technical migrations of applications for all SAP tiers

• P2V and V2V migrations using both onsite and offsite resources

• Technical checks of data consistency and performance of migrated systems

• Conversion to production operations of all approved systems

• Coordination of GoingLive™ Migration Checks with SAP

• Formal handover for transition to steady-state

Comprehensive SAP onboarding services


Cloud migration methodology

4

Planning phase• Technical preparation (project team w/OS/DB Migration Consultant)

• SAP GoingLive™ Migration Check where relevant (in source system)

Migration phases• Test runs for the migration (project team)

• Tuning and optimization in the target system (project team)

• Improvement of data transfer and flow of migration (project team)

• Further test runs until the production downtime requirements are met

Cutover and go-live• Migration of the production system (project team)

• Technical check of data consistency and performance (project team)

• Conversion of production operation to the target system (project team)

• SAP GoingLive™ Migration Checks in the target system

• Formal handover to Cloud Cover Services for ongoing operation


Plan• Document all applications and related

servers to be migrated

• Document related integrations

• Determine move sequencing

• Document testing scenarios, test scripts

• If it has to be done, it must be in the plan!

Cloud migration best practices

Practice Makes Perfect• Each repetition is an opportunity to refine

the plan, educate the team, hone the timing

and eliminate variables

• Mock Cutover to be highly scripted and

involve same participants as the final

cutover including the business users

1

2

3

Measure, Communicate and Execute• Baseline the project plan, then begin execution

• Continue planning on planning horizon

• Document risks, issues, plan changes, cutover plan tasks

• Weekly cadence for key meetings including steering committee

or PMO-type sessions


SAP cloud migration and installation factory

SOW is drafted based on identified

effort to get to target state

Build Team completes app

installation, upgrades and additional

migrations tasks tailored to

customers’ requirements

Technical Lead and PM

resources assigned

Automated deployment releases

“Golden” Physical or Virtual

optimized templates

Onboarding works with Network

Team to provide connectivity

and assign VLAN Virtustream

Cloud With Over

500 Successful

SAP Migrations

6

Customer

requests

environment

Virtustream cross-functional

architecture team reviews

requirements, then designs solution


Migration techniques and considerations

Considerations for each

server and/or each application

Existing technology and to-be

architecture

Ease of testing, availability of

testing resources

Amount of data

Number of related systems to be

moved in same outage

Production / non-production and

sensitivity / criticality

Available network bandwidth for

migration

Inputs lead to use of one of the

following methods

Backup and physically relocate to

co-location rack(s)

Virtual to Virtual migration (with or without ongoing replication)

Physical to Virtual migration (with or without ongoing replication)

New installation with data

migration (with or without ongoing replication)

Heterogeneous migration (DB export and re-platform OS and/or

DB)


• While every customer is unique – and

this fact can influence the project –

certain practices always apply.

• Flow follows typical General Computer

Controls “leading practices” and starts

with least impactful systems first

• The creation of a detailed “cookbook”

is the key to a successful recipe

• Practice makes perfect: a “mock” run is

essential to streamlining the production

run and minimizing risk

Flow of typical migration process

DEV

Mock

QA

PRD

Initiation

Cookbook

Validation

Refinement

Usage


Option Description Tools Pro Con

Standard SAP

Heterogeneous

Migration

Standard SAP end to

end concurrent

migration process

SAP Migration

Monitor, R3Load,

custom scripting

Start imports near

start of DT

Depends on WAN,

storage and compute

Target Side Temp

Hardware (*)

Replicate to Target,

migrate at cutover

local

Temp source OS

based server on

target, log shipping

Takes WAN out of

downtime

Additional hardware

requirement

Portable Media (*) Export to portable

media and ship

NAS Avoids load on WAN Depends on export,

ship, import serially

SAP nZDT (*) SAP near zero

downtime

SAP tools, service Low downtime,

move only changes

Cost & Complexity to

SAP Std.

Virtustream

Optimized (*)

Custom scripting

together with SAP

tool

SAP SWPM,

MigMon, SLT

Low downtime,

move only changes

Less complex and

less expensive than

SAP nZDT

(*) Not part of standard SOW. Additional analysis required for pricing.

Optimization options and considerations

9


Enhanced V2V migration overview


Virtustream governance recommendation

Project Leads

Senior Work Stream Leads

Work Stream Managers

Team Members

Quarterly Business

Reviews & As Needed

QBR & Monthly Status

Weekly As Needed

Monthly Status Call &

Weekly Status Calls

Weekly Status Calls &

Daily As Needed

Daily

Communication

Migration

Project

Ongoing

Operations

Twice Monthly &

As Needed

Weekly &

As Needed

Twice-Weekly &

As Needed

Daily As

Needed

Daily

Communication

Executive Sponsors

27

Onboarding: How to Successfully Move SAP to the Cloud · PDF fileNew installation with data migration (with or without ongoing replication) ... SAP Migration Monitor, R3Load, custom

Documents