CHALLENGES OF THE IT DEPARTMENTS Designing a DR solution is a complex task and many IT department do not have the required

resources.

High cost for implementing a DR solution.

Usually hardware resources in the DR site are not utilized appropriately.

Testing a Disaster Recovery is a very complex and time consuming task, that is jeopardizingproduction workloads.

Growing amount of data and lack of storage and compute resources.

RPO & RTO times can not be met with the current solutions in place

Lack of automation in the current DR solution.

Designing a DR solution is a complex task and many IT department do not have the requiredresources.

High cost for implementing a DR solution.

Usually hardware resources in the DR site are not utilized appropriately.

Testing a Disaster Recovery is a very complex and time consuming task, that is jeopardizingproduction workloads.

Growing amount of data and lack of storage and compute resources.

RPO & RTO times can not be met with the current solutions in place

Lack of automation in the current DR solution.

WHAT IS AZURE SITE RECOVERYAzure Site Recovery is a new service offered by Microsoft to automate and orchestrate thereplication, failover and recovery processes.

Azure Site RecoveryOn-Prem to On-Prem Scenario

Extensible Data Channel(Hyper-V Replica, SQL

Always-ON)

AZURE SITE RECOVERY USAGE SCENARIOSOn-premise to On-premise

On-premise to Hoster

√ Physical Servers√ Hyper-V hosts√ VMWare hosts

√ Physical Servers√ Hyper-V hosts√ VMWare hosts

On-premise to Azure

√ Physical Servers√ Hyper-V hosts√ VMWare hosts

X Physical Servers ← Will be supported in the next release of ASR√ Hyper-V hostsX VMWare hosts ← Will be supported in the next release of ASR

Azure Site Recovery

Supported Replication Channels:√ SQL Availability Group√ Hyper-V Replica√ SAN Replica (currently available for on-premise to on-

premise). Soon to be available on-premise to Azure.√ SAN Replica - EMC, NetApp, HP 3PAR√ SAN Replica – More partners next year

Hyper-V Replica

SQL Availability Group

SAN Replica

Use Cases & benefits of using Azure as a DR site:

One click Application Recovery

Test failover without impacting Production

Performing applications tests with production data without impacting Production

Disaster Avoidance

Failover during real disaster

Failback to on-premises

Use ASR for migration of VMs to Azure

Zero RPO

Low TCO compared to building an on-prem DR solution

Use Cases & benefits of using Azure as a DR site:

One click Application Recovery

Test failover without impacting Production

Performing applications tests with production data without impacting Production

Disaster Avoidance

Failover during real disaster

Failback to on-premises

Use ASR for migration of VMs to Azure

Zero RPO

Low TCO compared to building an on-prem DR solution

Steps required to setup ASR:

1) Create an Azure subscription

2) Create recovery vault and specify region tokeep the data

3) download Provider + registration file

4) Deploy Provider on VMM server and agentson all Hyper-V hosts

5) VMM pushes metadata to Azure SiteRecovery over HTTPS (only outbound)

6) Create VMM clouds and add VMs

7) Create storage accounts in Azure

8) Configure protection of the clouds in ASR

9) ASR monitors health continuously

10)Map networks from on-premise to Azure

System CenterVirtual MachineManager

AD

SQL

LOB

Steps required to setup ASR:

1) Create an Azure subscription

2) Create recovery vault and specify region tokeep the data

3) download Provider + registration file

4) Deploy Provider on VMM server and agentson all Hyper-V hosts

5) VMM pushes metadata to Azure SiteRecovery over HTTPS (only outbound)

6) Create VMM clouds and add VMs

7) Create storage accounts in Azure

8) Configure protection of the clouds in ASR

9) ASR monitors health continuously

10)Map networks from on-premise to Azure

System CenterVirtual MachineManager

AD

SQL

LOB

Azure Site Recovery

VMM 2012 SP1 or R2 with latest cumulative update

Hyper-V hosts with Windows Server 2012 or 2012 R2 with latest updates

Provider should be installed on the VMM server

Agents should be installed on the Hyper-V hosts when replicating to Azure

There should be internet connectivity from the VMM server (NAT & Proxy are supported)

Proper bandwidth calculation. Calculator is available.

The storage (CSV,SMB,local) where the on-prem VMs are located must be allowed inReplication Broker settings for replication

VMM 2012 SP1 or R2 with latest cumulative update

Hyper-V hosts with Windows Server 2012 or 2012 R2 with latest updates

Provider should be installed on the VMM server

Agents should be installed on the Hyper-V hosts when replicating to Azure

There should be internet connectivity from the VMM server (NAT & Proxy are supported)

Proper bandwidth calculation. Calculator is available.

The storage (CSV,SMB,local) where the on-prem VMs are located must be allowed inReplication Broker settings for replication

X After VM is added for replication newly added drives will not be replicated.

X There is no option to exclude virtual disks for replication.

X After VM is added to replication hardware changes on the VM will not be replicated.

X VMs are replicated to one Azure datacenter and are recovered in the same datacenter.

X ASR supports a maximum size of the OS disk of 127 GB when replicating to Azure

X Gen 2 VMs are currently not supported when replicating to Azure.

X VMWare VMs are currently not supported for replication to Azure.

X Windows Server Failover Clusters are not supported in Azure.

X Currently it is not possible to replicate physical servers to Azure.

X Offline replication to Azure is not supported.

X Multiple source clouds to a single target cloud is not supported

X After failover, endpoints need to be configured manually

X SAN replication is not yet supported when replicating to Azure

X After VM is added for replication newly added drives will not be replicated.

X There is no option to exclude virtual disks for replication.

X After VM is added to replication hardware changes on the VM will not be replicated.

X VMs are replicated to one Azure datacenter and are recovered in the same datacenter.

X ASR supports a maximum size of the OS disk of 127 GB when replicating to Azure

X Gen 2 VMs are currently not supported when replicating to Azure.

X VMWare VMs are currently not supported for replication to Azure.

X Windows Server Failover Clusters are not supported in Azure.

X Currently it is not possible to replicate physical servers to Azure.

X Offline replication to Azure is not supported.

X Multiple source clouds to a single target cloud is not supported

X After failover, endpoints need to be configured manually

X SAN replication is not yet supported when replicating to Azure

DocumentationTutorialPlanning guideDeployment guide

Team Blogs:ASR:http://blogs.technet.com/b/scvmm/archive/tags/windows+azure+hyper_2d00_v+recovery+manager/default.aspxHVR: http://blogs.technet.com/b/virtualization/archive/tags/hvr/

Other blogs from MSFTIn the Cloud – Brad Anderson’s blog postScott Guthrie’s blogWindows Server blog with pointers to casestudies

DocumentationTutorialPlanning guideDeployment guide

Team Blogs:ASR:http://blogs.technet.com/b/scvmm/archive/tags/windows+azure+hyper_2d00_v+recovery+manager/default.aspxHVR: http://blogs.technet.com/b/virtualization/archive/tags/hvr/

Other blogs from MSFTIn the Cloud – Brad Anderson’s blog postScott Guthrie’s blogWindows Server blog with pointers to casestudies

Thank you for your attention!

Svetoslav SpasovBusiness Unit Manager – Cloud, Infrastructure & ApplicationsM: + 359 884 10 69 60F: + 359 2 489 5883E-mail: Svetoslav.spasov@bulpros.comwww.bulpros.comSofia 1766, BULGARIAMladost 4, Business Park Sofia, Build. 4, fl. 5