2. Danny Newport / Stephane Budo
Protecting Your VMware VM’s to Azure Using Microsoft Azure Site Recovery
Danny Newport / Stephane Budo
INF334B

3. Enterprise Mobility Suite
Azure Site Recovery
Operations Management Suite
Azure Backup

4. Agenda
PowerPoint
Demo
More PowerPoint

5. DR; how do YOU do it?

6. Options for DR Don’t bother – it’s all just too hard (and expensive)
Backups and offsite tape storage
Redundant secondary DC
Active / Active across DC’s with additional capacity
Cloud based, capacity on demand, automated, PAYG

7. Common DR strategies Ostrich DR Check box DR Iron Mountain DR
What disaster, I don’t see no disaster
That sort of thing doesn’t happen here…
Check box DR
Phew! The CIO is off my back
God I hope this works! <Insert prayer here>
Plan B = seek.com.au
Iron Mountain DR
We have off-site tapes; I reckon I could get everything stood up in a week or 2 or 3 or 4…

8. What you’re really planning for
Patch Tuesday gone wrong
Network outage
Misconfiguration
Power outages
Terrorism
About 60% of all BC / DR events are caused by human error

9. BC / DR quick facts Loss of Data & Service Cost of Disruption
4/26/2017
Loss of Data & Service
Organizations experience 4+ disruptions each year
Recovery times range from 1hr to 9hrs
Cost of Disruption
Average cost of the disruption is $1.5M/hour
4 in 10 businesses do not reopen after a major disaster
Brand & Equity
Loss of reputation is often irreparable
Customer trust and brand severely impacted
Compliance
Clients want to partner with orgs that have BCDR in place
Protection & recovery is a key tenet for compliance
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Business Continuity Challenges Impact of data and application growth
Roadblock
Complexity of protecting data and applications
Too much data—often with insufficient protection
Long data-retention requirements
Time-intensive media management
Untested disaster recovery and decreasing recovery confidence
Higher costs as data size and number of virtual machines increase

11. Business Continuity Solutions Bypassing the obstacles
Roadblock
Roadblock
Automate, automate, automate
Protecting data and applications is complex
Too much data—often with insufficient protection
Integrate solutions which scale with data and VMs
Increase breadth and depth of protection
Long data retention requirements
Eliminate media management
Time-intensive media management
Implement testable solutions
Untested DR and decreasing recovery confidence
Costs scale with data size and number of VMs
Achieve cost and operations stability

12. What is Azure Site Recovery (ASR)?
The Azure Site Recovery service contributes to a robust business continuity and disaster recovery (BCDR) solution that protects your on-premises physical servers and virtual machines by orchestrating and automating replication and failover to Azure, or to a secondary on-premises datacentre.

13. Features Cost effective
Replicate to Azure Blob Storage and only pay for compute during test failovers or an actual DR recovery event
Workload-aware replication for heterogeneous environments
Seamless protection for VMware, Hyper-V, and physical machines
Discovery of VMware vSphere ESXi virtual machines
Support for VMware vCenter Server
Protection for bare-metal and hosted server workloads
Discovery based on IP address
Continuous Data Protection (CDP)
Near-zero Recovery Point Objective (RPO) and Recovery Time Objective (RTO) of minutes

14. Features Support for public Internet and private networks
Replicate data with or without Azure ExpressRoute
Workload-aware recovery with Recovery Plans
Optimize RTO with Azure Automation
Failback to on-premises VMware infrastructure
Failback to physical server in the roadmap
Health monitoring
Event reporting and notifications

15. Key definitions RTO RPO
How long can I afford to have my systems offline for
RPO
How much data can I afford to lose in the process

16. 4/26/2017
Protect your applications On-premises to Microsoft Azure protection with Azure Site Recovery
Orchestration and replication
Microsoft Azure Site Recovery
Enterprise & HSP primary site
Windows Server
Orchestration and replication
Microsoft Azure Site Recovery
SMB & branch primary site
Windows Server
Orchestration and replication
Microsoft Azure Site Recovery
Enterprise, SMB & HSP primary site
VMware/Physical
vCenter Server
Hyper-V
Use Azure as your disaster recovery site
Automated VM protection and replication
Remote health monitoring
Customizable recovery plans
No-impact recovery plan testing
Orchestrated recovery of tiered applications
New: Replication into Azure for SMBs and remote branch offices without System Center
Key features include:
Support for heterogeneous environments
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. 4/26/2017
Protect your applications On-premises to on-premises protection with Azure Site Recovery
Microsoft Azure Site Recovery
Communication channel
Replication channel: host-based or SAN-based
Primary site
Windows Server
Recovery site
Microsoft Azure Site Recovery
Download ASR components
Replication and orchestration channel: guest-based
Primary site
VMware/Physical
Recovery site
VMware
Agent
Automated VM protection and replication
Remote health monitoring
Customizable recovery plans
Integration with available investments
No-impact recovery plan testing
Orchestrated recovery of tiered applications
Key features include:
Support for heterogeneous environments
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. Deployment Architecture
4/26/2017
Deployment Architecture
Customer 1
Process Server
Microsoft Azure Site Recovery
Source: VMware VMs & Physical Machines
Customer 1
Customer 2
Target: Microsoft Azure
Data Channel
Process Server
Source: VMware VMs & Physical Machines
Microsoft Azure
Microsoft Azure
Customer 2
Mobility Service – Captures all data writes from memory
Process Server – Used for Caching, Compression & Encryption
Master Target – Used as a repository & for retention
Config Server – Used for Centralized Management
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. 4/26/2017
Prerequisites Infrastructure requirements when enabling protection for VMware and physical machines
On-premises
Deployed in customer’s Azure subscription
Windows Server 2012 R2 physical or virtual machine
Same network as source machines
VMware vSphere CLI 5.5 for automatic discovery of VMware vSphere ESXi VMs
Sufficient resources in customer’s subscription
Deploy the following in the same region
Azure virtual network
Geo-redundant Azure Storage account
Azure Site Recovery vault
Standard A3 Configuration Server
Standard A4, D14 or DS4 Master Target Servers
Process Server – Used for Caching, Compression & Encryption
Master Target – Used as a repository & for retention
Config Server – Used for Centralized Management
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. Target: Microsoft Azure
4/26/2017
Azure Traffic Manager
SQL
Web
SQL
Web
Primary
Secondary
Target: Microsoft Azure
Azure Traffic Manager
Microsoft Azure
Microsoft Azure
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. Demo
Stephane Budo – Vigilant

22. Summary of Actions 1 2 3 4 5 6 7 8 Customer selects recovery region
4/26/2017
Summary of Actions
Customer selects recovery region
CREATE VAULT 1
View step-by-step guidance
QUICK START 2
Infrastructure servers needed
SETUP SERVERS (CS, MT, PS) 3
Register vCenter Server
REGISTER 4
Define protection policy
CONFIGURE PROTECTION 5
Replicate disks to Azure
PROTECT VIRTUAL MACHINES 6
Define recovery plan
CREATE RECOVERY PLAN 7
Perform failover
FAILOVER TO AZURE 8
© 2012 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.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. ASR requirements (VMware to Azure DR)
Network connectivity from Source Site to Azure
Process Server to Configuration Server (https outbound )
Process Server to Master Target (TCP 9443 and 9080 – outbound)
Mobility Service to Configuration Server (https 443 – outbound)
Network bandwidth to Azure
Use Capacity Planner for infrastructure requirements
Enable protection in batches & can leverage ExpressRoute
To control network replication traffic you can implement QoS policy for Process Server
Source Infrastructure
VM and VMware tools inside the VM, should be running.
WMI and File and Print Sharing are enabled in firewall – More Info
Supported vSphere CLI on Process Server – More Info
Account for vCenter discovery should have necessary permissions – More Info

24. Azure Prerequisites Subscription with sufficient resources
Following in the same region
Azure virtual network
Geo Redundant Storage account
Azure Site Recovery vault
Standard A3 Configuration Server
Standard A4, D14 or DS4 Master Target Servers
Source machines comply with Azure VM requirements
Disk count – maximum of 31 disks per protected source machine
Disk sizes – individual disk capacity not more than 1023 GB
Clustering – clustered servers not supported
Boot – UEFI / EFI boot not supported
Volumes – BitLocker encrypted volumes not supported

25. Windows Source Machine Prerequisites
Operating systems (64-bit)
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2 with Service Pack 1
Storage
No dynamic disk support
Single or multiple NICs
All NICs on protected Azure VMs can be assigned to Azure VNETs

26. Linux Source Machine Prerequisites
Operating systems (64-bit)
CentOS 6.4 / 6.5 / 6.6
Oracle Linux 6.4 / 6.5
SUSE Linux Enterprise Server (SLES) 11 Service Pack 3
Storage
File systems - EXT3 / EXT4 / ReiserFS / XFS
Multipath software – Device Mapper-Multipath
Volume manager – LVM2
Physical servers with HP CCISS controller storage not supported
Single NIC
For multi-NIC source machines, only one NIC on protected Azure VM can be assigned to Azure VNET

27. Common Source Machine Prerequisites
Source machines turned on
ASR-guest based replication requires running source machines
Remote Desktop or Secure Shell enabled
For connectivity to recovered Azure VMs

28. Capacity Planning

29. Azure Capacity Planning tool
Key Inputs
No. of VMs and Size (Overall IR)
Average Churn rate (Daily delta replication)
Peak Churn
# VMs/batch
How long we can wait for IR (IR Window)
Key Outputs
Initial network bandwidth (For IR)
Average network bandwidth (For delta replication)
Peaks – Tradeoffs
Configurations and Units for Process Server, Master Target and Configuration Servers

30. Azure Capacity Planning - Compute
Configuration Server
Single Standard A3 VM manages up to ~750 protected source machine volumes
Assuming average three volumes per source machine, single Configuration Server scales to ~250 protected machines
Master Target Server
Two Master Target Server VM sizes
Standard A4 -16 data disks
Standard D data disks
One disk on every Master Target Server reserved for retention
Maximum protected disks per standard A4 =15 and per standard D14 = 31
Better scale out economics with multiple standard A4 Master Target Servers
Recommend using standard D14 only if single source machine has greater than 15 total disks
Windows sources need Windows Master Target Servers, Linux sources need Linux Master Target Servers

31. Capacity Planning – Component Servers
Deployed Azure instances
Cores
Memory
Max disks
Disk size
Configuration server
Standard A3 4
7 GB 8
1023 GB
Master target server
Standard A4
14 GB 16
Standard D14
112 GB 32
Standard DS4
28 GB

32. Azure Capacity Planning - Storage
Storage accounts provisioning
Single Master Target Server can span multiple storage accounts
One disk is required for its operating system and at least one for retention disk/s
One or more for replicated data disks
ASR-guest based replication has a ~2.5 IOPS multiplier on the Azure subscription
For every source I/O, two I/Os issued on replicated data disk and ~0.5 I/O issued on retention disk
Every standard Azure storage account supports maximum IOPS
Best practice to provision new storage account for every source machine IOPS

33. Capacity Planning – Process Server

34. Fail- back to VMware on-prem
Reverse the process
Process server in Azure
Master Target server on prem
Need to use vContinuum (Inmage component) tools to fail back
Step by step here
BUT; why would you…

35. Migration to Azure with ASR

36. Migration to Azure with ASR
Microsoft Migration Accelerator functionality now available in ASR
All source types supported in ASR
VMware vSphere ESXi VMs
Hyper-V VMs
Physical machines
Amazon Web Services VMs
Azure VMs cross-region
Feedback incorporated from Migration Accelerator Preview
Automated deployment of infrastructure components
No inbound ports needed on-premises
Enhanced push installation of mobility service to source machines
Consistent, unified experience in Azure with ASR portal
Security, scale, and quality improvements

37. ASR Resources

38. ASR Resources Blog Pricing Guide Service Updates Documentation Center
VMware to Azure - step by step
User Voice

39. Questions
Danny Newport
Stephane Budo

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

41. Continue your Ignite learning path
Microsoft Ignite 2015
4/26/2017 5:10 AM
Continue your Ignite learning path
Visit Microsoft Virtual Academy for free online training visit
Visit Channel 9 to access a wide range of Microsoft training and event recordings
Head to the TechNet Eval Centre to download trials of the latest Microsoft products
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.