Migration software
Azure File Sync
Suggested in 2 of our migration playbooks, mainly for Servers and cloud. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What does Azure File Sync handle?
The limits of the built-in tools that Azure File Sync gets around, as covered in our playbooks.
Azure migration
- Use a full-fidelity tool for file sharesSyncs a Windows file server to Azure Files in the background with permissions intact.
How does Azure File Sync handle key settings?
From the settings checklists in our playbooks: what Azure File Sync carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Folder permissions (ACLs) and owners | Microsoft lists it as full fidelity, natively integrated with Azure file shares. | NAS to Azure Files migration |
| Alternate data streams | Keeps alternate data streams on the on-premises Windows Server cache, not in the Azure file share. | NAS to Azure Files migration |
| Copy mode and deletes in the target | Robocopy fills the Azure File Sync server folder, which then syncs to Azure, so the Robocopy options decide deletes. | NAS to Azure Files migration |
| Network path and ports | Users reach a local Windows Server, so they do not need port 445 to Azure. | NAS to Azure Files migration |
Which tools do the same jobs as Azure File Sync?
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.