© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Lex Crosett, Enterprise Solutions Architect

August 23, 2016

Best Practices for Data Center Migration Planning

Or…

There must be fifty ways to leave your data center.

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

CAF Web siteWhitepapers

Find a Migration Partner

Cloud Adoption is not binary!

Many Worry There are Only Two Choices

Build a “Private” Cloud Rip everything out and move to AWS

#1 #2

You don't need to be coy, Roy, just set yourself free

DEVELOPMENT& TEST

ALL TOGETHER NEW APPLICATIONS

DIGITAL

ANALYTICS

MOBILEDC MIGRATION

MISSIONCRITICAL APPS

ALL IN

1 2 3 4

The journey to AWS is a well-trodden path

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

Typical Data Center Cost Structure

Colocation/Managed Data Center Services

Database Maintenance and Support

Storage Maintenance and Support

Software Licenses

Server maintenance

Networkcircu

its

Descending cost

AWS 6-R Tactics of Application Migration

Retain

SaaS on

EC2

ELB

Auto Scaling

RDS

On-premise

Retire

Repurchase

Rehost

Replatform

Refactor

Migration Process View

Migration Process DetailLabel Name Pattern Description Examples

Retire Application and host decommission on source No migration to target Application owner approvals needed

Existing Decomm Program ScopeSunOS, SCO; Clustered host for DR, alternative HA hosts

Retain Customer will keep host / application in their source environment Minimal analysis/validation of scope and application affinity Dependency on integrating service management Some host will need to be Re-hosted into target (i.e. Lift and Shift)

MainframeAIX host / applicationsSpecific GEO locations (exceptions)

Rehosting

Like for Like application migration to target cloud Minimal effort to make the application work on the target cloud infrastructure

(Minimal application layout change) Storage migration will be needed (without conversion) UAT - Some level of application testing

Simple to Medium V2V, P2VStorage: Local to DASDRHEL 6 aboveWin 2008 aboveLift & shift

Replatform

Up-Version of the OS and/or database onto the target cloud (same type) Storage migration will be needed (without conversion) Some level of application changes Application reinstallation on the target UAT is highly recommended

W2K3 to Win 2012; Win 2008 below; RHEL below; Oracle 8 to 11; All databasesNew application releasesAll clusters (MS cluster, DR)MS SQL same technology (RDS)

Refactoring OS and/or database porting (changing OS or database type) Middleware and application change to cloudify an application Data conversion; Database to AWS RDS UAT required

AIX to LinuxOracle to SQL; SQL to AuroraMiddleware, IBM products

Re-Purchasing / Re-Architect

Application architecture changes may also require Up-Version or Porting Middleware, data modernization; application consolidation / stacking UAT required; HPC Grid, No ITIL

Any custom application chgComplex / Highly complex application migration

R1

R2 /R2a

R3

R4

R5

R6

App

licat

ion

Mod

erni

zatio

n / C

hang

e Ef

fort

4 Months500 Servers

5+ People

An Australian BankAuto + Manual DiscoveryAuto Migration

24 Months800 Servers10+ People

A Pharmaceutical CompanyManual DiscoveryManual Migration

A Retail CommerceManual DiscoveryManual Migration

6 Months / 150 Servers10 People

Speed of Large Migration

2 Months50 Servers25 People

Oil & Gas Company (Sprint 0)Manual DiscoveryManual Migration

A Media CompanyManual DiscoveryAuto Migration

5 Days35 Servers5 People

Oil & Gas Company (Sprint 6)Auto DiscoveryAuto Migration

0.5 Month60 Servers

5 People

Speed of Small Migration

Customer Migration Examples

Condé 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?

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

Looks good, but how best to lower risk (cont)?

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

20,000

40,000

60,000

80,000

100,000

120,000

140,000

160,000

180,000

200,000

Overlapping Costs/Month

COLO PROVIDER AWS

DEVELOPMENT& TEST

ALL TOGETHER NEW APPLICATIONS

DIGITAL

ANALYTICS

MOBILE

DC MIGRATION

MISSIONCRITICAL APPS

ALL IN

1 2 3 4

The journey to AWS is a well-trodden path

Hybrid trap

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

First Step – Planning – Set the Goal PostsExample: Move one data center location and shut it down altogether in 9 months elapsed time To include all applications With some thoughts on the order of application migration With a reasonable buffer for cleanup and recycling of equipment

Review the relevant contracts, such as Colocation Storage Database (may be migrated) Circuits (bandwidth)

and determine whether the contract end points match the project end point. If not, get concessions from the vendors or change the target

Iterate on the right project target until the project and major contract end points line up.Order a Direct Connect circuit

Second Step – Budgeting and Risk Management

Develop an overlapping cost model with a project completion buffer Add initial AWS training costs for all staff members who will be involved

(PM, Dev, QA, Sys Admins, DevOps). Don’t start the project without starting training.

Consider an agile transition and training - Use Kanban for IT work, Agile Scrum for development work.

Hire an experienced AWS consulting partner to help the team through 50-75% of the project

Create a graduated capital budget that declines as the project succeeds

Third Step – Training, Leadership

Identify a “servant leader” who is empowered to make the right decisions and drive the team.

Identify a strong project manager (not the same person) Start the training effort (cloud and agile, if appropriate) Work with the partner to create the target architecture and implement

the initial skeleton design. Get the Direct Connect and governance systems working well

Fourth Step – Creating a Backlog

Use the AWS Application Discovery service to create a full server inventoryCreate a master spreadsheet of applications Tools create dependency maps Dependency drives migration order Identify storage arrays and related devices Identify databases

Review contracts again – match dependencies to contract terms and datesBuild a backlog of work for the teams using the inventorySelect an automated migration tool that will work with AWS ADS

Fifth Step – Organize for Effectiveness

Split up the migration team into thirds, create a migration factory – place partner staff on each team. Team 1 - Dev and Sys Admins – understand and categorize applications if documentation not available. Team 2 – QA and Sys Admin – setup new infrastructure (use CloudFormation or related DevOps

approach, create functional and dependency documentation), test and verify the applications. Team 3 – Sys Admins – Deploy the migrated applications and snapshot as needed (deployment

window used where possible). This team manages any problems during deployment.

Scrum/Kanban meeting first thing in the morning for each team, standard formatWeekly full project status review – PM has full authority to escalate to senior management when serious difficulties arrive.Monthly roll-up to display progress versus plan with management

Final Step – Factory Operation

Use the AWS Migration tools and capabilities to lower risk Iterate weekly and be willing to change the strategy to hit the end goal Focus on retiring high cost items and recycling (storage arrays, blade cabinets, etc.). Move the gear out after a fallback period to minimize the physical work at the end. Realize that a fixed project endpoint is not worth the effort to calculate, and that it will

change many times.

AWS Services Can Make This Easier

ConsultingTraining &

Certification

Data Migration

Database Migration

Application Migration

AWSPartner Network

SnowballS3 Transfer AccelerationKinesis Firehose Storage Gateway

Database Migration ServiceSchema ConversionTool

Application Discovery Service

The answer is easy if you take it logically..

Data Migration Services

AWS Import/Export

Snowball

Amazon S3 Transfer

Acceleration

Amazon Kinesis

Firehose

AWS Storage Gateway

AWS Direct Connect

I'd like to help you in your struggle to be free..

AWS Application Discovery Service streamlines planning for your cloud migration

Hop on the Bus, Gus..

AWS Application Discovery Service

Identify applicationInventory

Map applicationdependencies

Baseline system and process performance

Automate data center application discovery

Make a new plan, Stan..

AWS Database Migration Service

Migrate databases with zero downtime Continuously monitors source and target

database and keeps them synchronized Simple to use via a few clicks in the console Can convert between engines and even

consolidate multiple databases Wide engine support: MySQL, MariaDB, SQL

Server, Oracle, PostgreSQL, Aura

AWS Database Migration Service

Key Planning Takeaways

Use of lean methods is sensible for managing and prioritizing migration work, as long as the team is being trained formally along the way

Picking the right project approach and workload migration priority will drive ROI and can decrease migration pain and project length

Professional services should be used to minimize mistakes and get project velocity up, but not to power all of the work

Key Planning Takeaways (cont.)

Avoid the hybrid trap by migrating and shutting down high burn rate items early in the migration process

Moving storage and databases is hard but minimizes project risk overall, plan to do this first

Overlapping costs are often the common project enemy, not technology

Next Step: Talk to your AWS Account Team!

Helpful Resources

Cloud Adoption Framework

CAF Whitepapers

AWS Import/Export SnowballAmazon Kinesis Firehose

Amazon S3 Transfer Acceleration

AWS Storage Gateway

AWS Application Discovery Tool (new)

AWS Database Migration Service

Stephen Orban’s Blog

Drop off the key, Lee, and get yourself free

Thank you!

Lex Crosettcrosettl@amazon.com