Migrate to Azure file shares
This article covers the basic aspects of a migration to Azure file shares and contains a table of migration guides. These guides help you move your files into Azure file shares. The guides are organized based on where your data is and what deployment model (cloud-only or hybrid) you're moving to.
Azure has multiple available types of cloud storage. A fundamental aspect of file migrations to Azure is determining which Azure storage option is right for your data.
Azure file shares are suitable for general-purpose file data. This data includes anything you use an on-premises SMB or NFS share for. With Azure File Sync, you can cache the contents of several Azure file shares on servers running Windows Server on-premises.
For an app that currently runs on an on-premises server, storing files in an Azure file share might be a good choice. You can move the app to Azure and use Azure file shares as shared storage. You can also consider Azure Disks for this scenario.
Some cloud apps don't depend on SMB or on machine-local data access or shared access. For those apps, object storage like Azure blobs is often the best choice.
The key in any migration is to capture all the applicable file fidelity when moving your files from their current storage location to Azure. How much fidelity the Azure storage option supports and how much your scenario requires also helps you pick the right Azure storage. General-purpose file data traditionally depends on file metadata. App data might not.
Here are the two basic components of a file:
- Data stream: The data stream of a file stores the file content.
- File metadata: The file metadata has these subcomponents:
- File attributes like read-only
- File permissions, which can be referred to as NTFS permissions or file and folder ACLs
- Timestamps, most notably the creation and last-modified timestamps
- An alternative data stream, which is a space to store larger amounts of nonstandard properties
File fidelity in a migration can be defined as the ability to:
- Store all applicable file information on the source.
- Transfer files with the migration tool.
- Store files in the target storage of the migration. Ultimately, the target for migration guides on this page is one or more Azure file shares. Consider this list of features that SMB Azure file shares don't support.
To ensure your migration proceeds smoothly, identify the best copy tool for your needs and match a storage target to your source.
Taking the previous information into account, you can see that the target storage for general-purpose files in Azure is Azure file shares.
Unlike object storage in Azure blobs, an Azure file share can natively store file metadata. Azure file shares also preserve the file and folder hierarchy, attributes, and permissions. NTFS permissions can be stored on files and folders because they're on-premises.
If you're migrating on-premises file servers to Azure File Sync, set the ACLs for the root directory of the file share before copying a large number of files, as changes to permissions for root ACLs can take up to a day to propagate if done after a large file migration.
A user of Active Directory, which is their on-premises domain controller, can natively access an Azure file share. So can a user of Azure Active Directory Domain Services (Azure AD DS). Each uses their current identity to get access based on share permissions and on file and folder ACLs. This behavior is similar to a user connecting to an on-premises file share.
The alternative data stream is the primary aspect of file fidelity that currently can't be stored on a file in an Azure file share. It's preserved on-premises when Azure File Sync is used.
The following table lists detailed migration guides.
How to use the table:
Locate the row for the source system your files are currently stored on.
Choose one of these targets:
- A hybrid deployment using Azure File Sync to cache the content of Azure file shares on-premises
- Azure file shares in the cloud
Select the target column that matches your choice.
Within the intersection of source and target, a table cell lists available migration scenarios. Select one to directly link to the detailed migration guide.
A scenario without a link doesn't yet have a published migration guide. Check this table occasionally for updates. New guides will be published when they're available.
|Source||Target: Hybrid deployment||Target: Cloud-only deployment|
|Tool combination:||Tool combination:|
|Windows Server 2012 R2 and later|
|Windows Server 2012 and earlier||
|Network-attached storage (NAS)|
|Linux / Samba|
There are several file-copy tools available from Microsoft and others. To select the right tool for your migration scenario, you must consider these fundamental questions:
Does the tool support the source and target locations for your file copy?
Does the tool support your network path or available protocols (such as REST, SMB, or NFS) between the source and target storage locations?
Does the tool preserve the necessary file fidelity supported by your source and target locations?
In some cases, your target storage doesn't support the same fidelity as your source. If the target storage is sufficient for your needs, the tool must match only the target's file-fidelity capabilities.
Does the tool have features that let it fit into your migration strategy?
For example, consider whether the tool lets you minimize your downtime.
When a tool supports an option to mirror a source to a target, you can often run it multiple times on the same source and target while the source stays accessible.
The first time you run the tool, it copies the bulk of the data. This initial run might last a while. It often lasts longer than you want for taking the data source offline for your business processes.
By mirroring a source to a target (as with robocopy /MIR), you can run the tool again on that same source and target. The run is much faster because it needs to transport only source changes that occur after the previous run. Rerunning a copy tool this way can reduce downtime significantly.
The following table classifies Microsoft tools and their current suitability for Azure file shares:
|Recommended||Tool||Support for Azure file shares||Preservation of file fidelity|
|RoboCopy||Supported. Azure file shares can be mounted as network drives.||Full fidelity.*|
|Azure File Sync||Natively integrated into Azure file shares.||Full fidelity.*|
|Azure File Migration Program||Supported.||Full fidelity.*|
|Storage Migration Service||Indirectly supported. Azure file shares can be mounted as network drives on SMS target servers.||Full fidelity.*|
|Data Box (including the data copy service to load files onto the device)||Supported. (Data Box Disks does not support large file shares)||Data Box and Data Box Heavy fully support metadata. Data Box Disks does not preserve file metadata.|
|AzCopy latest version||Supported but not fully recommended.||Doesn't support differential copies at scale, and some file fidelity might be lost. Learn how to use AzCopy with Azure file shares|
|Azure Storage Explorer latest version||Supported but not recommended.||Loses most file fidelity, like ACLs. Supports timestamps.|
|Azure Data Factory||Supported.||Doesn't copy metadata.|
* Full fidelity: meets or exceeds Azure file-share capabilities.
Migration helper tools
This section describes tools that help you plan and run migrations.
RoboCopy from Microsoft Corporation
RoboCopy is one of the tools most applicable to file migrations. It comes as part of Windows. The main RoboCopy documentation is a helpful resource for this tool's many options.
TreeSize from JAM Software GmbH
Azure File Sync scales primarily with the number of items (files and folders) and not with the total storage amount. The TreeSize tool lets you determine the number of items on your Windows Server volumes.
You can use the tool to create a perspective before an Azure File Sync deployment. You can also use it when cloud tiering is engaged after deployment. In that scenario, you see the number of items and which directories use your server cache the most.
The tested version of the tool is version 4.4.1. It's compatible with cloud-tiered files. The tool won't cause recall of tiered files during its normal operation.
- Create a plan for which deployment of Azure file shares (cloud-only or hybrid) you want.
- Review the list of available migration guides to find the detailed guide that matches your source and deployment of Azure file shares.
More information about the Azure Files technologies mentioned in this article: