Azure Site recovery

Help your business to keep doing business—even during major IT outages. Azure Site Recovery offers ease of deployment, cost effectiveness, and dependability. Deploy replication, failover, and recovery processes through Site Recovery to help keep your applications running during planned and unplanned outages.


Site Recovery is a native disaster recovery as a service (DRaaS), and Microsoft has been recognized as a leader in DRaaS based on completeness of vision and ability to execute by Gartner in the 2019 Magic Quadrant for Disaster Recovery as a Service.


Replication scenarios


  •  Replicate Azure VMs from one Azure region to another.
  • Replicate on-premises VMware VMs, Hyper-V VMs, physical servers (Windows and Linux), Azure Stack VMs to Azure.
  • Replicate AWS Windows instances to Azure.
  • Replicate on-premises VMware VMs, Hyper-V VMs managed by System Center VMM, and physical servers to a secondary site.



  • Simple to deploy and manage.
    Minimize recovery issues by sequencing the order of multi-tier applications running on multiple virtual machines. Ensure compliance by testing your disaster recovery plan without impacting production workloads or end users. And keep applications available during outages with automatic recovery from on-premises to Azure or Azure to another Azure region.

  • Reduce infrastructure costs.
    Reduce the cost of deploying, monitoring, patching, and maintaining on-premises disaster recovery infrastructure by eliminating the need for building or maintaining a costly secondary datacenter. Plus, you pay only for the compute resources you need to support your applications in Azure.

  • Minimize downtime with dependable recovery.
    Easily comply with industry regulations such as ISO 27001 by enabling Site Recovery between separate Azure regions. Scale coverage to as many business-critical applications as you need, backed by Azure’s service availability and support. Restore your most recent data quickly with Site Recovery.


When you use Site Recovery, you incur charges for the Site Recovery license, Azure storage, storage transactions, and outbound data transfer.

  • The Site Recovery license is per protected instance, where an instance is a virtual machine or a physical server.
  • Storage cost is incurred for the Site Recovery replica of storage in the target location. A snapshot taken on this replica storage is used to create a new target storage disk upon test failover or failover. Overall storage cost is hence, based on replica of storage and the number of disaster recovery drills conducted in a year.
  • Storage transactions are charged during steady-state replication and for regular virtual machine operations after a failover or test failover.
  • Outbound data transfer cost is also called as egress and is charged only when the traffic leaves an Azure region. Hence, these charges are applied when you replicate an Azure virtual machine from one region to another. Azure Site Recovery compresses the data before you transfer. Hence, egress is charged for the compressed replication data.
  • Recovery points created by Site Recovery are snapshots taken for the replica storage. These snapshots are charged based on the consumed capacity.
  • Costs are also incurred for the virtual machine compute capacity and is only applied at the time of test failover and failover. This cost is usually zero provided there’s no active disaster recovery drill or no actual disaster.