Skip to content

Commit dc36fcb

Browse files
authored
Merge pull request #263779 from MaryMichael-MS/22JanSBMChange
Updated content.
2 parents 4d1e0b6 + ab4980a commit dc36fcb

File tree

2 files changed

+4
-13
lines changed

2 files changed

+4
-13
lines changed
76.3 KB
Loading

articles/migrate/tutorial-migrate-vmware.md

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: piyushdhore
66
ms.manager: vijain
77
ms.topic: tutorial
88
ms.service: azure-migrate
9-
ms.date: 06/19/2023
9+
ms.date: 01/22/2024
1010
ms.custom: mvc, engagement-fy23
1111
---
1212

@@ -81,10 +81,10 @@ Enable replication as follows:
8181

8282
:::image type="content" source="./media/tutorial-migrate-vmware/select-vms-inline.png" alt-text="Screenshot on selecting VMs." lightbox="./media/tutorial-migrate-vmware/select-vms-expanded.png":::
8383

84-
6. In **Target settings**, select the subscription and target region. Specify the resource group in which the Azure VMs reside after migration.
84+
6. In **Target settings**, select the subscription, target region, and Storage account.
8585
> [!Note]
86-
> The region for the project cannot be changed after the first replication is initiated. Please select the region carefully.
87-
7. In **Virtual Network**, select the Azure VNet/subnet which the Azure VMs join after migration.
86+
> After starting first replication of a VM, the storage account cannot be changed. The default option selected in drop down will be used to create a new storage account. If the option is not selected, the storage account will be created in final step of enabling replication.
87+
7. In **Virtual Network**, select the Azure VNet/subnet, which the Azure VMs join after migration.
8888
8. In **Availability options**, select:
8989
- Availability Zone to pin the migrated machine to a specific Availability Zone in the region. Use this option to distribute servers that form a multi-node application tier across Availability Zones. If you select this option, you'll need to specify the Availability Zone to use for each of the selected machine in the Compute tab. This option is only available if the target region selected for the migration supports Availability Zones
9090
- Availability Set to place the migrated machine in an Availability Set. The target Resource Group that was selected must have one or more availability sets in order to use this option.
@@ -133,15 +133,6 @@ Enable replication as follows:
133133
> [!NOTE]
134134
> You can update replication settings any time before replication starts (**Manage** > **Replicating machines**). You can't change settings after replication starts.
135135
136-
### Provisioning for the first time
137-
138-
If this is the first VM you're replicating in the project, the Migration and modernization tool automatically provisions these resources, in same resource group as the project.
139-
140-
- **Service bus**: The Migration and modernization tool uses the service bus to send replication orchestration messages to the appliance.
141-
- **Gateway storage account**: The Migration and modernization tool uses the gateway storage account to store state information about the VMs being replicated.
142-
- **Log storage account**: The Azure Migrate appliance uploads replication logs for VMs to a log storage account. Azure Migrate applies the replication information to the replica managed disks.
143-
- **Key vault**: The Azure Migrate appliance uses the key vault to manage connection strings for the service bus, and access keys for the storage accounts used in replication.
144-
145136
## Track and monitor
146137

147138
1. Track job status in the portal notifications.

0 commit comments

Comments
 (0)