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/storage-mover/endpoint-manage.md
+26-2Lines changed: 26 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,9 +74,18 @@ There are many use cases that require preserving metadata values such as file an
74
74
75
75
### NFS endpoints
76
76
77
-
Using the NFS protocol, you can transfer files between computers running Windows and other non-Windows operating systems, such as Linux or UNIX. The current Azure Storage Mover release supports migrations from NFS shares on a NAS or server device within your network to an Azure blob container only.
77
+
Using the NFS protocol, you can transfer files between computers running Windows and other non-Windows operating systems, such as Linux or UNIX. Azure Storage Mover release supports migrations from NFS shares on a NAS or server device within your network to an Azure blob container or Azure file shares.
78
78
79
-
Unlike SMB, NFS doesn't utilize the ACL concept or user-based authentication. This difference allows NFS endpoints to be accessed without Azure Key Vault integration. In addition, Storage Mover processes metadata differently for both NFS mount sources and their blob container target counterparts. The following table identifies outcomes for common metadata encountered during migration:
79
+
Unlike SMB, NFS doesn't utilize the ACL concept or user-based authentication. This difference allows NFS endpoints to be accessed without Azure Key Vault integration.
80
+
Any endpoint created programmatically requires you to make the following assignments manually:
@@ -89,6 +98,21 @@ Unlike SMB, NFS doesn't utilize the ACL concept or user-based authentication. Th
89
98
|Last accessed timestamp|This timestamp is preserved as custom blob metadata if it exists on the source file. There's no blob-native timestamp of this type.|
90
99
|Other metadata |Other metadata is persisted in a custom metadata field of the target blob if it exists on source items. Only 4 KiB of metadata can be stored. Metadata of a larger size isn't migrated.|
91
100
101
+
For NFS mount sources and Azure File share targets, the following table identifies outcomes for common metadata encountered during migration:
|Directory structure |The original directory structure of the source will be preserved on the target share.|
106
+
|Access permissions |Access mode, user and group permissions will be preserved from source file or directory on the target share.|
107
+
|Symbolic links |Symbolic links are skipped.|
108
+
|Hard links |Target file will be copied as regular file. Files on the source which are hard links will not be linked at the destination. The destination will receive full copies despite hard link status at the source.|
109
+
|Create timestamp |The original create timestamp of the source file will be preserved on the target share.|
110
+
|Change timestamp |Not preserved. NFS semantics treat ctime as a read-only attribute.|
111
+
|Modified timestamp |The original modified timestamp of the source file will be preserved on the target share. In some cases where directory information is updated before the files are updated, the “Modified timestamp” on directory will be reflected correctly after first sync and not during the initial copy.|
112
+
|Last accessed timestamp|Not preserved. This last access timestamp is neither supported for a file nor a directory on the target share.|
113
+
114
+
115
+
92
116
## Create an endpoint
93
117
94
118
Before you can create a job definition, you need to create endpoints for your source and target data sources.
| S3 (Preview) | Azure blob storage container | AWS S3 buckets with Glacier or Glacier Deep Archive storage classes cannot be migrated. |
23
-
| SMB 2.x & 3.x mount | Azure file share (SMB) | SMB 1.x sources and NFS Azure file shares are currently not supported. |
24
-
| SMB 2.x and 3.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. |
25
-
| 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. |
22
+
| S3 (Preview) | Azure Blob storage container | AWS (Amazon Web Services) S3 buckets with Glacier or Glacier Deep Archive storage classes can't be migrated. |
23
+
| SMB 2.x and 3.x mount | Azure file share (SMB) | SMB 1.x sources and NFS Azure file shares are currently not supported. |
24
+
| SMB 2.x and 3.x mount | Azure blob storage container | Containers with Flatnamespace (FNS) and Hierarchical Namespace Service (HNS) feature enabled are supported and the ADLS Gen2 REST API set is used for migration. |
25
+
| NFS 3 and 4 mount | Azure blob storage container | Containers with Flatnamespace (FNS) and Hierarchical Namespace Service (HNS) feature enabled are supported and the ADLS Gen2 REST API set is used for migration. |
26
+
| NFS 3 and 4 mount | Azure file share (NFS 4.1) ||
Copy file name to clipboardExpand all lines: articles/storage-mover/service-overview.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: stevenmatthew
5
5
6
6
ms.service: azure-storage-mover
7
7
ms.topic: overview
8
-
ms.date: 06/27/2025
8
+
ms.date: 10/17/2025
9
9
ms.author: shaas
10
10
---
11
11
@@ -27,10 +27,10 @@ Document score: 98 (808 words and 1 false positive)
27
27
28
28
:::row:::
29
29
:::column:::
30
-
[](https://youtu.be/bJL0JsRyP6c)
30
+
[](https://youtu.be/bJL0JsRyP6c)
31
31
:::column-end:::
32
32
:::column:::
33
-
Azure Storage Mover is a fully managed migration service that enables you to migrate your files and folders from on-prem or AWS S3 buckets to Azure Storage while minimizing downtime for your workload.
33
+
Azure Storage Mover is a fully managed migration service that enables you to migrate your files and folders from on-premises or AWS S3 buckets to Azure Storage while minimizing downtime for your workload.
34
34
:::column-end:::
35
35
:::row-end:::
36
36
@@ -46,8 +46,6 @@ When you migrate data from a source endpoint using the SMB protocol, Storage Mov
46
46
47
47
However, migrating data from a source endpoint using the NFS protocol might require "virtual" folders during the migration. Because Azure blob containers without HNS support don’t have a traditional file system, Storage Mover uses these folders to mimic a local file system. When files are found within folders on a source endpoint, Storage Mover prepends their paths to their names and places the file in a flat list within in the target blob container.
48
48
49
-
:::image type="content" source="media/overview/source-to-target.png" alt-text="A screenshot illustrating a source NFS share migrated through an Azure Storage Mover agent VM to an Azure Storage blob container." lightbox="media/overview/source-to-target-lrg.png" :::
50
-
51
49
## Fully managed migrations
52
50
53
51
You need only deploy one Storage Mover instance in your subscription to handle migrations from multiple source shares, even if they’re located in different parts of the world. The storage mover resource itself doesn't process your files and folders. Rather, you deploy a migration agent near your source share to send your data directly to the selected targets in Azure.
0 commit comments