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
# Use the Azure Import/Export service to export data from Azure Blob storage
13
+
# Tutorial: Export data from Azure Blob storage with Azure Import/Export
14
14
15
15
This article provides step-by-step instructions on how to use the Azure Import/Export service to securely export large amounts of data from Azure Blob storage. The service requires you to ship empty drives to the Azure datacenter. The service exports data from your storage account to the drives and then ships the drives back.
16
16
17
+
In this tutorial, you learn how to:
18
+
19
+
> [!div class="checklist"]
20
+
> * Prerequisites to export data from Azure Blob storage with Azure Import/Export
21
+
> * Step 1: Create an export job
22
+
> * Step 2: Ship the drives
23
+
> * Step 3: Update the job with tracking information
24
+
> * Step 4: Receive the disks
25
+
> * Step 5: Unlock the disks
26
+
17
27
## Prerequisites
18
28
19
29
Before you create an export job to transfer data out of Azure Blob Storage, carefully review and complete the following list of prerequisites for this service.
20
30
You must:
21
31
22
32
- Have an active Azure subscription that can be used for the Import/Export service.
23
33
- Have at least one Azure Storage account. See the list of [Supported storage accounts and storage types for Import/Export service](storage-import-export-requirements.md). For information on creating a new storage account, see [How to Create a Storage Account](../storage/common/storage-account-create.md).
24
-
- Have adequate number of disks of [Supported types](storage-import-export-requirements.md#supported-disks).
34
+
- Have adequate number of disks of [Supported types](storage-import-export-requirements.md#supported-disks). You can use the Azure Import/Export tool to determine how many disks to provide. For steps, see [Determine drives to use](storage-import-export-determine-drives-for-export.md#determine-how-many-drives-you-need).
25
35
- Have a FedEx/DHL account. If you want to use a carrier other than FedEx/DHL, contact Azure Data Box Operations team at `[email protected]`.
26
36
- The account must be valid, should have balance, and must have return shipping capabilities.
27
37
- Generate a tracking number for the export job.
@@ -77,7 +87,7 @@ Perform the following steps to create an export job in the Azure portal.
77
87
|Option|Description|
78
88
|------|-----------|
79
89
|**Add containers**|Export all blobs in a container.<br>Select **Add containers**, and enter each container name.|
80
-
|**Add blobs**|Specify individual blobs to export.<br>Select **Add blobs**. Then specify the relative path to the blob, beginning with the container name. Use *$root* to specify the root container.<br>You must provide the blob paths in valid format to avoid errors during processing, as shown in this screenshot. For more information, see [Examples of valid blob paths](#examples-of-valid-blob-paths).|
90
+
|**Add blobs**|Specify individual blobs to export.<br>Select **Add blobs**. Then specify the relative path to the blob, beginning with the container name. Use *$root* to specify the root container.<br>You must provide the blob paths in valid format to avoid errors during processing, as shown in this screenshot. For more information, see [Examples of valid blob paths](storage-import-export-determine-drives-for-export.md#examples-of-valid-blob-paths).|
81
91
|**Add prefixes**|Use a prefix to select a set of similarly named containers or similarly named blobs in a container. The prefix may be the prefix of the container name, the complete container name, or a complete container name followed by the prefix of the blob name. |
82
92
83
93
@@ -121,61 +131,6 @@ Perform the following steps to create an export job in the Azure portal.
121
131
122
132
1. After validation passes, select **Create**.
123
133
124
-
<!--Replaced text: Steps 4 - end of "Create an export job." Wizard design changes required both screen and text updates.
125
-
126
-
4. In **Basics**:
127
-
128
-
- Select **Export from Azure**.
129
-
- Enter a descriptive name for the export job. Use the name you choose to track the progress of your jobs.
130
-
- The name may contain only lowercase letters, numbers, hyphens, and underscores.
131
-
- The name must start with a letter, and may not contain spaces.
- You can specify which containers and blobs to export.
147
-
- **To specify a blob to export**: Use the **Equal To** selector. Specify the relative path to the blob, beginning with the container name. Use *$root* to specify the root container.
148
-
- **To specify all blobs starting with a prefix**: Use the **Starts With** selector. Specify the prefix, beginning with a forward slash '/'. The prefix may be the prefix of the container name, the complete container name, or the complete container name followed by the prefix of the blob name. You must provide the blob paths in valid format to avoid errors during processing, as shown in this screenshot. For more information, see [Examples of valid blob paths](#examples-of-valid-blob-paths).
149
-
150
-
151
-
152
-
- You can export from the blob list file.
153
-
154
-
155
-
156
-
> [!NOTE]
157
-
> If the blob to be exported is in use during data copy, Azure Import/Export service takes a snapshot of the blob and copies the snapshot.
158
-
159
-
6. In **Return shipping info**:
160
-
161
-
- Select the carrier from the dropdown list. If you want to use a carrier other than FedEx/DHL, choose an existing option from the dropdown. Contact Azure Data Box Operations team at `[email protected]` with the information regarding the carrier you plan to use.
162
-
- Enter a valid carrier account number that you have created with that carrier. Microsoft uses this account to ship the drives back to you once your export job is complete.
163
-
- Provide a complete and valid contact name, phone, email, street address, city, zip, state/province, and country/region.
164
-
165
-
> [!TIP]
166
-
> Instead of specifying an email address for a single user, provide a group email. This ensures that you receive notifications even if an admin leaves.
167
-
168
-
7. In **Summary**:
169
-
170
-
- Review the details of the job.
171
-
- Make a note of the job name and provided Azure datacenter shipping address for shipping disks to Azure.
172
-
173
-
> [!NOTE]
174
-
> Always send the disks to the datacenter noted in the Azure portal. If the disks are shipped to the wrong datacenter, the job will not be processed.
175
-
176
-
- Click **OK** to complete export job creation.
177
-
-->
178
-
179
134
### [Azure CLI](#tab/azure-cli)
180
135
181
136
Use the following steps to create an export job in the Azure portal.
@@ -234,7 +189,7 @@ Use the following steps to create an export job in the Azure portal.
234
189
blob-path-prefix=/myiecontainer
235
190
```
236
191
237
-
For more information, see [Examples of valid blob paths](#examples-of-valid-blob-paths).
192
+
For more information, see [Examples of valid blob paths](storage-import-export-determine-drives-for-export.md#examples-of-valid-blob-paths).
238
193
239
194
> [!NOTE]
240
195
> If the blob to be exported is in use during data copy, Azure Import/Export service takes a snapshot of the blob and copies the snapshot.
If you do not know the number of drives you need, go to the [Check the number of drives](#check-the-number-of-drives). If you know the number of drives, proceed to ship the drives.
303
+
If you do not know the number of drives you need, see [Determine how many drives you need](storage-import-export-determine-drives-for-export.md#determine-how-many-drives-you-need). If you know the number of drives, proceed to ship the drives.
@@ -380,84 +333,7 @@ Here is an example of the sample input.
380
333
381
334
At this time, you can delete the job or leave it. Jobs automatically get deleted after 90 days.
382
335
383
-
## Check the number of drives
384
-
385
-
This *optional* step helps you determine the number of drives required for the export job. Perform this step on a Windows system running a [Supported OS version](storage-import-export-requirements.md#supported-operating-systems).
386
-
387
-
1.[Download the WAImportExport version 1](https://www.microsoft.com/download/details.aspx?id=42659) on the Windows system.
388
-
2. Unzip to the default folder `waimportexportv1`. For example, `C:\WaImportExportV1`.
389
-
3. Open a PowerShell or command-line window with administrative privileges. To change directory to the unzipped folder, run the following command:
390
-
391
-
`cd C:\WaImportExportV1`
392
-
393
-
4. To check the number of disks required for the selected blobs, run the following command:
394
-
395
-
`WAImportExport.exe PreviewExport /ExportBlobListFile:<Path to XML blob list file> /DriveSize:<Size of drives used>`
396
-
397
-
The parameters are described in the following table:
398
-
399
-
|Command-line parameter|Description|
400
-
|--------------------------|-----------------|
401
-
|**/logdir:**|Optional. The log directory. Verbose log files are written to this directory. If not specified, the current directory is used as the log directory.|
402
-
|**/ExportBlobListFile:**|Required. Path to the XML file containing list of blob paths or blob path prefixes for the blobs to be exported. The file format used in the `BlobListBlobPath` element in the [Put Job](/rest/api/storageimportexport/jobs) operation of the Import/Export service REST API.|
403
-
|**/DriveSize:**|Required. The size of drives to use for an export job, *for example*, 500 GB, 1.5 TB.|
404
-
405
-
See an [Example of the PreviewExport command](#example-of-previewexport-command).
406
-
407
-
5. Check that you can read/write to the drives that will be shipped for the export job.
408
-
409
-
### Example of PreviewExport command
410
-
411
-
The following example demonstrates the `PreviewExport` command:
The export blob list file may contain blob names and blob prefixes, as shown here:
418
-
419
-
```xml
420
-
<?xml version="1.0" encoding="utf-8"?>
421
-
<BlobList>
422
-
<BlobPath>pictures/animals/koala.jpg</BlobPath>
423
-
<BlobPathPrefix>/vhds/</BlobPathPrefix>
424
-
<BlobPathPrefix>/movies/</BlobPathPrefix>
425
-
</BlobList>
426
-
```
427
-
428
-
The Azure Import/Export Tool lists all blobs to be exported and calculates how to pack them into drives of the specified size, taking into account any necessary overhead, then estimates the number of drives needed to hold the blobs and drive usage information.
429
-
430
-
Here is an example of the output, with informational logs omitted:
431
-
432
-
```powershell
433
-
Number of unique blob paths/prefixes: 3
434
-
Number of duplicate blob paths/prefixes: 0
435
-
Number of nonexistent blob paths/prefixes: 1
436
-
437
-
Drive size: 500.00 GB
438
-
Number of blobs that can be exported: 6
439
-
Number of blobs that cannot be exported: 2
440
-
Number of drives needed: 3
441
-
Drive #1: blobs = 1, occupied space = 454.74 GB
442
-
Drive #2: blobs = 3, occupied space = 441.37 GB
443
-
Drive #3: blobs = 2, occupied space = 131.28 GB
444
-
```
445
-
446
-
## Examples of valid blob paths
447
-
448
-
The following table shows examples of valid blob paths:
449
-
450
-
| Selector | Blob Path | Description |
451
-
| --- | --- | --- |
452
-
| Starts With |/ |Exports all blobs in the storage account |
453
-
| Starts With |/$root/ |Exports all blobs in the root container |
454
-
| Starts With |/book |Exports all blobs in any container that begins with prefix **book**|
455
-
| Starts With |/music/ |Exports all blobs in container **music**|
456
-
| Starts With |/music/love |Exports all blobs in container **music** that begin with prefix **love**|
457
-
| Equal To |$root/logo.bmp |Exports blob **logo.bmp** in the root container |
458
-
| Equal To |videos/story.mp4 |Exports blob **story.mp4** in container **videos**|
459
-
460
336
## Next steps
461
337
462
-
-[View the job and drive status](storage-import-export-view-drive-status.md)
0 commit comments