AWS re:Invent 2016: Workshop: Migrating Microsoft Applications to AWS (ENT216)
-
Upload
amazon-web-services -
Category
Technology
-
view
136 -
download
1
Transcript of AWS re:Invent 2016: Workshop: Migrating Microsoft Applications to AWS (ENT216)
© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Lou De La Torre, Solutions Architect
November 29, 2016
Workshop: Migrating Microsoft
Applications to AWS
ENT216
What to Expect from the Session
• Why customers are migrating Microsoft applications to
AWS
• Success factors for planning an application migration
• Key takeaways
• Workshop
• Before you architect
• Form your teams and design!
• Design presentations and discussion
Timeline
Time Topic
5 Min Welcome and introductions
5 Min Why customers are migrating Microsoft applications to AWS
15 Min Success factors for planning a Microsoft application migration
5 Min Key takeaways
5 Min Before you architect
70 Min Form your teams and architect
45 Min Architecture and migration strategy presentations
Why Customers Are Migrating
Microsoft Applications to AWS
Flexible
Why are customers migrating Windows
applications to AWS?
Secure Reliable High-Performance Familiar Cost-Effective Extensive
Optimization for Windows-based workloads
Wide range of scalable services
Alignment with business needs
Key solution scenarios
AWS for Windows is familiar
“We didn’t have time to re-design
applications. AWS could support our legacy
32-bit applications on Windows Server
2003, a variety of SQL Server and Oracle
databases, and a robust Citrix environment.”
- Jim McDonald, Lead Architect, Hess
Corporation
Windows-based application support
Your own servers
Utilize existing VMs
License as you see fit
Same tools as on-premises environments
Success Factors for Planning
an Application Migration
Let’s get started…
How to successfully plan for an application migration to
AWS
Migration
Common questions
• I am not sure what I have. How can I assess my
environment?
• Where do I start?
• What tools can/should I use?
• Who can help me?
• Is there a process that can guide me?
• How long should it take?
Migration process “mental model”
1) Evaluate
opportunity
2) Discover,
Analyze, and
Plan
3) Application
Design
4) Migrate,
Integrate, and
Validate
5) Operate and
Optimize
Application 3 Application 3
Application 2 Application 2
Application 1 Application 1Existing IT
EstateScoped
Migration
New Operating
Model
Portfolio discovery
Tools should automate your discovery process
and can be classified as:
• Agent-based vs Agentless
• Port-scanning vs Packet-scanning
• Appliance-based vs SaaS offering
Application discovery & planning tools
• AWS Application Discovery Service
• Risc Networks
• Cloudamize
• Atadata
Application migration tools
• AWS Server Migration Service
• Atadata
• Cloud Endure
Cloud migration strategiesMigration
Pattern
Label
Migration
Pattern NamePattern Description Example
Retain
Client will keep host / application in their source environment Minimal analysis/validation of scope and application affinity Dependency on integrating service management
Mainframe
UNIX host / applications
Retire*
Application and host decommission on source No migration to target Application owner approvals needed
Existing Decomission Program ScopeUNIX, SCO; Clustered host for DR, alternative HA hosts
Re-Hosting*
Like for Like application migration to target cloud Minimal effort to make the application work on the target cloud
infrastructure (Minimal appl layout change) Storage migration will be needed (without conversion) UAT - Some level of application testing
Simple to Medium V2V, P2V
Storage: Local to DASD
RHEL 6 above
Win 2008 above
Re-Platform*
Up-Version of the OS and/or Database onto the target cloud Storage migration will be needed (without conversion) Some level of application changes Application reinstallation on the target UAT is highly recommended Database to AWS RDS
W2K3 to Win 2012; Win 2008 below; RHEL
below; Oracle 8 to 11; All databases
New application releases
All clusters (MS cluster, DR)
MS SQL same technology (RDS)
Refactor*
OS and/or Database porting Middleware and application change to cloudify an application Data conversion; Database transition to MySQl, Aurora, etc. UAT required
AIX to Linux
Oracle to SQL; SQL to Aurora
Middleware, IBM products
Re-Purchase*
Replacing the application with a SaaS offering or COTS product Purchasing a cloud-compatible license
Oracle PeopleSoft
R1
R2
R4
R5
R6
Ap
plic
atio
n M
od
ern
izat
ion
/ C
han
ge E
ffo
rt
* Reduces TCO
R3
Comparing cloud migration strategies
Time Cost Agility
Retain + + N/A
Retire + + N/A
Re-host ++ ++ ++
Re-purchase +++ ++++ +++
Re-platform +++ +++ +++
Refactor ++++ ++++ ++++
Low
High
Mig
ratio
n C
om
ple
xity
Cloud migration strategy
Discover/Assess/Prioritize
Applications
Use Migration Tools
Cutover
Retain /
Not
Moving
App Code
Development
Purchase COTS/
SaaS & licensing
Validate
Modify underlying
Infrastructure
Full ALM /
SDLC
Manual Config
Manual
Deploy
Manual
Install
Retire /
Decommission
Determine
Migration
Path
Automate
Manual Install
& Setup
Integration
Determine
new platform
Operate
Contingency plan
Discover/Assess/Prioritize
Applications
Use Migration Tools
Cutover
Retain /
Not
Moving
App Code
Development
Purchase COTS/
SaaS & licensing
Validate
Modify underlying
Infrastructure
Full ALM /
SDLC
Manual Config
Manual
Deploy
Manual
Install
Retire /
Decommission
Determine
Migration
Path
Automate
Manual Install
& Setup
Integration
Determine
new platform
Operate
Planning your cloud migration
Now that you’ve gathered all the application and performance metrics for each server/application and have done a complete analysis and have consulted with the business/technology teams:• Decide on a migration strategy.
• Retain; Retire; Re-purchase; Re-host; Re-platform; Re-factor
• Decide on a priority and build the migration backlog.• Identify tools to help facilitate the migration.• Start to architect and design what the operational landing
zone will look like.
Getting ready for migration planning
Before you can create a detailed plan for your cloud migration project, you must have:• A final architecture for the target environment in the AWS
Cloud.• Understand hybrid connectivity with the target cloud
environment.• A discovery of your cloud migration portfolio.• Details of the application owners.• Come up with a contingency plan to ensure that the blast
radius is small is contained if there are issues.
Migration planning final planning
• Network connectivity• Migration tools• Monitoring• Amount of data• AWS service limits (soft and hard)• On-premises limitations• Test plans for the application and your users• Cutover plans• Escalation and operational plans• Define success criteria• One last baseline performance analysis of the source environment
for comparison to the new environment.
Migration validation, integration, and cutover
Migrate Validate Cutover
Integrate
Key takeaways
• Customers find AWS to be a good landing place for
Microsoft applications
• Leverage the Cloud Adoption Framework to successfully
plan your application migration to AWS
• Each application has its own set of requirements;
therefore, determine which of the 6 R’s is best for your
applications
• Have a rollback plan
• Leverage AWS and Partner Migration Tools
• Test, validate, get signoff, and cut over
Workshop
Before You Architect
• Meet your team
• Choose your scribe
• Choose your presenter(s)
• Read the case study
Guidelines for meeting the deadline
• Determine who knows what
• Divide and conquer tasks
• Listen to new ideas and approaches
• Get something on paper quickly and iterate, iterate,
iterate
• Save a few minutes at the end to compose your
presentation
Timeline
Time Topic
5 Min Welcome and introductions
5 Min Why customers are migrating Microsoft applications to AWS
15 Min Success factors for planning a Microsoft application migration
5 Min Key takeaways
5 Min Before you architect
70 Min Form your teams and architect
45 Min Architecture and migration strategy presentations
Presentations
Thank you!
Remember to complete
your evaluations!
Additional resources
Web Pages
Microsoft on AWS
http://aws.amazon.com/windows/
AWS Cloud Adoption Framework
http://aws.amazon.com/professional-services/CAF/
Reference Deployment Quickstart
http://aws.amazon.com/quickstart/
AWS Windows and .NET Developer Center (with sdk)
http://aws.amazon.com/net/
Amazon EC2 Windows Guide
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/
Microsoft Licensing on AWS
http://aws.amazon.com/windows/resources/licensing/
Whitepapers
Implementing Active Directory Domain Services on AWS
Implementing Microsoft Windows Server Failover Clustering
and SQL Server AlwaysOn Availability Groups in the AWS
Cloud
Remote Desktop Gateway Reference Architecture
Exchange on AWS Implementation & Planning Guide
Secure Microsoft Applications on AWS
more at http://aws.amazon.com/microsoft/whitepapers
Contact Us
https://aws.amazon.com/microsoft/contact-us/
If you have either business or technical questions about running
Microsoft software on AWS, please don’t hesitate to contact us.
Related Sessions
WIN301: Bring Microsoft Applications to AWS to Save Money and Stay Licensing Compliant
Tues, Nov 29 3:30-4:30 PM Venetian H
WIN204: How to Move 1,000 VMs and Biz Critical Apps to AWS in 6 months. Edwards Lifesciences
Tues, Nov 29 3:30-4:30 PM Venetian H
WIN303: How to launch a 100k user Microsoft back office and not break a sweat
Wed, Nov 30 5:30-6:30 PM Delfino 4004
WIN304: Design, Deploy & Optimize SharePoint on AWS
Wed Nov 30 12:30-1:30 PM Venetian, Level 3, San Polo 3403
WIN305: Best Practices for Integrating Active Directory with AWS Workloads
Wed, Nov 30 5:00-6:00 PM Venetian H
WIN306: Design, Deploy & Optimize SQL Server on AWS
Thurs, Dec 1 5:30-6:30 PM Venetian H