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
2. A capable Windows Hyper-V or VMware host on which to run the agent VM.<br/> See the [Recommended compute and memory resources](#recommended-compute-and-memory-resources) section in this article for details about resource requirements for the agent VM.
52
50
53
51
> [!NOTE]
54
-
> At present, Windows Hyper-V and VMware are the only supported virtualization environments for your agent VM. Other virtualization environments have not been tested and are not supported.
52
+
> Currently, Windows Hyper-V and VMware are the only supported virtualization environments for your agent VM. Other virtualization environments aren't tested and are therefore not supported.
55
53
56
54
## Determine required resources for the VM
57
55
@@ -80,7 +78,7 @@ You can get help with [creating a virtual switch for Hyper-V virtual machines](/
80
78
**Number of items***refers to the total number of files and folders in the source.*
81
79
82
80
> [!IMPORTANT]
83
-
> While agent VMs below minimal specs may work for your migration, they may not perform optimally and are not supported.
81
+
> While agent VMs below minimal specs might work for your migration, performance is suboptimal and therefore not supported.
84
82
85
83
The [Performance targets](performance-targets.md) article contains test results from different source namespaces and VM resources.
86
84
@@ -96,11 +94,11 @@ Images for agent VMs are hosted on Microsoft Download Center as a zip file. Down
96
94
97
95
The following steps describe the process for creating a VM using Microsoft Hyper-V. Consult the VMware support website for detailed guidance on creating a VMware-based VM.
98
96
99
-
1. Create a new VM to host the agent. Open **Hyper-V Manager**. In the **Actions** pane, select **New** and **Virtual Machine...** to launch the **New Virtual Machine Wizard**.
97
+
1. Create a new VM on which to host the agent. Open **Hyper-V Manager**. In the **Actions** pane, select **New** and **Virtual Machine...** to launch the **New Virtual Machine Wizard**.
100
98
101
99
:::image type="content" source="media/agent-deploy/agent-vm-create-sml.png" alt-text="Image showing how to launch the New Virtual Machine Wizard from within the Hyper-V Manager." lightbox="media/agent-deploy/agent-vm-create-lrg.png":::
102
100
103
-
1. Within the **Specify Name and Location** pane, specify values for the agent VM's **Name** and **Location** fields. The location should match the folder where the VHD is stored, if possible. Select **Next**.
101
+
1. Within the **Specify Name and Location** pane, provide values for the agent VM's **Name** and **Location** fields. The location should match the folder where the VHD is stored, if possible. Select **Next**.
104
102
105
103
:::image type="content" source="media/agent-deploy/agent-name-select-sml.png" alt-text="Image showing the location of the Name and Location fields within the New Virtual Machine Wizard." lightbox="media/agent-deploy/agent-name-select-lrg.png":::
106
104
@@ -109,7 +107,7 @@ The following steps describe the process for creating a VM using Microsoft Hyper
109
107
:::image type="content" source="media/agent-deploy/agent-vm-generation-select-sml.png" lightbox="media/agent-deploy/agent-vm-generation-select-lrg.png" alt-text="Image showing the location of the VM Generation options within the New Virtual Machine Wizard.":::
110
108
111
109
> [!IMPORTANT]
112
-
> Only *Generation 1* VMs are supported. This Linux image won't boot as a *Generation 2* VM.
110
+
> Only *Generation 1* VMs are supported. This Linux image doesn't boot as a *Generation 2* VM.
113
111
114
112
1. If you haven't already, [determine the amount of memory you need for your VM](#determine-required-resources-for-the-vm). Enter this amount in the **Assign Memory** pane, noting that you need to enter the value in MiB. 1 GiB = 1024 MiB. Using the **Dynamic Memory** feature is fine.
115
113
@@ -174,7 +172,7 @@ xdmsh> 4
174
172
Select the option **4) Unregister**. You're prompted for confirmation.
175
173
176
174
> [!WARNING]
177
-
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent you should register a new, previously unregistered agent VM. Do not reuse a previously unregistered agent VM.
175
+
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM isn't supported. If you need a new agent you should register a new, previously unregistered agent VM. Don't reuse a previously unregistered agent VM.
178
176
179
177
# [Azure portal](#tab/azure-portal)
180
178
@@ -185,7 +183,7 @@ You can unregister an agent in the Azure portal by navigating to your storage mo
185
183
- Select **Unregister agent** and wait for the operation to complete.
186
184
187
185
> [!WARNING]
188
-
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Do not reuse a previously unregistered agent VM.
186
+
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM isn't supported. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Don't reuse a previously unregistered agent VM.
*-Force* is an optional parameter, suppressing the confirmation prompt.
200
198
201
199
> [!WARNING]
202
-
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent you should register a new, previously unregistered agent VM. Do not reuse a previously unregistered agent VM.
200
+
> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM isn't supported. If you need a new agent you should register a new, previously unregistered agent VM. Don't reuse a previously unregistered agent VM.
Copy file name to clipboardExpand all lines: articles/storage-mover/includes/protocol-endpoint-agent.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
@@ -2,7 +2,7 @@
2
2
author: stevenmatthew
3
3
ms.author: shaas
4
4
ms.topic: include
5
-
ms.date: 06/02/2024
5
+
ms.date: 05/29/2025
6
6
ms.service: azure-storage-mover
7
7
---
8
8
<!--
@@ -17,7 +17,8 @@ Handle file and content with care.
17
17
18
18
The current Azure Storage Mover release supports full-fidelity migrations for specific source-target pair combinations. Always utilize the latest agent version to benefit from these supported sources and destinations:
|SMB 2.x mount |Azure file share (SMB) |SMB 1.x sources and NFS Azure file shares are currently not supported. |
23
-
|NFS 3 & 4 mount |Azure blob storage container |Containers with the "Hierarchical Namespace Service (HNS)" feature enabled, are supported and the ADLS Gen2 REST API set is used for migration.|
|SMB 2.x mount |Azure blob storage container, Azure file share (SMB) | SMB 1.x sources and NFS Azure file shares are currently not supported. |
23
+
|SMB 2.x mount |Azure blob storage container | Containers with the Hierarchical Namespace Service (HNS) feature enabled are supported and the ADLS Gen2 REST API set is used for migration.|
24
+
|NFS 3 & 4 mount |Azure blob storage container | Containers with the Hierarchical Namespace Service (HNS) feature enabled are supported and the ADLS Gen2 REST API set is used for migration.|
# Azure Storage Mover scale and performance targets
27
27
28
-
The performance of a storage migration service is a key aspect for any migration. In this article, we share performance test results, though because Azure Storage Mover is a new service, your experience may vary.
28
+
The performance of a storage migration service is a key aspect for any migration. In this article, we share performance test results, though because Azure Storage Mover is a new service, your experience might vary.
29
29
30
30
## Scale targets
31
31
32
-
Azure Storage Mover is tested with 100 million namespace items (files and folders), migrated from a [supported source to a supported target](service-overview.md#supported-sources-and-targets) in Azure.
32
+
Azure Storage Mover is tested with 500 million namespace items (files and folders), migrated from a [supported source to a supported target](service-overview.md#supported-sources-and-targets) in Azure.
33
33
34
34
## How we test
35
35
@@ -51,11 +51,11 @@ The following table describes the characteristics of the test environments that
|Elapsed time | 16 Min, 42 Sec | 15 Min, 18 Sec | 5 hr, 28 Min |
125
125
|Items* per Second | - | 3548 | 2860 |
@@ -147,26 +147,26 @@ Different agent resource configurations are tested on NFS endpoints:
147
147
148
148
## Why migration performance varies
149
149
150
-
Fundamentally, network quality and the ability to process files, folders and their metadata impact your migration velocity.
150
+
Fundamentally, network quality and the ability to process files, folders, and their metadata affect your migration velocity.
151
151
152
152
Across the two core areas of network and compute, several aspects have an impact:
153
153
154
154
-**Migration scenario** <br />Copying into an empty target is faster as compared to a target with content. This behavior is due the migration engine evaluating not only the source, but also the target to make copy decisions.
155
155
-**Namespace item count** <br />Migrating 1 GiB of small files takes more time than migrating 1 GiB of larger files.
156
156
-**Namespace shape** <br />A wide folder hierarchy lends itself to more parallel processing than a narrow or deep directory structure. The file to folder ratio also plays a roll.
157
-
-**Namespace churn** <br />How many files, folders, and metadata have changed between two copy runs from the same source to the same target.
157
+
-**Namespace churn** <br />How many files, folders, and metadata change between two copy runs from the same source to the same target.
158
158
-**Network**
159
159
- bandwidth and latency between source and migration agent
160
160
- bandwidth and latency between migration agent and the target in Azure
161
161
-**Migration agent resources** <br />The amount of memory (RAM), number of compute cores, and even the amount of available, local disk capacity on the migration agent can have a profound impact on the migration velocity. More compute resources help to optimize the utilization of the available bandwidth, especially when large amounts of smaller files need to be processed in a migration.
162
162
163
-
For example, a traditional migration requires a strategy to minimize downtime of the workload that depends on the storage that is to be migrated. Azure Storage Mover supports such a strategy. It's called convergent, n-pass migration.
163
+
For example, a traditional migration requires a strategy to minimize downtime of the workload that depends on the storage that is to be migrated. Azure Storage Mover supports this strategy, referred to as *convergent, n-pass migration*.
164
164
165
-
In this strategy, you copy from source to target several times. During these copy iterations, the source remains available for read and write to the workload. Just before the final copy iteration, you take the source offline. It's expected that the final copy finishes faster than say the first copy you've ever made and takes about as long as the one immediately preceding it. After the final copy, the workload is failed over to use the new target storage in Azure and available for use again.
165
+
In this strategy, you copy from source to target several times. During these copy iterations, the source remains available for read and write to the workload. Just before the final copy iteration, you take the source offline. The final copy is expected to finish faster than the first copy you make, and take about as long as the one immediately preceding it. After the final copy, the workload is failed over to use the new target storage in Azure and available for use again.
166
166
167
167
During the first copy from source to target, the target is likely empty and all the source content must travel to the target. As a result, the first copy is likely most constrained by the available network resources.
168
168
169
-
Towards the end of a migration, when you've copied the source to the target several times already, only a few files, folders, and metadata has changed since the last copy. In this last copy iteration, comparing each file in source and target to see if it needs to be updated, requires more compute resources and fewer network resources. Copy runs in this late stage of a migration are often more compute-constrained. Proper [resourcing of the Storage Mover agent](agent-deploy.md#recommended-compute-and-memory-resources) becomes increasingly important.
169
+
Towards the end of a migration, after you copy the source to the target several times already, only a few files, folders, and metadata are modified following the last copy. In this last copy iteration, comparing each file in source and target to see if it needs to be updated, requires more compute resources and fewer network resources. Copy runs in this late stage of a migration are often more compute-constrained. Proper [resourcing of the Storage Mover agent](agent-deploy.md#recommended-compute-and-memory-resources) becomes increasingly important.
0 commit comments