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/vmware-azure-prepare-failback.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Prepare VMware VMs for reprotection and failback with Azure Site Recovery
3
3
description: Prepare for fail back of VMware VMs after failover with Azure Site Recovery
4
4
ms.topic: conceptual
5
5
ms.service: site-recovery
6
-
ms.date: 12/02/2021
6
+
ms.date: 09/18/2023
7
7
ms.author: ankitadutta
8
8
author: ankitaduttaMSFT
9
9
ms.custom: engagement-fy23
@@ -13,9 +13,7 @@ ms.custom: engagement-fy23
13
13
14
14
After [failover](site-recovery-failover.md) of on-premises VMware VMs or physical servers to Azure, you reprotect the Azure VMs created after failover, so that they replicate back to the on-premises site. With replication from Azure to on-premises in place, you can then fail back by running a failover from Azure to on-premises when you're ready.
15
15
16
-
Before you continue, get a quick overview with this video about how to fail back from Azure to an on-premises site.<br /><br />
17
-
18
-
## Reprotection/failback components
16
+
## Reprotection or failback components
19
17
20
18
You need a number of components and settings in place before you can reprotect and fail back from Azure.
21
19
@@ -43,7 +41,7 @@ A number of ports must be open for reprotection/failback. The following graphic
43
41
44
42
## Deploy a separate master target server
45
43
46
-
1. Note the master target server [requirements and limitations](#reprotectionfailback-components).
44
+
1. Note the master target server [requirements and limitations](#reprotection-or-failback-components).
47
45
2. Create a [Windows](site-recovery-plan-capacity-vmware.md#deploy-additional-master-target-servers) or [Linux](vmware-azure-install-linux-master-target.md) master target server, to match the operating system of the VMs you want to reprotect and fail back.
48
46
3. Make sure you don't use Storage vMotion for the master target server, or failback can fail. The VM machine can't start because the disks aren't available to it.
49
47
- To prevent this, exclude the master target server from your vMotion list.
@@ -70,4 +68,4 @@ A number of ports must be open for reprotection/failback. The following graphic
70
68
71
69
## Next steps
72
70
73
-
[Reprotect](vmware-azure-reprotect.md) a VM.
71
+
Learn how to [reprotect](vmware-azure-reprotect.md) a VM.
0 commit comments