-
Notifications
You must be signed in to change notification settings - Fork 222
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1472 from Azure/dev
Release 10.11
- Loading branch information
Showing
52 changed files
with
1,798 additions
and
336 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
# AzCopy v10 | ||
|
||
AzCopy v10 is a command-line utility that you can use to copy data to and from containers and file shares in Azure Storage accounts. AzCopy V10 presents easy-to-use commands that are optimized for performance. | ||
AzCopy v10 is a command-line utility that you can use to copy data to and from containers and file shares in Azure Storage accounts. | ||
AzCopy V10 presents easy-to-use commands that are optimized for high performance and throughput. | ||
|
||
## Features and capabilities | ||
|
||
|
@@ -12,33 +13,93 @@ AzCopy v10 is a command-line utility that you can use to copy data to and from c | |
|
||
:white_check_mark: Download files and directories. | ||
|
||
:white_check_mark: Copy containers, directories and blobs between storage accounts (Blobs only). | ||
:white_check_mark: Copy containers, directories and blobs between storage accounts (Service to Service). | ||
|
||
:white_check_mark: Synchronize containers with local file systems and visa versa (Blobs only). | ||
:white_check_mark: Synchronize data between Local <=> Blob Storage, Blob Storage <=> File Storage, and Local <=> File Storage. | ||
|
||
:white_check_mark: Copy objects, directories, and buckets from Amazon Web Services (AWS) (Blobs only). | ||
:white_check_mark: Delete blobs or files from an Azure storage account | ||
|
||
:white_check_mark: List files in a container (Blobs only). | ||
:white_check_mark: Copy objects, directories, and buckets from Amazon Web Services (AWS) to Azure Blob Storage (Blobs only). | ||
|
||
:white_check_mark: Remove files from a container (Blobs only). | ||
:white_check_mark: Copy objects, directories, and buckets from Google Cloud Platform (GCP) to Azure Blob Storage (Blobs only). | ||
|
||
:white_check_mark: List files in a container. | ||
|
||
:white_check_mark: Recover from failures by restarting previous jobs. | ||
|
||
## Download AzCopy | ||
The latest binary for AzCopy along with installation instructions may be found | ||
[here](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10). | ||
|
||
## Find help | ||
|
||
For complete guidance, visit any of these articles on the docs.microsoft.com website. | ||
|
||
:eight_spoked_asterisk: [Get started with AzCopy (download links here)](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10) | ||
|
||
:eight_spoked_asterisk: [Transfer data with AzCopy and blob storage](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-blobs) | ||
:eight_spoked_asterisk: [Upload files to Azure Blob storage by using AzCopy](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-upload) | ||
|
||
:eight_spoked_asterisk: [Download blobs from Azure Blob storage by using AzCopy](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-download) | ||
|
||
:eight_spoked_asterisk: [Copy blobs between Azure storage accounts by using AzCopy](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-copy) | ||
|
||
:eight_spoked_asterisk: [Synchronize between Local File System/Azure Blob Storage (Gen1)/Azure File Storage by using AzCopy](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize) | ||
|
||
:eight_spoked_asterisk: [Transfer data with AzCopy and file storage](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files) | ||
|
||
:eight_spoked_asterisk: [Transfer data with AzCopy and file storage](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-files) | ||
:eight_spoked_asterisk: [Transfer data with AzCopy and Amazon S3 buckets](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-s3) | ||
|
||
:eight_spoked_asterisk: [Transfer data with AzCopy and Amazon S3 buckets](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-s3) | ||
:eight_spoked_asterisk: [Transfer data with AzCopy and Google GCP buckets](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-google-cloud) | ||
|
||
:eight_spoked_asterisk: [Use data transfer tools in Azure Stack Hub Storage](https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-storage-transfer) | ||
|
||
:eight_spoked_asterisk: [Configure, optimize, and troubleshoot AzCopy](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-configure) | ||
|
||
### Find help from your command prompt | ||
:eight_spoked_asterisk: [AzCopy WiKi](https://github.com/Azure/azure-storage-azcopy/wiki) | ||
|
||
## Supported Operations | ||
|
||
The general format of the AzCopy commands is: `azcopy [command] [arguments] --[flag-name]=[flag-value]` | ||
|
||
* `bench` - Runs a performance benchmark by uploading or downloading test data to or from a specified destination | ||
|
||
* `copy` - Copies source data to a destination location. The supported directions are: | ||
- Local File System <-> Azure Blob (SAS or OAuth authentication) | ||
- Local File System <-> Azure Files (Share/directory SAS authentication) | ||
- Local File System <-> Azure Data Lake Storage (ADLS Gen2) (SAS, OAuth, or SharedKey authentication) | ||
- Azure Blob (SAS or public) -> Azure Blob (SAS or OAuth authentication) | ||
- Azure Blob (SAS or public) -> Azure Files (SAS) | ||
- Azure Files (SAS) -> Azure Files (SAS) | ||
- Azure Files (SAS) -> Azure Blob (SAS or OAuth authentication) | ||
- AWS S3 (Access Key) -> Azure Block Blob (SAS or OAuth authentication) | ||
- Google Cloud Storage (Service Account Key) -> Azure Block Blob (SAS or OAuth authentication) [Preview] | ||
|
||
* `sync` - Replicate source to the destination location. The supported directions are: | ||
- Local File System <-> Azure Blob (SAS or OAuth authentication) | ||
- Local File System <-> Azure Files (Share/directory SAS authentication) | ||
- Azure Blob (SAS or public) -> Azure Files (SAS) | ||
|
||
* `login` - Log in to Azure Active Directory (AD) to access Azure Storage resources. | ||
|
||
* `logout` - Log out to terminate access to Azure Storage resources. | ||
|
||
* `list` - List the entities in a given resource | ||
|
||
* `doc` - Generates documentation for the tool in Markdown format | ||
|
||
* `env` - Shows the environment variables that you can use to configure the behavior of AzCopy. | ||
|
||
* `help` - Help about any command | ||
|
||
* `jobs` - Sub-commands related to managing jobs | ||
|
||
* `load` - Sub-commands related to transferring data in specific formats | ||
|
||
* `make` - Create a container or file share. | ||
|
||
* `remove` - Delete blobs or files from an Azure storage account | ||
|
||
## Find help from your command prompt | ||
|
||
For convenience, consider adding the AzCopy directory location to your system path for ease of use. That way you can type `azcopy` from any directory on your system. | ||
|
||
|
@@ -54,22 +115,30 @@ If you choose not to add AzCopy to your path, you'll have to change directories | |
|
||
### What is the difference between `sync` and `copy`? | ||
|
||
The `copy` command is a simple transferring operation, it scans the source and attempts to transfer every single file/blob. The supported source/destination pairs are listed in the help message of the tool. On the other hand, `sync` makes sure that whatever is present in the source will be replicated to the destination. If your goal is to simply move some files, then `copy` is definitely the right command, since it offers much better performance. | ||
* The `copy` command is a simple transferring operation. It scans/enumerates the source and attempts to transfer every single file/blob present on the source to the destination. | ||
The supported source/destination pairs are listed in the help message of the tool. | ||
|
||
* On the other hand, `sync` scans/enumerates both the source, and the destination to find the incremental change. | ||
It makes sure that whatever is present in the source will be replicated to the destination. For `sync`, | ||
|
||
For `sync`, last modified times are used to determine whether to transfer the same file present at both the source and the destination. If the use case is to incrementally transfer data | ||
then `sync` is the better choice, since only the modified/missing files are transferred. | ||
* If your goal is to simply move some files, then `copy` is definitely the right command, since it offers much better performance. | ||
If the use case is to incrementally transfer data (files present only on source) then `sync` is the better choice, since only the modified/missing files will be transferred. | ||
Since `sync` enumerates both source and destination to find the incremental change, it is relatively slower as compared to `copy` | ||
|
||
### Will `copy` overwrite my files? | ||
|
||
By default, AzCopy will overwrite the files at the destination if they already exist. To avoid this behavior, please use the flag `--overwrite=false`. | ||
|
||
### Will 'sync' delete files in the destination if they no longer exist in the source location? | ||
### Will `sync` overwrite my files? | ||
|
||
By default, the 'sync' command doesn't delete files in the destination unless you use an optional flag with the command. To learn more, see [Synchronize files](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-blobs#synchronize-files). | ||
By default, AzCopy `sync` use last-modified-time to determine whether to transfer the same file present at both the source, and the destination. | ||
i.e, If the source file is newer compared to the destination file, we overwrite the destination | ||
You can change this default behaviour and overwrite files at the destination by using the flag `--mirror-mode=true` | ||
|
||
## Download AzCopy | ||
The latest binary install for AzCopy along with installation instructions may be found | ||
[here](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10). | ||
### Will 'sync' delete files in the destination if they no longer exist in the source location? | ||
|
||
By default, the 'sync' command doesn't delete files in the destination unless you use an optional flag with the command. | ||
To learn more, see [Synchronize files](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize). | ||
|
||
## How to contribute to AzCopy v10 | ||
|
||
|
@@ -83,4 +152,4 @@ provided by the bot. You will only need to do this once across all repos using o | |
|
||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). | ||
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or | ||
contact [[email protected]](mailto:[email protected]) with any additional questions or comments. | ||
contact [[email protected]](mailto:[email protected]) with any additional questions or comments. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.