Best Practices for Data

Center Migration Planning

Lex Crosett, Enterprise Solutions Architect

August23,2016

© 2016. Amazon Web Services. Inc. or its Affiliates. All rights reserved !eT J Webinars
Or...

There must be fifty ways to leave your

data center. t-
Agenda

• Cloud adoption and setting a strategy

• AWS process recommendations and methodology

• Program, tool and process offerings

• The hybrid trap

• Steps to refine a migration plan

• Key takeaways
AWS Cloud Adoption Framework

Define Dellne EA
Go1Jernance Train1n9 and Policies and
S1ructure Certifica ion Practices

Define Seoority
Analysas Requirements

CAF Web site

Whitepapers
Find a Migration Partner
Cloud A doption is not binary!
 Many Worry There are Only Two Choices

Build a "Private" Cloud Rip everything out and

move to AWS

You don't need to be coy, Roy, just set yourself free ,;,
The journey to AWS is a well-trodden path

ALL IN
ALL TOGETHER NEW

1 2 3 4
Rational Expectations of Management

Migration project will have predictable

• Start and end dates
• Direct Cost
•
Overlapping cost will be predicted and budgeted
Capital Expense
• will drive to zero during migration (e.g. only repairs)

Operating Expense
• will increase significantly due to overlapping costs
• then fall below the previously budgeted level when DC closes

Otherwise, plan to slip out the back, Jack /I

 Typical Data Center Cost Structure
Colocation/Managed Data Center
Services

Database Maintenance and

Support

Storage Maintenance and

Support

Software Licenses

Server
maintenance
Descending cost
a·rcui ,5
AWS 6-R Tactics of Application Migration
On-premise

@
Retain
Retire

Repurchase

Rehost EC2

ELB

Re latform

Refactor
Migration Process View
Manual Install

Us &ration Tools
tc

Manual 04lploy

Oet rmil Modlf y und liytna

new plnf orm Infrastructure

Discover/ Assess/Prlorktze Validation Tra n Uon Production

Applications I
I
I
I Purcha COTS/
Ret n/
Not Moving I Sa aS & lloen51ng

Aetre I
Oec:ommlwon R d n App Code Full ALM / Int tlon
Appllcatlon/ Development SDLC
lnfrutructur Arch ctur
 Migration Process Detail
Label Name Pattern Description Examples

Application and host decommission on source Existing Decomm Program Scope

Retire No migration to target SunOS, SCO;
Application owner approvals needed Clustered host for DR, alternative HA hosts

t:: Customer will keep host I application in their source environment Mainframe
0
AIX host I applications

<V
Minimal analysis/validation of scope and application affinity
I t: Retain
w a Dependency on integrating service management Specific GEO locations (exceptions)
Q) Some host will need to be Re-hosted into target (i.e. Lift and Shift)
C>
c: Like for Like application migration to target cloud Simple to Medium V2V, P2V
cu
.c: Minimal effort to make the application work on the target cloud infrastructure Storage: Local to DASD

- 0
(.)
Rehosting (Minimal application layout change) RHEL 6 above
c: Storage migration will be needed (without conversion) Win 2008 above
0 UAT - Some level of application testing
:o:; Lift & shift
cu
N Up-Version of the OS and/or database onto the target cloud (same type) W2K3 to Win 2012; Win 2008 below; RHEL
c:
i...
Q)
Storage migration will be needed (without conversion) below; Oracle 8 to 1 1; All databases
"C Replatform Some level of application changes New application releases
0
Application reinstallation on the target All clusters (MS cluster, DR)
:::!!:
UAT is highly recommended MS SQL same technology (RDS)
c:
0
:o:; OS and/or database porting (changing OS or database type) AIX to Linux
cu

0
0 Middleware and application change to cloudify an application Oracle to SQL; SQL to Aurora
Refactoring Middleware, IBM products
Data conversion; Database to AWS RDS
0..
a. UAT required
<C
Application architecture changes may also require Up-Version or Porting Any custom application chg
Re-Purchasing I Complex I Highly complex application
Middleware, data modernization; application consolidation I stacking
Re-Architect migration
UAT required; HPCGrid, No ITIL
 Speed of Large Migration

A Retail Commerce
11
Manual Discovery
Manual Migration

An Australian Bank
. . . . .. . . - JJ1 ......... . . - . Auto + Manual Discovery
Auto Migration
Speed of Small Migration

Oil & Gas Company (Sprint 6)

= i:J Auto Discovery
Auto Migration

1?ays
)Servers L - - - -
eople
Customer Migration Examples

Conde Nast migrated 500 servers, 1PB of

storage, mission critical applications, and
100 database servers in 3 months to AWS.

General Electric (GE) is migrating more than 9,000 workloads,

including 300 disparate ERP systems, to AWS while reducing its
datacenter footprint from 34 to four over the next three years.
Looks good, but how best to lower risk?

• Focus on training the team while doing the work alongside the professional services
staff (Center of Excellence)

• Financial planning and ROI analysis - budget for overlapping expenses

• Discuss the merits of DEV/TEST and new project first approach - does this really
make financial sense?
Looks good, but how best to lower risk (cont)?

• Consider avoiding the "hybrid trap" by moving the most difficult workloads first

• Understand that traditional project management will not work well

• Minimize risk at each phase by using agile methods

 Overlapping Costs/Month
200,000

180,000

160,000

140,000

120,000

100,000

80,000

60,000

40,000

20,000

Q1 2015 Q2 2015 Q3 2015 Q4 2015 Q1 2016 Q2 2016 Q3 2016 Q4 2016

- COLO PROVIDER - AWS

The journey to AWS is a well-trodden path

ALL IN
ALL TOGETHER NEW

Hybrid trap

1 2 3 4
How to Refine Migration Tactics

Lower the overlapping burn rate - this can create real pain
• ($data center + $AWS)/time

Maximize pain relief (current app performance, ticket count, high severity events)

Help the finance team budget for the CAPEX/OPEX transition and planning