Luke Notley Migrating from AWS to Azure Seamlessly CLD32 1

Preview:

Citation preview

Spark the future.

Luke Notley

Migrating from AWS to Azure Seamlessly

CLD321

About Me- CTO @ DiverseIT since July 2014- Prior to that I ran my own cloud/hosting

company in Perth- Working with Cloud services circa 2008- Completed various datacenter and cloud

migrations

Agenda- Migration “Must Do” Prerequisites- Setting up a VPN between AWS and Azure- Useful Migration Tools and Methods- Those hidden Gotcha’s

Must Do Prerequisites

Prerequisites* Assess current usageAWS Bill

* Assess currently accessed servicesVPC Flow Logs, CloudWatch MetricsApplication logs, Event logs, Webserver logs, ELBWhat is accessed externally over the internet or via a VPN?

* Document Current ConfigurationHow do you know what needs to be created within Azure?Azure Virtual Machines Readiness Assessment tool / Microsoft Assessment and Planning (MAP) Toolkit

* Document Migration PlanWhat are all of the application dependencies?

Example AWS Bill with details

Example CloudWatch Metrics

Example Configuration Template

Microsoft Excel Worksheet

Powershell toolkit for AWS to gather information

VPN Between Azure and AWS* Establish Azure VPN GatewayThis will be the primary gateway and AWS will “dial into” the Azure Gateway

* Ensure you have at least 1 VM AzureWithout a VM, the Azure Gateway will not allow you to “Connect”

* Provision a Windows 2012 R2 VPN Server in AWSEnsure it has network connectivity to all VPC networks in AWS which are being migrated

* Connect!

Establish Azure VPN Gateway• Establish Your Azure Networks• Define your AWS “Local” networks• Configure Azure VPN Gateway (takes up to 30 minutes)• Make sure gateway type is “Dynamic!”

Windows VPN Server in AWS• Ensure it has network connectivity to all VPC networks • Use the script generated from Azure to configure• Dial on Demand will save you $$$• Ensure passphrase is correct and changed regularly

Question?• Why can we not establish a VPN natively between AWS VPN Server within a VPN and Azure Gateway?

DEMO

Luke Notley

Useful Migration Tools and Methods* Treat the migration like DC to DCThe same principals apply, whether on-premise or not

* Keep it simple!Don’t overcomplicate the migration

* Use native application methods where possibleSometimes the best tools are right under your nose

* Augment native methods with toolsMicrosoft tools, Azure, 3rd party applications

Treat the migration like no other• Testing criteria is the same as DC to DC• Still watch out for data consistency• Testing Testing Testing!

Use Native Application Methods• Exchange Replication• SQL Mirroring/Replication• DFS• Robocopy!• Clustering

Augment Native Methods with Tools• Azure Site Recovery Services• Syncovery (File Based)• Double Take Move (In Guest Agent)• Zerto• Any tool which allows you to install “in guest” agents to perform data replication

DEMO

Luke Notley

Those hidden Gotcha’s!• AWS Network and Firewall ACL’s!• At least 1 Azure VM required in your Azure Network• If multiple networks, ensure routing is configured• Test Test Test• Application Dependencies• DNS (external and internal)

Useful LinksAWS – Configuring VPC Flow Logshttp://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs.html

Powershell Toolkit for AWShttps://aws.amazon.com/powershell/

Useful LinksMigration Tool - Syncoveryhttps://www.syncovery.com

Azure Site Recoveryhttps://azure.microsoft.com/en-us/services/site-recovery/

Complete your session evaluation on My Ignite for your chance to win one of many daily prizes.

Continue your Ignite learning pathVisit Microsoft Virtual Academy for free online training visit https://www.microsoftvirtualacademy.com

Visit Channel 9 to access a wide range of Microsoft training and event recordings https://channel9.msdn.com/

Head to the TechNet Eval Centre to download trials of the latest

Microsoft products http://Microsoft.com/en-us/evalcenter/

© 2015 Microsoft Corporation. All rights reserved.Microsoft, Windows and other product names are or may be registered

trademarks and/or trademarks in the U.S. and/or other countries.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY,

AS TO THE INFORMATION IN THIS PRESENTATION.