Releases: Azure/azure-storage-azcopy
Releases · Azure/azure-storage-azcopy
AzCopy V10.1.1 Release
Bug fixes
- Fixed typo in local traverser (error handling in walk).
- Fixed memory alignment issue for atomic functions on 32 bit system.
AzCopy V10.1.0 GA Release
Version 10.1.0 (GA)
Breaking changes
- The
--block-size
parameter has been replaced by--block-size-mb
. The old parameter took a number of bytes; the
new one takes a number of Megabytes (MiB). - The following command line parameters have been renamed, for clarity
--output
is now--output-type
--md5-validation
is now called--check-md5
--s2s-source-change-validation
is now called--s2s-detect-source-changed
--s2s-invalid-metadata-handle
is is now called--s2s-handle-invalid-metadata
--quota
(in themake
command) is now called--quota-gb
. Note that the values were always in GB, the new name
simply clarifies that fact
New features
- AzCopy is now able to be configured to use older API versions. This enables (limited) support for Azure Stack.
- Listing command now shows file sizes.
Bug fixes
- AzCopy v10 now works correctly with ADLS Gen 2 folders that contain spaces in their names.
- When cancelling with CRTL-C, status of in-progress transfers is now correctly recorded.
- For security, the Service-to-Service (S2S) feature will only work if both the source and destination connections are
HTTPS. - Use of the
--overwrite
parameter is clarified in the in-application help. - Fixed incorrect behavior with setting file descriptor limits on platforms including OS X and BSD.
- On Linux and OS X, log files are now created with same file permissions as all other files created by AzCopy.
- ThirdPartyNotice.txt is updated.
- Load DLL in a more secure manner compatible with Go's sysdll registration.
- Fixed support for relative paths and shorthands.
- Fixed bug in pattern matching for blob download when recursive is off.
AzCopyV10.0.9 Preview Release
Version 10.0.9 (Release Candidate)
Breaking changes
- 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
- 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. - 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. - 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). - 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
- Fixed memory leak when downloading large files
- Fixed performance when downloading a single large file
- Fixed bug with "too many open files" on Linux
- Fixed memory leak when uploading sparse files (files with big blocks of zeros) to Page Blobs and
Azure Files. - 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.) - Fixed functionality and usabilty issues with
remove
command - Improved performance for short-duration jobs (e.g. those lasting less than a minute)
- Prevent unnecessary error message that sometimes appeared when cancelling a job
- Various improvements to the online help and error messages.
AzCopyV10.0.8 Preview Release
- Rewrote sync command to eliminate numerous bugs and improve usability (see wiki for details)
- Implemented various improvements to memory management
- Added MD5 validation support (available options: NoCheck, LogOnly, FailIfDifferent, FailIfDifferentOrMissing)
- Added last modified time checks for source to guarantee transfer integrity
- Formalized outputs in JSON and elevated the output flag to the root level
- Eliminated outputs to STDERR (for new version notifications), which were causing problems for certain CI systems
- Improved log format for Windows
- Optimized plan file sizes
- Improved command line parameter names as follows (to be consistent with naming pattern of other parameters):
- fromTo -> from-to
- blobType -> blob-type
- excludedBlobType -> excluded-blob-type
- outputRaw (in "list" command) -> output
- stdIn-enable (reserved for internal use) -> stdin-enable
AzCopyV10.0.7 Preview Release
- Fixed error detection when flushing and closing files at download time
AzCopyV10.0.6 Preview Release
- Refactor uploads for DRY and performance
- Sort jobs according to their start time
- Fix the internal integration with client_id for OAuth
AzCopyV10.0.5 Preview Release
- Optimized the memory usage through un-mapping unused memory correctly.
- Optimized the OAuth support for better user experience.
- Fixed the issue that data integrity could be influenced when uploading local file to Azure File.
- Fixed various bugs for ADLS Gen2.
- Refactored download code to not use memory-mapped file.
AzCopyV10.0.4 Preview Release
- Various bug fixes
- Improved
sync
command's performance - Added
env
command to show possible configurations (environment variables) - Improved content-type detection
AzCopyV10.0.3 Preview Release
- Various bug fixes
- Fixed CPU high usage issue
AzCopyV10.0.2 Preview Release
- Various bug fixes
- Added support for using OAuth to access Storage resources