Azure/azure-storage-azcopy v10.0.9

AzCopyV10.0.9 Preview Release

on GitHub

Version 10.0.9 (Release Candidate)

Breaking changes

1. For creating MD5 hashes when uploading, version 10.x now has the OPPOSITE default to version
   AzCopy 8.x. Specifically, as of version 10.0.9, MD5 hashes are NOT created by default. To create
   Content-MD5 hashs when uploading, you must now specify --put-md5 on the command line.

New features

1. Can migrate data directly from Amazon Web Services (AWS). In this high-performance data path
   the data is read directly from AWS by the Azure Storage service. It does not need to pass through
   the machine running AzCopy. The copy happens syncronously, so you can see its exact progress.
2. Can migrate data directly from Azure Files or Azure Blobs (any blob type) to Azure Blobs (any
   blob type). In this high-performance data path the data is read directly from the source by the
   Azure Storage service. It does not need to pass through the machine running AzCopy. The copy
   happens syncronously, so you can see its exact progress.
3. Sync command prompts with 4 options about deleting unneeded files from the target: Yes, No, All or
   None. (Deletion only happens if the --delete-destination flag is specified).
4. Can download to /dev/null. This throws the data away - but is useful for testing raw network
   performance unconstrained by disk; and also for validing MD5 hashes in bulk (when run in a cloud
   VM in the same region as the Storage account)

Bug fixes

1. Fixed memory leak when downloading large files
2. Fixed performance when downloading a single large file
3. Fixed bug with "too many open files" on Linux
4. Fixed memory leak when uploading sparse files (files with big blocks of zeros) to Page Blobs and
   Azure Files.
5. Fixed issue where application crashed after being throttled by Azure Storage Service. (The
   primary fix here is for Page Blobs, but a secondary part of the fix also helps with Block Blobs.)
6. Fixed functionality and usabilty issues with remove command
7. Improved performance for short-duration jobs (e.g. those lasting less than a minute)
8. Prevent unnecessary error message that sometimes appeared when cancelling a job
9. Various improvements to the online help and error messages.