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
+39-38Lines changed: 39 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,28 +8,28 @@ ms.service: site-recovery
8
8
ms.topic: article
9
9
ms.date: 11/27/2018
10
10
ms.author: rajanaki
11
-
12
-
13
11
---
12
+
14
13
# Reprotect failed over Azure VMs to the primary region
15
14
16
-
When you [fail over](site-recovery-failover.md) Azure VMs from one region to another using [Azure Site Recovery](site-recovery-overview.md), the VMs boot up in the secondary region, in an **unprotected** state. If you want to fail back the VMs to the primary region, you need to do the following:
15
+
When you [fail over](site-recovery-failover.md) Azure VMs from one region to another using [Azure Site Recovery](site-recovery-overview.md), the VMs boot up in the secondary region, in an **unprotected** state. If you want to fail back the VMs to the primary region, do the following tasks:
17
16
18
-
- Reprotect the VMs in the secondary region, so that they start to replicate to the primary region.
19
-
- After reprotection completes and the VMs are replicating, you can fail them over from the secondary to primary region.
17
+
1. Reprotect the VMs in the secondary region, so that they start to replicate to the primary region.
18
+
1. After reprotection completes and the VMs are replicating, you can fail over from the secondary to primary region.
20
19
21
20
## Prerequisites
22
-
1. The VM failover from the primary to secondary region must be committed.
23
-
2. The primary target site should be available, and you should be able to access or create resources in that region.
21
+
22
+
- The VM failover from the primary to secondary region must be committed.
23
+
- The primary target site should be available, and you should be able to access or create resources in that region.
24
24
25
25
## Reprotect a VM
26
26
27
27
1. In **Vault** > **Replicated items**, right-click the failed over VM, and select **Re-Protect**. The reprotection direction should show from secondary to primary.
2. Review the resource group, network, storage, and availability sets. Then click **OK**. If there are any resources marked as new, they are created as part of the reprotection process.
32
-
3. The reprotection job seeds the target site with the latest data. After that finishes, delta replication takes place. Then, you can fail over back to the primary site. You can select the storage account or the network you want to use during reprotect, using the customize option.
31
+
1. Review the resource group, network, storage, and availability sets. Then click **OK**. If there are any resources marked as new, they're created as part of the reprotection process.
32
+
1. The reprotection job seeds the target site with the latest data. After the job finishes, delta replication takes place. Then, you can fail over back to the primary site. You can select the storage account or the network you want to use during reprotect, using the customize option.
@@ -41,49 +41,50 @@ You can customize the following properties of the target VM during reprotection.
41
41
42
42
|Property |Notes |
43
43
|---------|---------|
44
-
|Target resource group | Modify the target resource group in which the VM is created. As the part of reprotection, the target VM is deleted. You can choose a new resource group under which to create the VM after failover.|
45
-
|Target virtual network | The target network can't be changed during the reprotect job. To change the network, redo the network mapping.|
46
-
|Target Storage (Secondary VM does not use managed disks) | You can change the storage account that the VM uses after failover.|
47
-
|Replica managed disks (Secondary VM uses managed disks) | Site Recovery creates replica managed disks in the primary region to mirror the secondary VM's managed disks.|
48
-
|Cache Storage | You can specify a cache storage account to be used during replication. By default, a new cache storage account is be created, if it doesn't exist.|
49
-
|Availability Set |If the VM in the secondary region is part of an availability set, you can choose an availability set for the target VM in the primary region. By default, Site Recovery tries to find the existing availability set in the primary region, and use it. During customization, you can specify a new availability set.|
44
+
|Target resource group | Modify the target resource group in which the VM is created. As the part of reprotection, the target VM is deleted. You can choose a new resource group under which to create the VM after failover. |
45
+
|Target virtual network | The target network can't be changed during the reprotect job. To change the network, redo the network mapping. |
46
+
|Target storage (Secondary VM doesn't use managed disks) | You can change the storage account that the VM uses after failover. |
47
+
|Replica managed disks (Secondary VM uses managed disks) | Site Recovery creates replica managed disks in the primary region to mirror the secondary VM's managed disks. |
48
+
|Cache storage | You can specify a cache storage account to be used during replication. By default, a new cache storage account is created, if it doesn't exist. |
49
+
|Availability set |If the VM in the secondary region is part of an availability set, you can choose an availability set for the target VM in the primary region. By default, Site Recovery tries to find the existing availability set in the primary region, and use it. During customization, you can specify a new availability set. |
50
50
51
51
### What happens during reprotection?
52
52
53
-
By default the following occurs:
53
+
By default, the following occurs:
54
54
55
55
1. A cache storage account is created in the region where the failed over VM is running.
56
-
2. If the target storage account (the original storage account in the primary region) doesn't exist, a new one is created. The assigned storage account name is the name of the storage account used by the secondary VM, suffixed with "asr".
57
-
3. If your VM uses managed disks, replica managed disks are created in the primary region to store the data replicated from the secondary VM's disks.
58
-
4. If the target availability set doesn't exist, a new one is created as part of the reprotect job if required. If you have customized the reprotection settings, then the selected set is used.
56
+
1. If the target storage account (the original storage account in the primary region) doesn't exist, a new one is created. The assigned storage account name is the name of the storage account used by the secondary VM, suffixed with `asr`.
57
+
1. If your VM uses managed disks, replica managed disks are created in the primary region to store the data replicated from the secondary VM's disks.
58
+
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.
59
59
60
60
When you trigger a reprotect job, and the target VM exists, the following occurs:
61
61
62
62
1. The target side VM is turned off if it's running.
63
-
2. If the VM is using managed disks, a copy of original disks are created with '-ASRReplica' suffix. The original disks are deleted. The '-ASRReplica' copies are used for replication.
64
-
3. 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.
65
-
4. 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.
66
-
5. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
63
+
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.
64
+
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.
65
+
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.
66
+
1. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
67
+
68
+
When you trigger a reprotect job, and the target VM and disks don't exist, the following occurs:
67
69
68
-
When you trigger a reprotect job, and the target VM and disks do not exist, the following occurs:
69
-
1. If the VM is using managed disks, replica disks are created with '-ASRReplica' suffix. The '-ASRReplica' copies are used for replication.
70
-
2. If the VM is using unmanaged disks, replica disks are created in the target storage account.
71
-
3. The entire disks are copied from the failed over region to the new target region.
72
-
4. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
70
+
1. If the VM is using managed disks, replica disks are created with `-ASRReplica` suffix. The `-ASRReplica` copies are used for replication.
71
+
1. If the VM is using unmanaged disks, replica disks are created in the target storage account.
72
+
1. The entire disks are copied from the failed over region to the new target region.
73
+
1. After the synchronization completes, the delta replication begins, and a recovery point is created in line with the replication policy.
73
74
74
-
#### Estimated time to do the reprotection
75
+
#### Estimated time to do the reprotection
75
76
76
-
In most cases, Azure Site Recovery doesn’t replicate the complete data to the source region.
77
-
Below are the conditions that determines how much data would be replicated:
77
+
In most cases, Azure Site Recovery doesn’t replicate the complete data to the source region.
78
+
The following conditions determine how much data is replicated:
78
79
79
-
1.If the source VM data is deleted, corrupted, or inaccessible due to some reason, like a resource group change/delete, then during reprotection a complete Site Recovery will happen as there is no data available on the source region to use.
80
-
2. If the source VM data is accessible, then only differentials are computed by comparing both the disks and then transferred. Check the table below to get the estimated time.
80
+
1.If the source VM data is deleted, corrupted, or inaccessible for some reason, such as a resource group change/delete, then during reprotection a complete initial replication will happen because there's no data available on the source region to use.
81
+
1.If the source VM data is accessible, then only differentials are computed by comparing both the disks and then transferred. Check the table below to get the estimated time.
81
82
82
-
|Example situation | Time taken to Reprotect|
83
+
|Example situation | Time taken to reprotect|
83
84
|---|---|
84
-
|Source region has 1 VM with 1 TB standard Disk<br/>- Only 127 GB data is used, and the rest of the disk is empty<br/>- Disk type is standard with 60 MiB/S throughput<br/>- No data change after failover| Approximate time: 45 minutes – 1.5 hours<br/> - During reprotection, Site Recovery will populate the checksum of all data which will take 127 GB/ 45 MBs~45 minutes<br/>- Some overhead time is required for Site Recovery to auto scale: approx. 20-30 minutes<br/>- No Egress charges |
85
-
|Source region has 1 VM with 1 TB standard Disk<br/>- Only 127 GB data is used and rest of the disk is empty<br/>- Disk type is standard with 60 MiB/S throughput<br/>- 45 GB data changes after failover| Approximate time: 1 hours – 2 hours<br/>- During reprotection, Site Recovery will populate the checksum of all data which will take 127 GB/ 45 MBs~45 minutes<br/>- Transfer time to apply changes of 45 GB that is 45 GB/ 45 MBps ~ 17 minutes<br/>- Egress charges would be for 45 GB data changes, not for the checksum |
86
-
85
+
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used, and the rest of the disk is empty.<br/>Disk type is standard with 60 MiB/S throughput.<br/>No data change after failover.| Approximate time: 45 minutes – 1.5 hours.<br/>During reprotection, Site Recovery will populate the checksum of all data that will take 127 GB/ 45 MBs, approximately 45 minutes.<br/>Some overhead time is required for Site Recovery to auto scale, approximately 20-30 minutes.<br/>No Egress charges.|
86
+
|Source region has 1 VM with 1 TB standard disk.<br/>Only 127 GB data is used and rest of the disk is empty.<br/>Disk type is standard with 60 MiB/S throughput.<br/>45 GB data changes after failover.| Approximate time: 1 hour – 2 hours.<br/>During reprotection, Site Recovery will populate the checksum of all data that will take 127 GB/ 45 MBs, approximately 45 minutes.<br/>Transfer time to apply changes of 45 GB that is 45 GB/ 45 MBps, approximately 17 minutes.<br/>Egress charges would be for 45 GB data changes, not for the checksum.|
87
+
87
88
## Next steps
88
89
89
-
After the VM is protected, you can initiate a failover. The failover shuts down the VM in the secondary region and creates and boots the VM in the primary region, with some small downtime during this process. We recommend you choose an appropriate time for this process and that you run a test failover before initiating a full failover to the primary site. [Learn more](site-recovery-failover.md) about Azure Site Recovery failover.
90
+
After the VM is protected, you can initiate a failover. The failover shuts down the VM in the secondary region and creates and boots the VM in the primary region, with brief downtime during this process. We recommend you choose an appropriate time for this process and that you run a test failover before initiating a full failover to the primary site. [Learn more](site-recovery-failover.md) about Azure Site Recovery failover.
0 commit comments