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
description: Learn about migrations to Azure file shares and find your migration guide.
4
4
author: fauhse
5
5
ms.service: storage
6
-
ms.topic: migration
7
-
ms.date: 2/27/2020
6
+
ms.topic: conceptual
7
+
ms.date: 3/18/2020
8
8
ms.author: fauhse
9
9
ms.subservice: files
10
10
---
@@ -23,20 +23,20 @@ The key in any migration is to capture all the applicable file fidelity when mig
23
23
1.**Data stream**: The data stream of a file stores the file content.
24
24
2.**File metadata**: The file meta data has several sub components:
25
25
* file attributes: read-only, for instance
26
-
* file permissions: generally referred to as *NTFS permissions* or *file and folder ACLs*
27
-
* timestamps: most notably the create and last modified timestamps
28
-
* alternative data stream: this is a space to store larger amounts of non-standard properties
26
+
* file permissions: referred to as *NTFS permissions* or *file and folder ACLs*
27
+
* timestamps: most notably the *create* and *last modified* timestamps
28
+
* alternative data stream: a space to store larger amounts of non-standard properties
29
29
30
30
File fidelity, in a migration, can therefore be defined as the ability to store all applicable file information on the source, the ability to transfer them with the migration tool and the ability to store them on the target storage of the migration.
31
31
32
32
The complexity in any file migration project is to match a storage target to your source and use a fidelity preserving copy tool to get your files there.
33
33
34
-
In that context, it becomes clear what the target storage for general purpose files in Azure are: **[Azure file shares]**. Compared to object storage in Azure blobs, file metadata can be natively stored on files in an Azure file share.
34
+
In that context, it becomes clear what the target storage for general purpose files in Azure is: **[Azure file shares]**. Compared to object storage in Azure blobs, file metadata can be natively stored on files in an Azure file share.
35
35
The one aspect of files that cannot be stored in a file share at this time, is the alternative data stream.
36
36
37
37
**[Learn more about file fidelity in Azure file shares]**
38
38
39
-
Azure file shares also preserve the file and folder hierarchy. Additionally, they not only allow for NTFS permissions to be stored, but also allowing your AD users (or AAD DS users) to natively access an Azure file share. They use their current identity and get access based on share permissions as well as file and folder ACLs. This is the same as when users connect to an on-premises file share.
39
+
Azure file shares also preserve the file and folder hierarchy. Additionally, they not only allow for NTFS permissions to be stored, but also allowing your AD users (or AAD DS users) to natively access an Azure file share. They use their current identity and get access based on share permissions as well as file and folder ACLs. A behavior not unlike when users connect to an on-premises file share.
40
40
41
41
***[Learn more about AD authentication for Azure file shares]**
42
42
***[Learn more about Azure Active Directory Domain Services (AAD DS) authentication for Azure file shares]**
@@ -52,7 +52,7 @@ Navigate it by:
52
52
53
53
A scenario without a link does not yet have a published migration guide. Check this table occasionally. New guides are frequently added.
| Windows Server 2012 R2 and newer | <ul><li>Azure File Sync</li><li>Azure File Sync + DataBox</li><li>Storage Migration Service + Azure File Sync</li></ul> | <ul><li>Azure File Sync</li><li>Azure File Sync + DataBox</li><li>Storage Migration Service + Azure File Sync</li><li>RoboCopy</li></ul> |
58
58
| Windows Server 2012 and older | <ul><li>Azure File Sync + DataBox</li><li>Storage Migration Service + Azure File Sync</li></ul> | <ul><li>Storage Migration Service + Azure File Sync</li><li>RoboCopy</li></ul> |
@@ -68,17 +68,17 @@ A scenario without a link does not yet have a published migration guide. Check t
68
68
69
69
There are several Microsoft and non-Microsoft file copy tools available. In order to choose the right tool for a migration scenario, there are three fundamental questions one must consider:
70
70
71
-
1. Does the copy tool support the source and the target location for a given file copy? This is a very obvious requirement but it is worth looking a layer deeper: Does it support your network path and/or available protocols (for instance REST/SMB/NFS) to and from the source and target storage locations?
71
+
1. Does the copy tool support the source and the target location for a given file copy? While this appears to be an obvious requirement, it is worth looking a layer deeper: Does it support your network path and/or available protocols (for instance REST/SMB/NFS) to and from the source and target storage locations?
72
72
2. Does the copy tool preserve the necessary file fidelity that is supported by the source/target location? In some cases, your target storage does not support the same fidelity as your source. You have already made the decision that the target storage is sufficient for your needs, hence the copy tool only needs to match the targets file fidelity capabilities.
73
-
3. Does the copy tool have features that make it fit into my migration strategy? For instance, consider if it has options that allow you to minimize your downtime. A good questions to ask is: Can I run this copy multiple times on the same, by users actively accessed location? If so, you can reduce the amount of downtime significantly. Compare that to a situation where you can only start the copy when the source stops changing, in order to guarantee a complete copy.
73
+
3. Does the copy tool have features that make it fit into my migration strategy? For instance, consider if it has options that allow you to minimize your downtime. A good question to ask is: Can I run this copy multiple times on the same, by users actively accessed location? If so, you can reduce the amount of downtime significantly. Compare that to a situation where you can only start the copy when the source stops changing, in order to guarantee a complete copy.
74
74
75
75
The following table classifies Microsoft tools and their current suitability for Azure file shares:
|| RoboCopy | Supported. Azure file shares can be mounted as network drives. | Full fidelity*|
80
80
|| Azure File Sync | Natively integrated into Azure file shares. | Full fidelity*|
81
-
|| Storage Migration Service (SMS) | Indirectly supported. Azure file shares can be mounted as network drives on a SMS target server. | Full fidelity*|
81
+
|| Storage Migration Service (SMS) | Indirectly supported. Azure file shares can be mounted as network drives on an SMS target server. | Full fidelity*|
82
82
|| Azure DataBox | Supported. | Does not copy metadata. [Can be used in combination with Azure File Sync](storage-sync-offline-data-transfer.md). |
83
83
|| AzCopy | Supported. | Does not copy metadata. |
84
84
|| Azure Storage Explorer | Supported. | Does not copy metadata. |
@@ -94,4 +94,4 @@ This category lists tools that help with planning and executing migrations.
94
94
* TreeSize, from JAM Software GmbH
95
95
96
96
Azure File Sync primarily scales with the number of items (files and folders) in a sync scope and less so with the total TiB amount. The tool below can be used to determine the number of files and folders on your Windows Server volumes. Furthermore it can be used to create a perspective before an [Azure File Sync deployment](storage-sync-files-deployment-guide.md) - but also after, when cloud tiering is engaged and you like to see not only the number of items but also in which directories your server cache is used the most.
97
-
This tool (tested version 4.4.1) is compatible with cloud tiered files. It will not cause recall of tiered files during it's normal operation.
97
+
This tool (tested version 4.4.1) is compatible with cloud tiered files. It will not cause recall of tiered files during its normal operation.
0 commit comments