Skip to content

Commit 4cc0e7b

Browse files
huypubhuypub
authored
Merge pull request #274474 from MicrosoftDocs/release-vmware-migration
Standing pull request with main - release-vmware-migration
2 parents fa6b8c1 + 2a34c4f commit 4cc0e7b

25 files changed

+548
-271
lines changed

‎articles/migrate/.openpublishing.redirection.migrate.json

Lines changed: 104 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,106 @@
2020
"redirect_url": "discovered-metadata",
2121
"redirect_document_id": false
2222
},
23+
{
24+
"source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware-migration.md",
25+
"redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware-migration?context=/azure/migrate/context/vmware-context",
26+
"redirect_document_id": true
27+
},
28+
{
29+
"source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware.md",
30+
"redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware?context=/azure/migrate/context/vmware-context",
31+
"redirect_document_id": true
32+
},
33+
{
34+
"source_path_from_root": "/articles/migrate/tutorial-discover-vmware.md",
35+
"redirect_url": "/azure/migrate/vmware/tutorial-discover-vmware?context=/azure/migrate/context/vmware-context",
36+
"redirect_document_id": true
37+
},
38+
{
39+
"source_path_from_root": "/articles/migrate/set-discovery-scope.md",
40+
"redirect_url": "/azure/migrate/vmware/set-discovery-scope?context=/azure/migrate/context/vmware-context",
41+
"redirect_document_id": true
42+
},
43+
{
44+
"source_path_from_root": "/articles/migrate/how-to-set-up-appliance-vmware.md",
45+
"redirect_url": "/azure/migrate/vmware/how-to-set-up-appliance-vmware?context=/azure/migrate/context/vmware-context",
46+
"redirect_document_id": true
47+
},
48+
{
49+
"source_path_from_root": "/articles/migrate/tutorial-import-vmware-using-rvtools-xlsx.md",
50+
"redirect_url": "/azure/migrate/vmware/tutorial-import-vmware-using-rvtools-xlsx?context=/azure/migrate/context/vmware-context",
51+
"redirect_document_id": true
52+
},
53+
{
54+
"source_path_from_root": "/articles/migrate/tutorial-assess-vmware-azure-vm.md",
55+
"redirect_url": "/azure/migrate/vmware/tutorial-assess-vmware-azure-vm?context=/azure/migrate/context/vmware-context",
56+
"redirect_document_id": true
57+
},
58+
{
59+
"source_path_from_root": "/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md",
60+
"redirect_url": "/azure/migrate/vmware/tutorial-assess-vmware-azure-vmware-solution?context=/azure/migrate/context/vmware-context",
61+
"redirect_document_id": true
62+
},
63+
{
64+
"source_path_from_root": "/articles/migrate/server-migrate-overview.md",
65+
"redirect_url": "/azure/migrate/vmware/server-migrate-overview?context=/azure/migrate/context/vmware-context",
66+
"redirect_document_id": true
67+
},
68+
{
69+
"source_path_from_root": "/articles/migrate/concepts-vmware-agentless-migration.md",
70+
"redirect_url": "/azure/migrate/vmware/concepts-vmware-agentless-migration?context=/azure/migrate/context/vmware-context",
71+
"redirect_document_id": true
72+
},
73+
{
74+
"source_path_from_root": "/articles/migrate/prepare-for-agentless-migration.md",
75+
"redirect_url": "/azure/migrate/vmware/prepare-for-agentless-migration?context=/azure/migrate/context/vmware-context",
76+
"redirect_document_id": true
77+
},
78+
{
79+
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware.md",
80+
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware?context=/azure/migrate/context/vmware-context",
81+
"redirect_document_id": true
82+
},
83+
{
84+
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware-powershell.md",
85+
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware-powershell?context=/azure/migrate/context/vmware-context",
86+
"redirect_document_id": true
87+
},
88+
{
89+
"source_path_from_root": "/articles/migrate/troubleshoot-changed-block-tracking-replication.md",
90+
"redirect_url": "/azure/migrate/vmware/troubleshoot-changed-block-tracking-replication?context=/azure/migrate/context/vmware-context",
91+
"redirect_document_id": true
92+
},
93+
{
94+
"source_path_from_root": "/articles/migrate/troubleshoot-replication-vmware.md",
95+
"redirect_url": "/azure/migrate/vmware/troubleshoot-replication-vmware?context=/azure/migrate/context/vmware-context",
96+
"redirect_document_id": true
97+
},
98+
{
99+
"source_path_from_root": "/articles/migrate/agent-based-migration-architecture.md",
100+
"redirect_url": "/azure/migrate/vmware/agent-based-migration-architecture?context=/azure/migrate/context/vmware-context",
101+
"redirect_document_id": true
102+
},
103+
{
104+
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware-agent.md",
105+
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware-agent?context=/azure/migrate/context/vmware-context",
106+
"redirect_document_id": true
107+
},
108+
{
109+
"source_path_from_root": "/articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md",
110+
"redirect_url": "/azure/migrate/vmware/how-to-migrate-vmware-vms-with-cmk-disks?context=/azure/migrate/context/vmware-context",
111+
"redirect_document_id": true
112+
},
113+
{
114+
"source_path_from_root": "/articles/migrate/how-to-automate-migration.md",
115+
"redirect_url": "/azure/migrate/vmware/how-to-automate-migration?context=/azure/migrate/context/vmware-context",
116+
"redirect_document_id": true
117+
},
118+
{
119+
"source_path_from_root": "/articles/migrate/how-to-test-replicating-virtual-machines.md",
120+
"redirect_url": "/azure/migrate/vmware/how-to-test-replicating-virtual-machines?context=/azure/migrate/context/vmware-context",
121+
"redirect_document_id": true
122+
},
23123
{
24124
"source_path_from_root": "/articles/migrate/migrate-scenarios-assessment.md",
25125
"redirect_url": "contoso-migration-assessment",
@@ -162,7 +262,7 @@
162262
},
163263
{
164264
"source_path_from_root": "/articles/migrate/tutorial-assess-vmware.md",
165-
"redirect_url": "tutorial-assess-vmware-azure-vm",
265+
"redirect_url": "/azure/migrate/vmware/tutorial-assess-vmware-azure-vm?context=/azure/migrate/context/vmware-context",
166266
"redirect_document_id": false
167267
},
168268
{
@@ -182,17 +282,17 @@
182282
},
183283
{
184284
"source_path_from_root": "/articles/migrate/tutorial-prepare-vmware.md",
185-
"redirect_url": "tutorial-discover-vmware",
285+
"redirect_url": "/azure/migrate/vmware/tutorial-discover-vmware?context=/azure/migrate/context/vmware-context",
186286
"redirect_document_id": false
187287
},
188288
{
189289
"source_path_from_root": "/articles/migrate/how-to-prepare-linux-for-migration.md",
190-
"redirect_url": "tutorial-prepare-vmware",
290+
"redirect_url": "/azure/migrate/vmware/tutorial-prepare-vmware?context=/azure/migrate/context/vmware-context",
191291
"redirect_document_id": false
192292
},
193293
{
194294
"source_path_from_root": "/articles/migrate/tutorial-assessment-vmware.md",
195-
"redirect_url": "tutorial-prepare-vmware",
295+
"redirect_url": "/azure/migrate/vmware/tutorial-prepare-vmware?context=/azure/migrate/context/vmware-context",
196296
"redirect_document_id": false
197297
},
198298
{

‎articles/migrate/context/vmware-context.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
### YamlMime:ContextObject
22
brand: azure
3-
uhfHeaderId: azure
4-
breadcrumb_path: /azure/migrate/breadcrumb/toc.json
5-
toc_rel: /azure/bread/toc.json
3+
breadcrumb_path: ../breadcrumb/toc.yml
4+
toc_rel: ../vmware/toc.yml

‎articles/migrate/agent-based-migration-architecture.md renamed to ‎articles/migrate/vmware/agent-based-migration-architecture.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,31 @@ ms.manager: kmadnani
77
ms.service: azure-migrate
88
ms.topic: conceptual
99
ms.date: 12/12/2022
10-
ms.custom: engagement-fy23
10+
ms.custom: vmware-scenario-422, engagement-fy23
1111
---
1212

1313
# Agent-based migration architecture
1414

15-
This article provides an overview of the architecture and processes used for agent-based replication of VMware VMs with the [Migration and modernization](migrate-services-overview.md#migration-and-modernization-tool) tool.
15+
This article provides an overview of the architecture and processes used for agent-based replication of VMware VMs with the [Migration and modernization](../migrate-services-overview.md#migration-and-modernization-tool) tool.
1616

1717
Using the Migration and modernization tool, you can replicate VMware VMs with a couple of options:
1818

1919
- Migrate VMs using agent-based replication, as described in this article.
2020
- Migrate VMware VMs using agentless replication. This migrates VMs without needing to install anything on them.
2121

22-
Learn more about [selecting and comparing](server-migrate-overview.md) migration methods for VMware VMs.
22+
Learn more about [selecting and comparing](server-migrate-overview.md?context=/azure/migrate/context/vmware-context) migration methods for VMware VMs.
2323

2424

2525
## Agent-based migration
2626

27-
Agent-based migration is used to migrate on-premises VMware VMs and physical servers to Azure. It can also be used to migrate other on-premises virtualized servers, as well as private and public cloud VMs, including AWS instances, and GCP VMs. Agent-based migration in Azure Migrate uses some backend functionality from the [Azure Site Recovery](../site-recovery/site-recovery-overview.md) service.
27+
Agent-based migration is used to migrate on-premises VMware VMs and physical servers to Azure. It can also be used to migrate other on-premises virtualized servers, as well as private and public cloud VMs, including AWS instances, and GCP VMs. Agent-based migration in Azure Migrate uses some backend functionality from the [Azure Site Recovery]../../site-recovery/site-recovery-overview.md) service.
2828

2929

3030
## Architectural components
3131

3232
The diagram illustrates the components involved in agent-based migration.
3333

34-
![Diagram shows the components for agent-based migration, which are explained in a table.](./media/agent-based-replication-architecture/architecture.png)
34+
![Diagram shows the components for agent-based migration, which are explained in a table.](../media/agent-based-replication-architecture/architecture.png)
3535

3636
The table summarizes the components used for agent-based migration.
3737

@@ -83,7 +83,7 @@ By default, you deploy a single replication appliance that runs both the configu
8383

8484
### Plan VMware deployment
8585

86-
If you're replicating VMware VMs, you can use the [Site Recovery Deployment Planner for VMware](../site-recovery/site-recovery-deployment-planner.md), to help determine performance requirements, including the daily data change rate, and the process servers you need.
86+
If you're replicating VMware VMs, you can use the [Site Recovery Deployment Planner for VMware](../../site-recovery/site-recovery-deployment-planner.md?context=/azure/migrate/context/vmware-context), to help determine performance requirements, including the daily data change rate, and the process servers you need.
8787

8888
### Replication appliance capacity
8989

@@ -122,4 +122,4 @@ VMware traffic that replicates to Azure goes through a specific process server.
122122

123123
## Next steps
124124

125-
Try out [agent-based migration](tutorial-migrate-vmware-agent.md) for [VMware](tutorial-migrate-vmware-agent.md) or [physical servers](tutorial-migrate-physical-virtual-machines.md).
125+
Try out [agent-based migration](tutorial-migrate-vmware-agent.md) for [VMware](tutorial-migrate-vmware-agent.md)

‎articles/migrate/concepts-vmware-agentless-migration.md renamed to ‎articles/migrate/vmware/concepts-vmware-agentless-migration.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.manager: vijain
77
ms.topic: conceptual
88
ms.service: azure-migrate
99
ms.date: 10/18/2023
10-
ms.custom: engagement-fy24
10+
ms.custom: vmware-scenario-422, engagement-fy24
1111
---
1212
# Azure Migrate agentless migration of VMware virtual machines
1313

@@ -17,7 +17,7 @@ This article describes the replication concepts when migrating VMware VMs using
1717

1818
The agentless replication option works by using VMware snapshots and VMware changed block tracking (CBT) technology to replicate data from virtual machine disks. The following block diagram shows you various steps involved when you migrate your virtual machines using the Migration and modernization tool.
1919

20-
![Migration steps.](./media/concepts-vmware-agentless-migration/migration-phases.png)
20+
![Migration steps.](../media/concepts-vmware-agentless-migration/migration-phases.png)
2121

2222
When replication is configured for a virtual machine, it first goes through an initial replication phase. During initial replication, a VM snapshot is taken, and a full copy of data from the snapshot disks is replicated to managed disks in your target subscription.
2323

@@ -169,7 +169,7 @@ We use the following constraints to ensure that we don't exceed the IOPS limits
169169

170170
Azure Migrate supports concurrent replication of 500 virtual machines. When you're planning to replicate more than 300 virtual machines, you must deploy a scale-out appliance. The scale-out appliance is similar to an Azure Migrate primary appliance but consists only of gateway agent to facilitate data transfer to Azure. The following diagram shows the recommended way to use the scale-out appliance.
171171

172-
![Scale-out configuration.](./media/concepts-vmware-agentless-migration/scale-out-configuration.png)
172+
![Scale-out configuration.](../media/concepts-vmware-agentless-migration/scale-out-configuration.png)
173173

174174

175175
You can deploy the scale-out appliance anytime after configuring the primary appliance, but isn't required until there are 300 VMs replicating concurrently. When there are 300 VMs replicating concurrently, you must deploy the scale-out appliance to proceed.
@@ -199,7 +199,7 @@ You could create a policy on the Azure Migrate appliance to throttle replication
199199
> [!NOTE]
200200
> This is applicable to all the replicating VMs from the Azure Migrate appliance simultaneously.
201201
202-
You can also increase and decrease replication bandwidth based on a schedule using the [sample script](./common-questions-server-migration.md).
202+
You can also increase and decrease replication bandwidth based on a schedule using the [sample script](../common-questions-server-migration.md).
203203

204204
### Blackout window
205205

‎articles/migrate/how-to-automate-migration.md renamed to ‎articles/migrate/vmware/how-to-automate-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.manager: kmadnani
77
ms.service: azure-migrate
88
ms.topic: how-to
99
ms.date: 05/11/2023
10-
ms.custom: engagement-fy23
10+
ms.custom: vmware-scenario-422, engagement-fy23
1111
---
1212

1313

‎articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md renamed to ‎articles/migrate/vmware/how-to-migrate-vmware-vms-with-cmk-disks.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: MaryMichael-MS
55
ms.author: v-michaelar
66
ms.topic: how-to
77
ms.date: 05/31/2023
8-
ms.custom: devx-track-azurepowershell, engagement-fy23
8+
ms.custom: vmware-scenario-422, devx-track-azurepowershell, engagement-fy23
99

1010
---
1111

@@ -15,16 +15,16 @@ ms.custom: devx-track-azurepowershell, engagement-fy23
1515

1616
This article describes how to migrate VMware VMs to Azure virtual machines with disks encrypted using server-side encryption(SSE) with customer-managed keys(CMK), using Migration and modernization (agentless replication).
1717

18-
The Migration and modernization portal experience lets you [migrate VMware VMs to Azure with agentless replication.](tutorial-migrate-vmware.md) The portal experience supports DES/CMK. DES should be created before starting replication and must be provided while starting replication. It cannot be provided at the time of migration. In this article, you'll see how to create and deploy an [Azure Resource Manager template](../azure-resource-manager/templates/overview.md) to replicate a VMware VM and configure the replicated disks in Azure to use SSE with CMK.
18+
The Migration and modernization portal experience lets you [migrate VMware VMs to Azure with agentless replication.](tutorial-migrate-vmware.md) The portal experience supports DES/CMK. DES should be created before starting replication and must be provided while starting replication. It cannot be provided at the time of migration. In this article, you'll see how to create and deploy an [Azure Resource Manager template](../../azure-resource-manager/templates/overview.md) to replicate a VMware VM and configure the replicated disks in Azure to use SSE with CMK.
1919

2020
The examples in this article use [Azure PowerShell](/powershell/azure/new-azureps-module-az) to perform the tasks needed to create and deploy the Resource Manager template.
2121

22-
[Learn more](../virtual-machines/disk-encryption.md) about server-side encryption (SSE) with customer managed keys(CMK) for managed disks.
22+
[Learn more](../../virtual-machines/disk-encryption.md) about server-side encryption (SSE) with customer managed keys(CMK) for managed disks.
2323

2424
## Prerequisites
2525

2626
- [Review the tutorial](tutorial-migrate-vmware.md) on migration of VMware VMs to Azure with agentless replication to understand tool requirements.
27-
- [Follow these instructions](./create-manage-projects.md) to create an Azure Migrate project and add the **Migration and modernization** tool to the project.
27+
- [Follow these instructions](../create-manage-projects.md) to create an Azure Migrate project and add the **Migration and modernization** tool to the project.
2828
- [Follow these instructions](how-to-set-up-appliance-vmware.md) to set up the Azure Migrate appliance for VMware in your on-premises environment and complete discovery.
2929

3030
## Prepare for replication
@@ -55,9 +55,9 @@ The Migration and modernization portal experience simplifies preparation of the
5555

5656
A disk encryption set object maps Managed Disks to a Key Vault that contains the CMK to use for SSE. To replicate VMs with CMK, you'll create a disk encryption set and pass it as an input to the replication operation.
5757

58-
Follow the example [here](../virtual-machines/windows/disks-enable-customer-managed-keys-powershell.md) to create a disk encryption set using Azure PowerShell. Ensure that the disk encryption set is created in the target subscription that VMs are being migrated to, and in the target Azure region for the migration.
58+
Follow the example [here](../../virtual-machines/windows/disks-enable-customer-managed-keys-powershell.md) to create a disk encryption set using Azure PowerShell. Ensure that the disk encryption set is created in the target subscription that VMs are being migrated to, and in the target Azure region for the migration.
5959

60-
The disk encryption set can be configured to encrypt managed disks with a customer-managed key, or for double encryption with both a customer-managed key and a platform key. To use the double encryption at rest option configure the disk encryption set as described [here](../virtual-machines/windows/disks-enable-double-encryption-at-rest-powershell.md).
60+
The disk encryption set can be configured to encrypt managed disks with a customer-managed key, or for double encryption with both a customer-managed key and a platform key. To use the double encryption at rest option configure the disk encryption set as described [here](../../virtual-machines/windows/disks-enable-double-encryption-at-rest-powershell.md).
6161

6262
In the example shown below the disk encryption set is configured to use a customer-managed key.
6363

@@ -250,7 +250,7 @@ uuid label name maxSizeInBytes
250250

251251
## Set up replication
252252

253-
You can now deploy the edited Resource Manager template to the project resource group to set up replication for the VM. Learn how to [deploy resource with Azure Resource Manager templates and Azure PowerShell](../azure-resource-manager/templates/deploy-powershell.md)
253+
You can now deploy the edited Resource Manager template to the project resource group to set up replication for the VM. Learn how to [deploy resource with Azure Resource Manager templates and Azure PowerShell](../../azure-resource-manager/templates/deploy-powershell.md)
254254

255255
```azurepowershell
256256
New-AzResourceGroupDeployment -ResourceGroupName $ProjectResourceGroup -TemplateFile "C:\Users\Administrator\Downloads\template.json"

0 commit comments

Comments
 (0)