You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Azure Storage Data Movement library is a cross-platform open source library that is designed for high performance uploading, downloading, and copying of blobs and files. The Data Movement library provides convenient methods that aren't available in the Azure Storage client library for .NET. These methods allow you to set the number of parallel operations, track transfer progress, resume a canceled transfer, and more.
20
20
21
-
The Data Movement library is only available for .NET, and only supports Azure Blob Storage and Azure Files.
21
+
The Data Movement library is only available for .NET, and only supports Azure Blob Storage and Azure Files. You should consider these limitations and other [known issues](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.DataMovement/KnownIssues.md#known-issues) when deciding whether to use the Data Movement library.
22
+
23
+
If you're migrating code from the older **Microsoft.Azure.Storage.DataMovement** library (version 2.X.X) to the current **Azure.Storage.DataMovement** library (version 12.X.X), see the [Migration guide](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.DataMovement/MigrationGuide.md#migration-guide-from-microsoftazurestoragedatamovement-to-azurestoragedatamovement).
@@ -34,7 +36,7 @@ If you don't have an existing project, this section shows you how to set up a pr
34
36
35
37
#### Install packages
36
38
37
-
From your project directory, install packages for the Azure Storage Data Movement client library and the Azure Identity client library using the `dotnet add package` command. The Azure.Identity package is needed for passwordless connections to Azure services.
39
+
From your project directory, install packages for the Azure Storage Data Movement client library and the Azure Identity client library using the `dotnet add package` command. The **Azure.Identity** package is needed for passwordless connections to Azure services.
38
40
39
41
```dotnetcli
40
42
dotnet add package Azure.Storage.DataMovement
@@ -243,7 +245,7 @@ To resume a transfer, call the following method:
Provide the transfer ID of the transfer that you want to resume. The transfer ID is a unique identifier for the transfer that's returned as part of the `TransferOperation` object when the transfer is started. If you don't know the transfer ID value, you can call [TransferManager.GetTransfersAsync](/dotnet/api/azure.storage.datamovement.transfermanager.gettransfersasync) to find the transfer and it's corresponding ID.
248
+
Provide the transfer ID of the transfer that you want to resume. The transfer ID is a unique identifier for the transfer that's returned as part of the `TransferOperation` object when the transfer is started. If you don't know the transfer ID value, you can call [TransferManager.GetTransfersAsync](/dotnet/api/azure.storage.datamovement.transfermanager.gettransfersasync) to find the transfer and its corresponding ID.
247
249
248
250
The following code example shows how to resume a transfer:
249
251
@@ -279,7 +281,7 @@ The `TransferStatus` property returns a [TransferStatus](/dotnet/api/azure.stora
279
281
280
282
| Property | Type | Description |
281
283
| --- | --- | --- |
282
-
|`HasCompletedSuccessfully`| Boolean | Represents if the transfer has completed successfully without any failure or skipped items. |
284
+
|`HasCompletedSuccessfully`| Boolean | Represents if the transfer completes successfully without any failure or skipped items. |
283
285
|`HasFailedItems`| Boolean | Represents if transfer has any failure items. If set to `true`, the transfer has at least one failure item. If set to `false`, the transfer currently has no failures. |
284
286
|`HasSkippedItems`| Boolean | Represents if transfer has any skipped items. If set to `true`, the transfer has at least one skipped item. If set to `false`, the transfer currently has no skipped items. It's possible to never have any items skipped if `SkipIfExists` isn't enabled in [TransferOptions.CreationPreference](/dotnet/api/azure.storage.datamovement.transferoptions.creationpreference). |
285
287
|`State`|[TransferState](/dotnet/api/azure.storage.datamovement.transferstate)| Defines the types of the state a transfer can have. See [TransferState](/dotnet/api/azure.storage.datamovement.transferstate) for details. |
@@ -329,18 +331,18 @@ BlobServiceClient client = new BlobServiceClient(
0 commit comments