Skip to content

Commit cd017ec

Browse files
committed
Content Freshness - Test replication
1 parent 2198750 commit cd017ec

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

articles/migrate/how-to-test-replicating-virtual-machines.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Tests migrate replicating virtual machines
2+
title: Test migrate replicating virtual machines
33
description: Learn best practices for testing replicating virtual machines
44
author: piyushdhore-microsoft
55
ms.author: piyushdhore
66
ms.manager: vijain
77
ms.topic: how-to
8-
ms.date: 3/23/2022
8+
ms.date: 10/10/2022
99
---
1010

1111

@@ -17,30 +17,31 @@ This article helps you understand how to test replicating virtual machines. Test
1717

1818
## Prerequisites
1919

20-
Before you get started, you need to perform the following steps:
20+
Before you get started, perform the following steps:
2121

22-
- Create the Azure Migrate project.
23-
- Deploy the appliance for your scenario and complete discovery of virtual machines.
22+
- [Create](create-manage-projects.md) an Azure Migrate project.
23+
- Deploy the appliance for your scenario and complete the discovery of virtual machines.
2424
- Configure replication for one or more virtual machines that are to be migrated.
25+
2526
> [!IMPORTANT]
26-
> You'll need to have at least one replicating virtual machine in the project before you can perform test migration.
27+
> You'll need to have at least one replicating virtual machine in the project before you can test the migration.
2728
28-
To learn how to perform the above, review the following tutorials based on your scenarios
29-
- [Migrating VMware virtual machines to Azure with the agentless migration method](./tutorial-migrate-vmware.md).
30-
- [Migrating Hyper-V VMs to Azure with Azure Migrate Server Migration](./tutorial-migrate-hyper-v.md)
31-
- [Migrating machines as physical server to Azure with Azure Migrate.](./tutorial-migrate-physical-virtual-machines.md)
29+
Review the following tutorials based on your environment:
30+
- [Migrating VMware VMs with agentless migration](./tutorial-migrate-vmware.md).
31+
- [Migrating Hyper-V VMs to Azure](./tutorial-migrate-hyper-v.md).
32+
- [Migrating machines as physical servers to Azure](./tutorial-migrate-physical-virtual-machines.md)
3233

3334

3435
## Setting up your test environment
3536

36-
The requirements for a test environment can vary according to your needs. Azure Migrate gives customers complete flexibility to create their own test environment. An option to select the VNet is given during test migration. You can customize the setting of this VNet to create a test environment according to your need.
37+
The requirements for a test environment can vary according to your needs. Azure Migrate provides customers complete flexibility to create their own test environment. An option to select the VNet is provided during test migration. You can customize the setting of this VNet to create a test environment according to your requirement.
3738

3839
Furthermore, you can create 1:1 mapping between subnets of the VNet and Network Interface Cards (NICs) on VM, which gives more flexibility in creating the test environment.
3940

4041
> [!Note]
4142
> Currently, the subnet selection feature is available only for agentless VMware migration scenario.
4243
43-
The following logic is used for subnet selection for other scenarios (Migration from Hyper-V environment and physical server migration)
44+
The following logic is used for subnet selection for other scenarios (Migration from Hyper-V environment and physical server migration).
4445

4546
- If a target subnet (other than default) was specified as an input while enabling replication. Azure Migrate prioritizes using a subnet with the same name in the Virtual Network selected for the test migration.
4647

0 commit comments

Comments
 (0)