Skip to content

Commit 853137f

Browse files
author
Ankita Dutta
committed
rephrase checks
1 parent b85fe81 commit 853137f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Move from classic to modernized VMware disaster recovery.
33
description: Learn about the architecture, necessary infrastructure, and FAQs about moving your VMware replications from classic to modernized protection architecture.
44
ms.service: site-recovery
55
ms.topic: conceptual
6-
ms.date: 03/15/2023
6+
ms.date: 03/16/2023
77
author: ankitaduttaMSFT
88
ms.custom: engagement-fy23
99
---
@@ -138,11 +138,11 @@ It is important to note that the classic architecture for disaster recovery will
138138

139139
### What machines should be migrated to the modernized architecture?
140140

141-
All VMware machines, which are replicated using a configuration server, should be migrated to the modernized architecture. As of now, we have released support for VMware machines.
141+
All VMware machines that are replicated using a configuration server should be migrated to the modernized architecture. Currently, we’ve released support for VMware machines.
142142

143143
### Where should my modernized Recovery Services vault be created?
144144

145-
The modernized Recovery Services vault should be present in the same region and tenant as the classic vault. It can be a part of any subscription or resource group.
145+
The modernized Recovery Services vault should be located in the same region and tenant as the classic vault. It can be a part of any subscription or resource group.
146146

147147
### Will my replication continue while the migration is happening?
148148

0 commit comments

Comments
 (0)