Best Practices amp Roadmap Gaurav Daga Principal Lead Program Manager Microsoft Corporation BRK2457 Nathan Muggli Principal Program Manager Microsoft Corporation Agenda Migration scenarios ID: 490795
Download Presentation The PPT/PDF document "Microsoft Azure Migration" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1Slide2
Microsoft Azure Migration Best Practices & Roadmap
Gaurav Daga Principal Lead Program ManagerMicrosoft Corporation
BRK2457
Nathan Muggli
Principal Program Manager
Microsoft CorporationSlide3
Agenda
Migration scenarios
Target: Microsoft Azure
Source:
Microsoft Azure
Target: Microsoft Azure
Source: AWS
Target: Microsoft Azure
Virtual or Physical
machine to Azure
AWS
VM to Azure
Azure to Azure
Azure
services
your migration scenario
migration
tools
this
session
Source: On-premiseSlide4
Virtual/Physical Machine to Azure Migration
AWS to Azure MigrationSlide5
Common Challenges
We hear from our customers
‘I am unable to deliver the services my business requires’
‘My
infrastructure is
extremely complex and difficult to manage’
‘I don’t have the capital budget required to keep my infrastructure up-to-date’Slide6
Availability on Demand
Solves IT
challenges
with the power of Microsoft Azure
Extend Your Datacenter
Achieve True Hybrid
Cloud
Transform Your Business
Harness
powerful cloud capabilities, turning IT into a
differentiator
A
unified platform across your datacenter and the cloud, making it easy to truly achieve a hybrid solution
Dynamically respond to the needs of your business with the elasticity of Azure and the convenience of a pay-as-you-go modelSlide7
Availability on Demand
Empower your business with cloud services from Microsoft Azure
Availability on
Demand
Long-Term Retention
Cloud Backup
Recovery
Analytics/Reporting
Cloud Bursting
Cloud Migration
DevTestSlide8
Migrate Workloads to Azure
Limit your
datacenter footprint
Reduce the burden on IT and lower costs for your on-premises infrastructure
Control where you run apps and store data for a true hybrid experience
A scalable and reliable platform for both Tier 1 and Tier 2 workloadsIncrease datacenter agility with on demand, near-limitless cloud scalabilitySlide9
Migrate Workloads to Azure
Key considerations
Reduce downtime of production workload during migration
Test applications in Azure before migration
Replicate data to Azure only once, for both migration and recoverySlide10
Azure Site Recovery
One migration solution for heterogeneous infrastructure
Orchestration and Replication
Microsoft Azure
Site Recovery
Primary Site
Hyper-V
Orchestration and Replication
Microsoft Azure
Site Recovery
Primary Site
vCenter
VMware
NEW
Orchestration and Replication
Microsoft Azure
Site Recovery
Primary Site
Physical, Azure, or AWS
NEW
Key features include:
Automated VM protection and replication
Remote health monitoring
Near zero RPO
No-impact
migration testing
Customizable
recovery
plans
Minimal RTO – few minutes to hours
Orchestrated
migration when
needed
Replicate to – and recover in – Azure
Heterogeneous physical and virtual support Slide11
Migrate VMware VMs and Physical
Machines
Microsoft Azure
Data Channel
Microsoft Azure
Site Recovery
Process Server –
Used for Caching, Compression & Encryption
Config Server –
Used for Centralized Management
Master Target –
Used as a repository & for retention
Source: VMware
VMs
& Physical
Machines
Process
Server
Customer 1
Process
Server
Customer 2
Source: VMware
VMs
& Physical
Machines
Mobility Service –
Captures all data writes from memory
Microsoft Azure
Customer 1
Customer 2
Target: Microsoft AzureSlide12
Migration with ASR
Availability on Demand
Microsoft Migration Accelerator functionality is now available in Azure Site Recovery
ASR incorporates feedback from the Migration Accelerator Preview
NEW
Automated deployment of infrastructure components
NEW
No
inbound ports needed on-premises
NEW
Enhanced
push installation of
Mobility Service
NEW
Consistent
, unified experience in Azure and ASR portal
Security, scale, and quality improvements with ASRSlide13
Demo
SharePoint Server on VMware to Azure
AWS Windows AMI to AzureSlide14
Summary
of
Actions
Customer selects migration region
CREATE VAULT1Define migration plan
CREATE RECOVERY PLAN
7
Register vCenter ServerREGISTER
4
Replicate disks to Azure
PROTECT VIRTUAL MACHINES
6
View step-by-step guidance
QUICK START
2
Infrastructure servers needed
SETUP SERVERS (CS, MT, PS)
3
Perform
migrationMIGRATE TO AZURE8Define protection policyCONFIGURE PROTECTION5Slide15
Requirements
VMware VMs and physical machines migration to Azure
Minimum configuration for on-premises Process
Server
2
CPU, 4 GB RAM,
and 300
GB disk for cache
storage
Sufficient bandwidth to replicate source servers to Azure
No inbound ports needed
Configuration Server and Master Target Servers
Azure subscription with sufficient resources
At least one standard A3 VM for Configuration Server
One or more standard A4 VMs for Master Target Servers
Standard D14 VM for Master Target Servers for source server with more than 15 disks
At least one retention drive per Master Target ServerSlide16
Migrate Hyper-V 2012 R2 VMs
Data Channel
Microsoft Azure
Site Recovery
Source:
Hyper-V VMs
Customer
Data Center
Microsoft Azure Recovery Services Agent
- Replicates
data to AzureSlide17
Summary
of
Actions
Customer selects migration regionCREATE VAULT
1Define migration planCREATE RECOVERY PLAN
7
Replicate disks to Azure
PROTECT VIRTUAL MACHINES
6
View step-by-step guidance
QUICK START
2
Perform
migration
MIGRATE TO AZURE
8
Define protection policy
CONFIGURE PROTECTION
5
3CREATE SITEGroup of Hyper-V hosts4REGISTERRegister Hyper-V ServerSlide18
ASR Pricing
Free protection for
any
server for the first 31 days – for both migration and recovery
No additional cost to migrate servers to Azure when migration is completed within the first 31 days – only pay for resources that you consume in Azure
Standard ASR pricing applies after 31 days Slide19
Azure to Azure MigrationSlide20
Internet users
■
500,000,000+
■
100,000,000 – 499,999,999
■
50,000,000 – 99,999,999
■ 25,000,000 – 49,999,999■ 5,000,000 – 24,999,999■ 100,000 – 4,999,999
■ 50,000 – 999,999
■ 0 – 49,999
*Operated by 21Vianet
1 million+ servers
•
100+ Datacenters in over 40 countries
Azure
Regions
India
Central
TBD
India
South
TBD
India
West
TBD
Brazil South
Sao Paulo
China North*
Beijing
China South*
Shanghai
Australia East
New South Wales
Australia
SouthEast
Victoria
Japan West
Osaka
Japan East
Saitama
New Regions launched in 2014Slide21
Azure to Azure
What? Why?
Azure to Azure migration is an emerging scenario with two main sub-scenarios:
Subscription
migration
Region to Region migrationCustomers want to run their existing Azure services/applications in a new region for performance, cost, or data residency purposes. What we hear from customers:
lessons from Japan geo launchMigration vs high availability vs load balancingMigration implies a goal of running services in the migration Target long term while Source is decommed eventuallyHighly Available and Load Balanced native Cloud applications have their own architecture guidance for running a global application across geographies for a global customer base and not considered a migration scenario even though both involve the movement of data across regionCommon gotchas and considerations across all servicesEndpoints (
ie URLs), Storage account keys, Timezone, DNS
Target: Microsoft Azure
Source:
Microsoft AzureSlide22
Azure
to Azure
Workload best practices: Storage
Option1: Use
AZCOPY
tool (Blob, Table, File data) to copy from Source to Target
Option2: Copy Source to an Intermediary (i.e on-premises server) then to TargetOption3: For Linux or Python users, use Option2+AzureSDK for Python or Script Center
Blob
Table
Source:
Microsoft Azure
Target:
Microsoft Azure
Blob
Table
Secondary
(geo-redundant)
Primary
Target & Source (optional): On premise Server
File
MyStorageAccount2
File
MyStorageAccountSlide23
Azure to Azure
Workload best practices: Virtual Machine(s)
VM
Option1: Don’t migrate. Delete and recreate VMs in new region.
Option2:
NEW
Use ASR for
online
VM
migration
Option3: Use
Azure
Datacenter Migration Solution
(
ADCMS
)
tool for
offline migration Option4: Copy Source to an Intermediary (ie on-premise server) then to Target
Source:
Microsoft Azure
Target:
Microsoft Azure
Target & Source (optional): On premise Server
VNET
Blob
Table
VM
VNET
Blob
Table
MyVM
MyVM2
File
FileSlide24
Azure Data Center Migration Solution
Free, open source tool for VM migration
Supported migration services
Affinity groups, Networks, Cloud services, Storage accounts, Virtual machines (VMs)
Supported migration scenarios…
From one subscription to another subscription in either the same region or different regionsIn the same subscription with the same region or different regionsADCMS produces a JSON-based template of your subscription configuration metadata which can be edited offline before importLimitationsThe solution creates all storage accounts of the source subscription but excludes the VM-independent blobs. You must copy these blobs manually, if required.
Migration occurs offline so the source VMs must be powered offWeb roles and Worker roles Cloud services are not migratedSlide25
Demo
Online
Azure to Azure VM migration using
ASR
Slide26
Azure to Azure
Workload best practices: Born in cloud native multi-tier Application
Source:
Microsoft Azure
Target: Microsoft Azure
Option1:
DIY experience through individual service migrationOption2: Contact MCS or a System Integrator to plan and execute the migration
VM
VNET
Blob
Table
Worker role(s)
Web role(s)
Planning phase (piloting)
Enumerate endpoints
(
ie
Search keywords within
data)
Establish
maintenance window
Practice copying data and measure performance and time
Prepare (dev work)
Rebuild
application with modified endpoints and
deploy
in new region. Don’t forget to change Management URL endpoint as well to point to new region
Migrate (App Offline)
Old
application stopped and taken offline.
Copy data from to new destination using data migration tools (
Blob,Table,DB
)
Switchover
VIP swap, DNS
CName
update.
Validate
. Compare
source data and copied
data.
Rollback
if needed
SQL DB(s)Slide27
Azure
Migration
Roadmap, Futures, and North Star
Regions
Azure is in 19
regions today with more on the way. India private preview program for 3 new regions expected to open this yearGuidanceBest Practice documentation for Azure to Azure migration including born-in-cloud native multi-tier applications
Source
Availability
Supported Guest
OS
Types
Hyper-V 2012 R2
Available All Guest
OS types supported by AzureHyper-V 2008 R2 SP1 and 2012
Available in PreviewWindows and LinuxVMware vCenter Server 5.1/5.5, ESXi 5.1/5.5, Physical
Machines, Azure VMsAvailable in PreviewWindows and LinuxAmazon Web Services (Windows AMIs)Available in PreviewWindows Server 2008 R2 SP1+ Amazon Web Services (Linux AMIs)RoadmapTBD
ToolingASR preview (2015): more Sources and guest OS types.Consistent experience
(Roadmap): On-premise to Azure migration has a lot of overlap with Azure to Azure. Consider one solution/approach for both which includes all workloads. Migration-as-a-Service (North Star): migration is just a service you just click a button in the UI without managing the migration serviceRemove pain points for migration in Azure (North Star): investigate Azure platform improvements such as renaming storage accounts so applications don’t need to change endpointsSource: AWSSlide28
Resources
Blog:
Preview of protect VMware VMs or physical servers to Azure
Preview signup:
Protect VMware VMs or physical servers to Azure
Documentation:
Protection between on-premises VMware VMs or physical servers and Azure
Documentation:
Protection between on-premises Hyper-V VMs and Azure
Azure
Script
Center:
http
://azure.microsoft.com/en-us/documentation/scripts
/
ADCMS:
https
://
github.com/persistentsystems/adcms
Slide29
Azure Site Recovery Breakout Sessions #MSIgnite
Disaster Recovery for Azure appsWednesday 6 May 9 am: Best Practices for Disaster Recovery for Azure Applications
Disaster Recovery for on-premises data centers
Wednesday 6 May 1:30 pm:
Azure Site Recovery: Microsoft Azure As a Destination for Disaster Recovery
Thursday 7 May 3:15 pm: Protecting Your VMware and Physical Servers by Using Microsoft Azure Site Recovery Friday 8 May 9 am: Managing Storage with Microsoft System Center Virtual Machine Manager: A Deep Dive Friday 8 May 12:30 pm: Best Practices for Deploying Disaster Recovery Services with Microsoft Azure Site RecoverySlide30
Ignite Azure
Challenge Sweepstakes
Attend Azure sessions and activities, track your progress online, win raffle tickets for great prizes!
Aka.ms/
MyAzureChallenge
Enter this session code online
: BRK2457
NO PURCHASE NECESSARY. Open only to event attendees. Winners must be present to win. Game ends May 9
th
, 2015. For Official Rules, see The Cloud and Enterprise Lounge or myignite.com/challengeSlide31
Learn more
with FREE
IT Pro Resources
Free technical training resources:
On-demand online training:
http://aka.ms/learnhybrid
Expand your
Hybrid I
nfrastructure
Knowledge
Free ebooks:
Rethinking Enterprise Storage: A Hybrid Cloud Model:
http://
aka.ms/hybrid-storage-ebook
Microsoft Azure Essentials: Fundamentals of Azure:
http://aka.ms/azure-fundamentals-ebook
Join the IT Pro community:
Twitter
@MS_ITProSlide32
Visit
Myignite
at
http://myignite.microsoft.com or download and use the Ignite
Mobile App with the QR code above.
Please evaluate this session
Your feedback is important to us!Slide33