You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/migrate/agent-based-migration-architecture.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,19 @@
1
1
---
2
-
title: Agent-based migration in Azure Migrate Server Migration
2
+
title: Agent-based migration in the Migration and modernization tool
3
3
description: Provides an overview of agent-based VMware VM migration in Azure Migrate.
4
4
author: vijain
5
5
ms.author: vijain
6
6
ms.manager: kmadnani
7
7
ms.topic: conceptual
8
-
ms.date: 03/23/2021
8
+
ms.date: 12/12/2022
9
+
ms.custom: engagement-fy23
9
10
---
10
11
11
12
# Agent-based migration architecture
12
13
13
-
This article provides an overview of the architecture and processes used for agent-based replication of VMware VMs with the [Azure Migrate: Server Migration](migrate-services-overview.md#migration-and-modernization-tool) tool.
14
+
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.
14
15
15
-
Using Azure Migrate: Server Migration, you can replicate VMware VMs with a couple of options:
16
+
Using the Migration and modernization tool, you can replicate VMware VMs with a couple of options:
16
17
17
18
- Migrate VMs using agent-based replication, as described in this article.
18
19
- Migrate VMware VMs using agentless replication. This migrates VMs without needing to install anything on them.
@@ -35,7 +36,7 @@ The table summarizes the components used for agent-based migration.
35
36
36
37
**Component** | **Details** | **Installation**
37
38
--- | --- | ---
38
-
**Replication appliance** | The replication appliance (configuration server/process server) is an on-premises server that acts as a bridge between the on-premises environment, and Server Migration. The appliance discovers the on-premises server inventory, so that Server Migration can orchestrate replication and migration. The appliance has two components:<br/><br/> **Configuration server**: Connects to Server Migration and coordinates replication.<br/> **Process server**: Handles data replication. The process server receives server data, compresses and encrypts it, and sends to Azure. In Azure, Server Migration writes the data to managed disks. | By default the process server is installed together with the configuration server on the replication appliance.
39
+
**Replication appliance** | The replication appliance (configuration server/process server) is an on-premises server that acts as a bridge between the on-premises environment, and the Migration and modernization tool. The appliance discovers the on-premises server inventory, so that the Migration and modernization tool can orchestrate replication and migration. The appliance has two components:<br/><br/> **Configuration server**: Connects to the Migration and modernization tool and coordinates replication.<br/> **Process server**: Handles data replication. The process server receives server data, compresses and encrypts it, and sends to Azure. In Azure, the Migration and modernization tool writes the data to managed disks. | By default the process server is installed together with the configuration server on the replication appliance.
39
40
**Mobility service** | The Mobility service is an agent installed on each server you want to replicate and migrate. It sends replication data from the server to the process server. | Installation files for different versions of the Mobility service are located on the replication appliance. You download and install the agent you need, in accordance with the operating system and version of the server you want to replicate.
Copy file name to clipboardExpand all lines: articles/migrate/common-questions-server-migration.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Common questions about Azure Migrate Server Migration
3
-
description: Get answers to common questions about using Azure Migrate Server Migration to migrate machines.
2
+
title: Common questions about the Migration and modernization tool
3
+
description: Get answers to common questions about using Migration and modernization to migrate machines.
4
4
author: piyushdhore-microsoft
5
5
ms.author: piyushdhore
6
6
ms.manager: vijain
@@ -9,7 +9,7 @@ ms.date: 12/12/2022
9
9
ms.custom: engagement-fy23
10
10
---
11
11
12
-
# Azure Migrate Server Migration: Common questions
12
+
# Migration and modernization: Common questions
13
13
14
14
This article answers common questions about the Migration and modernization tool. If you've other questions, check these resources:
15
15
@@ -21,11 +21,11 @@ This article answers common questions about the Migration and modernization tool
21
21
## General questions
22
22
23
23
24
-
### What are the migration options in Azure Migrate: Server Migration?
24
+
### What are the migration options in Migration and modernization?
25
25
26
26
The Migration and modernization tool offers two options for migrating your source servers and virtual machines to Azure: agentless migration and agent-based migration.
27
27
28
-
Regardless of the migration option chosen, the first step to migrate a server using Azure Migration: Server Migration is to start replication for the server. This performs an initial replication of your VM/server data to Azure. After the initial replication is completed, an ongoing replication (ongoing delta-sync) is established to migrate incremental data to Azure. Once the operation reaches the delta-sync stage, you can choose to migrate to Azure at any time.
28
+
Regardless of the migration option chosen, the first step to migrate a server using the Migration and modernization tool is to start replication for the server. This performs an initial replication of your VM/server data to Azure. After the initial replication is completed, an ongoing replication (ongoing delta-sync) is established to migrate incremental data to Azure. Once the operation reaches the delta-sync stage, you can choose to migrate to Azure at any time.
29
29
30
30
Here are some considerations to keep in mind while deciding on the migration option.
31
31
@@ -133,7 +133,7 @@ Migration and modernization tool migrates all the UEFI-based machines to Azure a
133
133
134
134
### Can I migrate Active Directory domain-controllers using Azure Migrate?
135
135
136
-
The Migration and modernization tool is application agnostic and works for most applications. When you migrate a server using the Migration and modernization tool, all the applications installed on the server are migrated along with it. However, for some applications, alternate migration methods other than server migration may be better suited for the migration. For Active Directory, if hybrid environments where the on-premises site is connected to your Azure environment, you can extend your Directory into Azure by adding extra domain controllers in Azure and setting up Active Directory replication. If you're migrating into an isolated environment in Azure requiring its own domain controllers (or testing applications in a sandbox environment), you can migrate servers using the Migration and modernization tool.
136
+
The Migration and modernization tool is application agnostic and works for most applications. When you migrate a server using the Migration and modernization tool, all the applications installed on the server are migrated along with it. However, for some applications, alternate migration methods other than Migration and modernization may be better suited for the migration. For Active Directory, if hybrid environments where the on-premises site is connected to your Azure environment, you can extend your Directory into Azure by adding extra domain controllers in Azure and setting up Active Directory replication. If you're migrating into an isolated environment in Azure requiring its own domain controllers (or testing applications in a sandbox environment), you can migrate servers using the Migration and modernization tool.
137
137
138
138
139
139
### Can I upgrade my OS while migrating?
@@ -146,7 +146,7 @@ To [migrate VMware VMs](server-migrate-overview.md) using VMware agent-based or
146
146
147
147
### Can I consolidate multiple source VMs into one VM while migrating?
148
148
149
-
Azure Migrate server migration capabilities support likeforlike migrations currently. We don't support consolidating servers or upgrading the operating system as part of the migration.
149
+
Migration and modernization capabilities support like-for-like migrations currently. We don't support consolidating servers or upgrading the operating system as part of the migration.
150
150
151
151
### Will Windows Server 2008 and 2008 R2 be supported in Azure after migration?
152
152
@@ -163,7 +163,7 @@ Review this article to [prepare your Windows Server 2003 machines for migration]
163
163
## Agentless VMware migration
164
164
### How does agentless migration work?
165
165
166
-
Azure Migrate: Server Migration provides agentless replication options for the migration of VMware virtual machines and Hyper-V virtual machines running Windows or Linux. The tool also provides another agent-based replication option for Windows and Linux servers that can be used to migrate physical servers, and x86/x64 virtual machines on VMware, Hyper-V, AWS, GCP, etc. The agent-based replication option requires the installation of agent software on the server/virtual machine that’s being migrated, whereas in the agentless option no software needs to be installed on the virtual machines themselves, thus offering more convenience and simplicity over the agent-based replication option.
166
+
The Migration and modernization tool provides agentless replication options for the migration of VMware virtual machines and Hyper-V virtual machines running Windows or Linux. The tool also provides another agent-based replication option for Windows and Linux servers that can be used to migrate physical servers, and x86/x64 virtual machines on VMware, Hyper-V, AWS, GCP, etc. The agent-based replication option requires the installation of agent software on the server/virtual machine that’s being migrated, whereas in the agentless option no software needs to be installed on the virtual machines themselves, thus offering more convenience and simplicity over the agent-based replication option.
167
167
168
168
The agentless replication option works by using mechanisms provided by the virtualization provider (VMware, Hyper-V). In the case of VMware virtual machines, the agentless replication mechanism uses VMware snapshots and VMware changed block tracking technology to replicate data from virtual machine disks. This mechanism is similar to the one used by many backup products. In the case of Hyper-V virtual machines, the agentless replication mechanism uses VM snapshots and the change tracking capability of the Hyper-V replica to replicate data from virtual machine disks.
169
169
@@ -297,7 +297,7 @@ For an agent-based method of replication, the Deployment Planner can help profil
297
297
298
298
### How does agentless migration work?
299
299
300
-
Azure Migrate: Server Migration provides agentless replication options for the migration of VMware virtual machines and Hyper-V virtual machines running Windows or Linux. The tool also provides an additional agent-based replication option for Windows and Linux servers that can be used to migrate physical servers, as well as x86/x64 virtual machines on VMware, Hyper-V, AWS, GCP, etc. The agent-based replication option requires the installation of agent software on the server/virtual machine that’s being migrated, whereas in the agentless option no software needs to be installed on the virtual machines themselves, thus offering additional convenience and simplicity over the agent-based replication option.
300
+
The Migration and modernization tool provides agentless replication options for the migration of VMware virtual machines and Hyper-V virtual machines running Windows or Linux. The tool also provides an additional agent-based replication option for Windows and Linux servers that can be used to migrate physical servers, as well as x86/x64 virtual machines on VMware, Hyper-V, AWS, GCP, etc. The agent-based replication option requires the installation of agent software on the server/virtual machine that’s being migrated, whereas in the agentless option no software needs to be installed on the virtual machines themselves, thus offering additional convenience and simplicity over the agent-based replication option.
301
301
302
302
The agentless replication option works by using mechanisms provided by the virtualization provider (VMware, Hyper-V). In the case of Hyper-V virtual machines, the agentless replication mechanism uses VM snapshots and the change tracking capability of the Hyper-V replica to replicate data from virtual machine disks.
Copy file name to clipboardExpand all lines: articles/migrate/concepts-migration-planning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ A few recommendations:
114
114
115
115
**State** | **Action**
116
116
--- | ---
117
-
**Azure ready VMs** | Export the assessment report, and filter all servers with state *Ready for Azure*. This might be the first group of servers that you lift and shift to Azure, using the [Azure Migrate: Server Migration](migrate-services-overview.md#migration-and-modernization-tool) tool.
117
+
**Azure ready VMs** | Export the assessment report, and filter all servers with state *Ready for Azure*. This might be the first group of servers that you lift and shift to Azure, using the [Migration and modernization](migrate-services-overview.md#migration-and-modernization-tool) tool.
118
118
**End-of-support operating systems** | Export the assessment report, and filter all servers running Windows Server 2008 R2/Windows Server 2008. These operating systems are at the end of support, and only Azure provides a free three years of security updates when you migrate them to Azure. If you combine Azure Hybrid Benefit, and use RIs, the savings could be much higher.
119
119
**SQL Server migration** | Use the database assessment recommendations to migrate databases that are ready for Azure SQL Database, using the Azure Migrate: Database Migration tool. Migrate the databases ready for Azure SQL VM using the Migration and modernization tool.
120
120
**End-of-support software** | Export your application inventory, and filter for any software/extensions that might be reaching end-of-support. Prioritize these applications for migration.
0 commit comments