You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/site-recovery/site-recovery-cost.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ ms.author: ankitadutta
8
8
author: ankitaduttaMSFT
9
9
---
10
10
11
-
# Azure Site Recovery for Managed Disks and associated costs
11
+
# Azure to Azure for managed disks and associated costs
12
12
13
-
Azure Site Recovery (ASR) is a robust disaster recovery solution offering seamless replication and failover capabilities for virtual and physical machines. It is important to understand the cost components associated with using Site Recovery to manage expenses effectively. Following is a detailed breakdown of the charges you may incur when using this service.
13
+
Azure to Azure (A2A) disaster recovery in Site Recovery is a robust disaster recovery solution offering seamless replication and failover capabilities for virtual and physical machines. It is important to understand the cost components associated with using Site Recovery to manage expenses effectively. Following is a detailed breakdown of the charges you may incur when using this service.
14
14
15
15
16
16
## Protected Instance License fee
@@ -22,15 +22,15 @@ The Protected Instance License fee is a fundamental charge for using Azure Site
22
22
23
23
Storage cost is a significant part of the overall expense when using Azure Site Recovery. This cost includes:
24
24
25
-
-**Replica Storage**: The replica storage in the target location mirrors source storage. This storage is used during replication, and its size and type depend on the source storage configuration. Applicable for A2A, V2A, and H2A.
25
+
-**Replica Storage**: The replica storage in the target location mirrors source storage. This storage is used during replication, and its size and type depend on the source storage configuration. Applicable only for A2A.
26
26
-**Cache Storage Account Cost**:
27
-
-**Azure Virtual Machines**: The cache storage account is in the source region. High churn is priced at Premium Block Blob pricing, and Normal Churn is charged at Gpv2 or Gpv1 pricing. There are minimal egress costs only in A2A for Delta Replication.
28
-
-**VMware/Physical Machines/Hyper-V Machines**: The cache storage account is in the target region, charged at Gpv2 or Gpv1 pricing as per the customer’s selection.
27
+
-**Azure Virtual Machines**: The cache storage account is in the source region. When a user selects *High Churn* the cache storage account uses Premium Block Blob. For *Normal Churn* it uses a General Purpose Storage Account. The charges depend on the type of storage account used. There are minimal egress costs only in A2A for Delta Replication.
28
+
-**VMware/Physical Machines/Hyper-V Machines**: The cache storage account is in the target region, charged at Gpv2 or Gpv1 pricing as per the user's selection.
29
29
30
30
31
31
## Storage Transactional cost
32
32
33
-
Storage transactions incur charges during the replication process and regular virtual machine operations after a failover or test failover. These costs are associated with the read and write operations performed on the cache storage account. The higher the number of disks attached to a VM, the higher the transactional costs.
33
+
Storage transactions incur charges during the replication process and regular virtual machine operations after a failover or test failover. These costs are associated with the read and write operations performed on the cache storage account. During initial replication or resync, attaching more disks to a VM increases transactional costs. After that, transactional costs will depend on the churn on the source disks for delta replication.
34
34
35
35
36
36
## Network Egress cost
@@ -42,10 +42,10 @@ Network egress costs, also known as outbound data transfer charges, occur when r
42
42
43
43
This cost includes:
44
44
45
-
-**Source (Applicable for A2A)**:
45
+
-**Source**:
46
46
- For Pv1 disks, incremental snapshots are charged.
47
47
- For Pv2 disks, one full snapshot followed by incremental snapshots is charged. A total of 12 snapshots are retained.
48
-
-**Target (Applicable for A2A, V2A, and H2A)**:
48
+
-**Target**:
49
49
- Snapshot costs are associated with the recovery points created by Azure Site Recovery. These snapshots capture the replica storage at a point in time and are charged based on the consumed capacity. Pricing details align with Page Blob Snapshots. [Learn more](https://azure.microsoft.com/pricing/details/storage/page-blobs/#:~:text=Note%3A%20Snapshots%20are%20charged,at%20%240.12%20%2FGB%20per%20month.?msockid=3816c7206e2268e7035dd3316f7069f4).
50
50
51
51
@@ -54,19 +54,19 @@ This cost includes:
54
54
This cost is applicable only during the initial replication. The duration for replicating 1 TB of data can be approximately assumed to be 6 hours. For example, if your data is 12 TB, the initial replication takes about 12 hours. The temporary source disk size and SKU type would be the same as the source data disk SKU and would be charged for the time it takes for the initial replication to complete.
55
55
56
56
57
-
## Optional cost
57
+
## Optional costs
58
58
59
-
### Capacity Reservation
59
+
### Capacity Reservation cost
60
60
61
-
Customers are advised to have capacity reservations in the target region. After deployment, capacity is reserved for your use and is always available within the scope of applicable service-level agreements (SLAs). This is not an Azure Site Recovery cost but an auxiliary cost for better infrastructure availability. After creating the capacity reservation, you can use the resources immediately. Capacity is reserved until the user deletes the reservation. [Learn more](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview#pricing-and-billing).
61
+
Site Recovery doesn't reserve any capacity on the target. If users need a higher probability of capacity for failover in the target region, they can use Capacity Reservation, which incurs additional costs. After deployment, capacity is reserved for your use and is always available within the scope of applicable service-level agreements (SLAs). This is not an Azure Site Recovery cost but an auxiliary cost for better infrastructure availability. After creating the capacity reservation, you can use the resources immediately. Capacity is reserved until the user deletes the reservation. [Learn more](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview#pricing-and-billing).
62
62
63
63
64
64
## Conclusion
65
65
66
66
Understanding the various cost components of Azure Site Recovery is essential for effective budgeting and cost management. Each of these charges contributes to the overall expense of maintaining a reliable disaster recovery solution. By carefully planning and monitoring the frequency of disaster recovery drills, the type of storage used, and the regions involved, you can optimize the costs associated with Azure Site Recovery.
67
67
68
68
> [!NOTE]
69
-
> -**Disaster Recovery Drills**: Each disaster recovery drill, such as test failovers, involves creating a snapshot of the replica storage. These snapshots are stored as new target storage disks, contributing to the overall storage cost until the customer decides to clean up the test failover. The frequency and number of drills conducted throughout the year directly impact this minimal cost.
69
+
> -**Disaster Recovery Drills**: Each disaster recovery drill, such as test failovers, involves creating a snapshot of the replica storage. These snapshots are stored as new target storage disks, contributing to the overall storage cost until the user decides to clean up the test failover. The frequency and number of drills conducted throughout the year directly impact this minimal cost.
70
70
>
71
71
> -**Compute Capacity Cost**: The Compute Capacity Cost is relevant only during active disaster recovery drills or an actual disaster. This cost is associated with the virtual machine compute capacity used during a test failover or failover event. Under normal conditions, with no ongoing drills or disaster events, this cost is typically zero.
0 commit comments