Migration software
Azure Storage Mover
Suggested in one 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 it handles
The limits of the built-in tools that Azure Storage Mover gets around, as covered in our playbooks.
Azure migration
- Use a full-fidelity tool for file sharesSMB 2 and 3 and NFS sources to Azure Files with ACLs, timestamps and attributes; re-runs move only changes, or only new metadata.
- Azure File Sync needs a Windows server with NTFSCopies SMB 2 and 3 mounts to SMB Azure file shares and NFS 3 and 4 mounts to NFS Azure file shares. SMB 1 sources are not supported.
- Plan for a slow link with offline transferDetects differences after a Data Box transfer and uploads only new and changed files.
- AzCopy may lose some file fidelity because it uses the Azure Files REST API, and handles up to 10 million files per job.Full-fidelity SMB copies with ACLs, timestamps and attributes; re-runs copy only changes.
How it handles key settings
From the settings checklists in our playbooks: what Azure Storage Mover carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| File permissions, timestamps and attributes | Keeps folder structure, timestamps, ACLs and attributes for SMB shares, and re-runs copy only what changed. | Azure migration |
| Keep a local file server or not | Copies straight from NAS or Linux SMB 2 and 3 shares, and NFS 3 and 4 shares, to Azure Files when there is no Windows server to run Azure File Sync. | Azure migration |
Tools for the same jobs
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.