Skip to content

Commit 0ec8a00

Browse files
Merge pull request #251820 from ankitaduttaMSFT/gi114015
GI114015
2 parents 3ca37ac + a368d81 commit 0ec8a00

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

articles/site-recovery/vmware-azure-prepare-failback.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Prepare VMware VMs for reprotection and failback with Azure Site Recovery
33
description: Prepare for fail back of VMware VMs after failover with Azure Site Recovery
44
ms.topic: conceptual
55
ms.service: site-recovery
6-
ms.date: 12/02/2021
6+
ms.date: 09/18/2023
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
99
ms.custom: engagement-fy23
@@ -13,9 +13,7 @@ ms.custom: engagement-fy23
1313

1414
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.
1515

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
1917

2018
You need a number of components and settings in place before you can reprotect and fail back from Azure.
2119

@@ -43,7 +41,7 @@ A number of ports must be open for reprotection/failback. The following graphic
4341

4442
## Deploy a separate master target server
4543

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).
4745
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.
4846
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.
4947
- 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
7068

7169
## Next steps
7270

73-
[Reprotect](vmware-azure-reprotect.md) a VM.
71+
Learn how to [reprotect](vmware-azure-reprotect.md) a VM.

0 commit comments

Comments
 (0)