Migration software
AWS DataSync
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 AWS DataSync gets around, as covered in our playbooks.
Cloud-to-cloud migration
- Pick an object copy tool for the Azure to AWS directionTransfers block, page and append blobs from Azure Blob Storage to Amazon S3, without an agent in Enhanced mode, and copies object tags by default. Archive tier objects must be rehydrated first, the cold tier is not supported, and objects with more than 2 KB of metadata do not transfer to S3.
- AzCopy cannot write to Amazon S3, so it does not help with Azure to AWS or repatriation copies.Copies Azure Blob Storage into Amazon S3 with object tags. Rehydrate archive tier first; the cold tier and objects with over 2 KB of metadata are not supported.
How it handles key settings
From the settings checklists in our playbooks: what AWS DataSync carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Data transfer out (egress) | Lists transferring data in or out of Azure Blob Storage among the costs of a transfer. | Cloud-to-cloud migration |
| Object metadata and bucket names | Azure Blob to Amazon S3: copies object tags by default. Objects with tags or metadata over 2 KB, or over 5 TB in size, are not transferred, and copying tags fails on accounts with a hierarchical namespace. | Cloud-to-cloud migration |
| Storage tiers and archived objects | Reads hot and cool tier blobs. Archive tier blobs must be rehydrated (moved back to an online tier) first, and the cold tier is not supported. | Cloud-to-cloud migration |
| Top-up copies (delta passes) | Can optionally delete destination objects that are not in the source. How it detects changed objects: not stated on its Azure Blob location page: test it in your pilot. | Cloud-to-cloud 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.