Carlos Mayol is a Premier Field Engineer at Microsoft focused on Azure infrastructure services including Azure Site Recovery. Azure Site Recovery allows for replication, failover, and recovery of workloads between on-premises and Azure. It supports various scenarios including replication between on-premises Hyper-V and VMWare sites, as well as migration from on-premises to Azure. The presentation provides an overview of Azure Site Recovery capabilities and scenarios.

1. Azure Site Recovery
Carlos Mayol (carlosm@microsoft.com)
Premier Field Engineer - Microsoft

2. Carlos Mayol (MSFT since 2010, on IT since 1997)
• Actively working on Clustering ,Virtualization and Azure Infrastructure
Services at Microsoft
• Content contributor for Microsoft Press books, TechNet articles and
Webcast
• Speaker on System center and Azure User Groups
Premier Field Engineer focused on Proactive Services and Trainings for Microsoft products and solutions

3. • Azure Infrastructure as a Service
• Azure Storage hybrid integration
• Azure Site Recovery
 Part 1 Tech slides
 Part 2 Demos
 Part 3 FAQ / Q&A

5. What is Azure Site Recovery?
Cloud service that integrates into BCDR strategy
Orchestrates replication, failover, and recovery of
workloads and apps to a remote location
Automated VM protection
Remote health monitoring
Customizable recovery plans
No-impact test recovery
Reports and alerts

6. Azure Site Recovery

7. Azure Site Recovery - Scenarios
Between two on-premises VMM sites (HyperV or SAN replica)
Between two on-premises VMM sites and Microsoft Azure
Between an on-premises Hyper-V sites (Branch)
and Microsoft Azure
Between two on-premises VMWare or Physical sites
Between on-premises VMWare or Physical sites to
Microsoft Azure

8. Azure Site Recovery – Scenarios extra!
Migrate VMs between Azure regions
Migrate VMs from AWS
Migrate VMs from VMware to Hyper-V

9. Contoso Primary Location
(On-Premises/Service Provider)
Source:VMwarevSphereVMs
& Physical Servers
Heterogeneous Disaster Recovery
for VMware vSphere-based VMs & Physical Servers
Process
Server
Contoso Secondary Location
(On-Premises/Service Provider)
Target:VMwarevSphereVMs
Config
Server
Master
Target
InMage
Scout Data
Channel
Download
InMage
Scout
Microsoft Azure
Site Recovery
Download
InMage
Scout
ProcessServer – Used for Caching,
Compression & Encryption
Config Server – Used for Centralized
Management of InMage Scout
Master Target – Used as a repository&
for retention

10. Heterogeneous Disaster Recovery
*Failback to on-premises is always to VMware VMs, even if you failed over a physical server
Enhanced VMware/Physical to Azure

11. Hyper-V Replica Scenario Overview
11

12. Hyper-V Replica Scenario Overview (continued)
12
Hyper-V Replica allows organizations to implement affordable disaster
recovery
Virtual machines running in a primary site are replicated to a secondary
location (Replica site) usually across a WAN link
Hardware, storage, and workload-agnostic solution that implements
asynchronous replication
Failover requires manual intervention or Azure Site Recovery

13. Hyper-V Replica Considerations
13
No Microsoft Active Directory Domain Services
(AD DS) Required unless Failover Cluster is involved
Additional security configuring Trust Groups
Firewall rules should be configured for http or https
Mutual Authentication (Active Directory) or Certificates

14. Azure Site Recovery - Failover options
Test Failover
• Allow you to test on a cloned version of your VM
Planned Failover
• Allow you to switch your VM/application between locations
Unplanned Failover
• Allow you to restore your VMs/apps into the remote
location (data loss based on the replica RPO)

15. Azure Site Recovery - Planning
Run capacity planning tools
Review Networking – IP planning / set TCP failover
When VMM in place
• Review logical network
• Review Storage classification
Execute Test Failover

16. Failover TCP/IP
16
Primary VM IP
Addressing
IPV4 Address: 192.168.0.1
Subnet mask: 255.255.255.0
Default GW: 192.168.0.100
Preferred Domain Name System
(DNS): 192.168.0.254
Alternate DNS: 192.168.0.253
Replica VM IP
Addressing
IPV4 Address: 10.0.0.1
Subnet mask: 255.0.0.0
Default Gateway (GW):
10.0.0.100
Preferred DNS: 10.0.0.254
Alternate DNS: 10.0.0.253
Considerations
• Should be configured after
Replica virtual machine
creation
• Failback IP should be
configured on Primary virtual
machine as well
• ICs Required

17. Azure Site Recovery
VMM Sites

18. Azure Site Recovery
VMM Sites prerequisites
VMM 2012 R2 (Last UR is recommended) & runs on Windows Server 2012 R2
You have at least 2 VMM Cloud, that contains:
One or more VMM Host Groups (no shared hosts)
One or more Hyper-V hosts servers/clusters in each Host Group
One or more virtual machines on the source Hyper-V hosts
Your VMM Server should have access to the following set of URLs.
• *.hypervrecoverymanager.windowsazure.com
• *.accesscontrol.windows.net
• *.backup.windowsazure.com
• *.blob.core.windows.net
• *.store.core.windows.net
• http://www.msftncsi.com/ncsi.txt

20. Azure Site Recovery
Hyper-V to Azure prerequisites
Make sure your server runs Windows Server 2012 R2 (2012 RTM is not
supported)
Make sure you have installed the June 2014 Rollup
Your Hyper-V Server should have access to the following set of URLs.
• *.hypervrecoverymanager.windowsazure.com
• *.accesscontrol.windows.net
• *.backup.windowsazure.com
• *.blob.core.windows.net
• *.store.core.windows.net
• http://www.msftncsi.com/ncsi.txt

22. Q&A / FAQ
22
Can I control the bandwidth on my replication to Azure?
A: Yes, use the Azure backup tool installed with MASR or Set-OBMachineSetting
Can I protect VMs if Hyper-V is running on a client operating system?
A: No
Can I deploy Site Recovery with VMM if I only have one VMM server?
A: Yes
Can I replicate Hyper-V generation 2 virtual machines to Azure?
A: Yes
https://azure.microsoft.com/en-us/documentation/articles/site-recovery-faq/