Site Recovery pricing

Automated replication to help protect your services

Azure Site Recovery can help you protect important services by coordinating the automated replication and recovery of protected instances at a secondary location.

Pricing details

Azure Site Recovery is billed based on the number of instances protected. Every instance that is protected with Azure Site Recovery is free for the first 31 days, as noted below.

Price for first 31 days Price after 31 days
Azure Site Recovery to customer-owned sites Free $-/month per instance protected
Azure Site Recovery to Azure Free $-/month per instance protected
Azure Site Recovery between Azure regions is charged at the same rate as Azure Site Recovery to Azure.

Azure Site Recovery is billed in units of the average daily number of instances you are protecting over a monthly period. For example, if you consistently protected 20 instances for the first half of the month and none for the second half of the month, the average daily number of protected instances would be 10 for that month.

Support and SLA

FAQs

  • Every instance that is protected with Azure Site Recovery is free for the first 31 days of protection. From the 32nd day onwards, protection for the instance is charged at the rates above.

  • Yes, it doesn’t matter how long you’ve been using Azure Site Recovery. Every protected instance incurs no Azure Site Recovery charges for the first 31 days. For example, if you have been protecting 10 instances for the last 6 months and you connect an 11th instance to Azure Site Recovery, there will be no Azure Site Recovery charges for the 11th instance for the first 31 days. The first 10 instances continue to incur Azure Site Recovery charges, as they have been protected for more than 31 days.

  • Yes, even though Azure Site Recovery is free during the first 31 days of a protected instance, you might incur charges for Azure Storage, storage transactions and data transfer. A recovered virtual machine might also incur Azure compute charges.

  • 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.

    • If a virtual machine disk replicates to a standard storage account, the Azure Storage charge is for the storage consumption. For example, if the source disk size is 1 TB, and 400 GB of storage is used, Site Recovery creates a 1 TB VHD in Azure, but the storage charged is 400 GB (plus the amount of storage space used for replication logs).
    • If a virtual machine disk replicates to a premium storage account, the Azure storage charge is for the provisioned storage size, rounded out for the nearest premium storage disk option. For example, if the source disk size is 50 GB, Site Recovery creates a 50 GB disk in Azure, and Azure maps this to the nearest premium storage disk (P10). Costs are calculated on P10, and not on the 50 GB disk size. Learn more. If you're using premium storage, a standard storage account for replication logging is also required, and the amount of standard storage space used for these logs is also billed.
    • No disks are created until a test failover or a failover. In the replication state, storage charges under the category of "Page blob and disk" as per the storage pricing calculator are incurred. These charges are based on the type of storage—premium or standard—and the data redundancy type, including LRS, GRS, RA-GRS, and more.
    • If the option to use managed disks on a failover is selected, charges for managed disks apply after a failover or test failover. Managed disks charges do not apply during replication. During replication, storage charges under the category of "Unmanaged disks and page blobs" are incurred. These charges are based on the storage type of premium/standard and the data redundancy type - LRS, GRS, RA-GRS etc.

      Example: For a VM replicating to premium storage with 128 GB OS disk and 500 GB data disk:

      1. During replication: Storage charges under the category of "Unmanaged disks and page blobs" for premium storage disk sizes P10 and P20 are incurred. The size of the disks being replicated (128 GB and 500 GB) are rounded off to the nearest unmanaged premium disk size of P10(128 GB) and P20(512 GB) for billing. A standard storage account for logging delta changes during replication is also used. Storage charges under the category of "Unmanaged disks and page blobs" based on the amount of standard storage used for these logs is also billed.
      2. During a Test failover or after failover to managed disks: Managed disk charges for premium managed disks of sizes P10 and P20 apply.

      Example: For a VM replicating to standard storage with 32 GB OS disk and 250 GB data disk:

      1. During replication: Storage charges under the category of "Unmanaged disks and page blobs" for standard storage are incurred.
      2. During a Test failover or after failover to managed disks: Managed disk charges for standard managed disks of sizes S4(32 GB) and S15(256 GB) apply. As you can see, the size of the disks (32 GB and 250 GB) have been rounded off to the nearest standard managed disk size of S4(32 GB) and S15(256 GB).
    • If the option to use managed disks on a failover is not selected, storage charges under the category of "Unmanaged Disks and Page blobs" as per the Storage pricing calculator are incurred after failover. These charges are based on the type of storage—premium or standard—and the data redundancy type, including LRS, GRS, RA-GRS, and more.
    • Storage transactions are charged during steady-state replication and for regular virtual machine operations after a failover or test failover. But these charges are negligible.

    Costs are also incurred during test failover, where the virtual machine, storage, egress, and storage transactions costs will be applied.

  • The Azure Hybrid Benefit helps you to get the most value from licences on-premises and in the cloud. It lets you use your Windows Server licences with Software Assurance for virtual machines at the base compute rate, resulting in up to 40 per cent savings or more across all Azure regions. Use your Hybrid Benefit while migrating your Windows servers to Azure. Learn more.

  • See Azure Site Recovery frequently asked questions.

    Licensing Microsoft Server products for disaster recovery

    It's important to note that when an instance protected by Azure Site Recovery is recovered at the recovery site, the software running inside the protected instance must be properly licensed as well. The end customer needs to license Microsoft server products as follows, depending on the recovery site selected.

    On-Premises* Service Provider Dedicated Hardware Service Provider Shared Hardware Azure
    Windows Server
    • Fully licensed servers, or
    • End Customer licenses, via Disaster Recovery Software Assurance benefit
    • Service Provider provides via Services Provider License Agreement (SPLA)
    • End customer licenses, via Disaster Recovery Software Assurance benefit (for example, dedicated outsourcing)
    • Service Provider provides via Services Provider License Agreement (SPLA)
    • Azure Site Recovery, now lets you leverage your Hybrid Benefit while migrating your Windows servers to Azure. Learn more.
    Other Microsoft Servers (SQL, Exchange, SharePoint, etc.)
    • Fully licensed servers, or
    • End Customer licenses, via Disaster Recovery Software Assurance benefit
    • Service Provider provides via Services Provider License Agreement (SPLA)
    • End customer licenses, via Disaster Recovery Software Assurance benefit (for example, dedicated outsourcing)
    • Service Provider provides via Services Provider License Agreement (SPLA)
    • The disaster recovery software assurance benefit applies to Microsoft server products protected with Azure Site Recovery. This change was made in the 2015 Product Use Rights (PUR).

    *On-premises can be used to describe both an end customer or service provider environment, as long as it is for their own usage and not resold.

  • The servers need to be fully licensed with Windows Server licences. If the customer has active Software Assurance coverage on their Windows Server at the primary site, they may deploy Windows Server at the secondary site through the Disaster Recovery Software Assurance benefit for non-production disaster recovery purposes only. Consult the Product Use Rights (PUR) to determine whether customer usage meets the Disaster Recovery Software Assurance benefit criteria.

  • These servers can be licensed with separate licences at the secondary site or through the Disaster Recovery Software Assurance benefit, if the customer qualifies for this benefit.

  • Windows Server should be licensed via your Services Provider Licence Agreement (SPLA).

  • Windows Server can be licensed via your SPLA agreement or via the end customer’s licence if they qualify for the Disaster Recovery Software Assurance benefit.

  • These server products should be licensed via your SPLA on the basis in which the servers are normally licensed in SPLA (Per Core, Per User and so on).

  • These servers can be licensed via your SPLA or via the end customer’s licence if they qualify for the Disaster Recovery Software Assurance benefit.

  • Azure Hybrid Benefit is applicable to all customers with active Software Assurance and can be activated in Azure regardless of how Azure is being procured (Enterprise Agreement, Cloud Solution Provider and others).

  • Licence Mobility and Azure Hybrid Benefit require Software Assurance and therefore do not apply to SPLA. The service provider should refer to their SPLA contracts about terms and conditions of the agreement.

  • The Disaster Recovery Software Assurance benefit applies to Microsoft server products protected with Azure Site Recovery. This change was made in the January 2015 Product Use Rights.

  • No, each of these Software Assurance benefits has limitations that make them inappropriate for licensing recovery to Azure. The License Mobility benefit requires customers to reassign their licences to Azure for a minimum of 90 days, which does not align with a temporary production recovery on Azure. In addition, License Mobility only provides for one running instance at a time, which does not provide for test recoveries where the production instance continues to run on premises while the test recovery instance runs on Azure. The Disaster Recovery benefit does cover both production and test recovery scenarios but is not eligible for instances run on shared (multi-tenant) hardware.

  • If a customer is using Azure Site Recovery to migrate Microsoft server products (for example, SQL Server) from a service provider to Azure, the customer would need to have their own Software Assurance and use Licence Mobility.

  • Yes, test recoveries are limited to brief periods of disaster recovery testing within one week every 90 days.

  • Azure Site Recovery replication for SQL Server is covered under the Software Assurance – Disaster Recovery benefit, for all Azure Site Recovery scenarios (on-premises to Azure disaster recovery, or cross-region Azure IaaS disaster recovery).

    Use of any other high availability technology for SQL Server, for example, failover clustering, or replication technology, such as SQL Always On Availability Groups, database mirroring and log shipping, is bound by the following SQL Server licensing guidelines – the first passive database instance (typically for local high availability) is covered by the Software Assurance licence of the primary database. Any additional passive database instances (for disaster recovery, say in a remote on-premises data centre or in any cloud) need additional SQL Server licences. If the primary SQL instance is on dedicated hardware, the first passive instance is covered by the Software Assurance licence on dedicated hardware, and not on shared hardware. If the primary SQL instance is on shared hardware, then the first passive instance is covered on shared hardware. Read the SQL Server Licensing guide for more information.

  • Azure is broadly certified to run SAP solutions on Azure – both current generation platform (NetWeaver) and next generation platform (HANA). The certifications that SAP issues are based on a combination of Business Application (SAP product), Guest OS and relational database management systems. Learn more. Additional details can be found in SAP Notes on the SAP Support Portal.

  • Oracle provides licence mobility for customers who want to run Oracle software on Microsoft Azure. See Licensing Oracle Software in the cloud computing environment. Oracle’s partnership with Microsoft enables customers to deploy Oracle software in Microsoft public and private clouds with the confidence of certification and support from Oracle.

  • Please refer to the licensing terms of your third-party application.

  • Azure does not support persistent MAC addresses, so software with MAC-based licence models can't be used for on-premises to Azure migration or disaster recovery.

Resources

Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Site Recovery

Review technical tutorials, videos and more resources

Added to estimate. Press 'v' to view on calculator View on calculator

Learn and build with $200 in credit, and keep going for free

Free account