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/azure-to-azure-how-to-reprotect.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,21 +59,25 @@ By default, the following occurs:
59
59
1. Temporary replicas of the source disks (disks attached to the VMs in secondary region) are created with the name `ms-asr-<GUID>`, that are used to transfer / read data. The temp disks let us utilize the complete bandwidth of the disk instead of only 16% bandwidth of the original disks (that are connected to the VM). The temp disks are deleted once the reprotection completes.
60
60
1. If the target availability set doesn't exist, a new one is created as part of the reprotect job if necessary. If you've customized the reprotection settings, then the selected set is used.
61
61
62
-
When you trigger a reprotect job, and the target VM exists, the following occurs:
62
+
**When you trigger a reprotect job, and the target VM exists, the following occurs:**
63
63
64
64
1. The target side VM is turned off if it's running.
65
65
1. If the VM is using managed disks, a copy of the original disk is created with an `-ASRReplica` suffix. The original disks are deleted. The `-ASRReplica` copies are used for replication.
66
66
1. If the VM is using unmanaged disks, the target VM's data disks are detached and used for replication. A copy of the OS disk is created and attached on the VM. The original OS disk is detached and used for replication.
67
67
1. Only changes between the source disk and the target disk are synchronized. The differentials are computed by comparing both the disks and then transferred. Check below to find the estimated time to complete the reprotection.
68
68
1. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
69
69
70
-
When you trigger a reprotect job, and the target VM and disks don't exist, the following occurs:
70
+
**When you trigger a reprotect job, and the target VM and disks don't exist, the following occurs:**
71
71
72
72
1. If the VM is using managed disks, replica disks are created with `-ASRReplica` suffix. The `-ASRReplica` copies are used for replication.
73
73
1. If the VM is using unmanaged disks, replica disks are created in the target storage account.
74
74
1. The entire disks are copied from the failed over region to the new target region.
75
75
1. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
76
76
77
+
> [!NOTE]
78
+
> The `ms-asr` disks are temporary disks that are deleted after the *reprotect* action is completed. You will be charged a minimal cost based on the Azure managed disk price for the time that these disks are active.
79
+
80
+
77
81
#### Estimated time to do the reprotection
78
82
79
83
In most cases, Azure Site Recovery doesn't replicate the complete data to the source region. The amount of data replicated depends on the following conditions:
0 commit comments