|
1 | 1 | --- |
2 | | -title: Review copy logs from imports and exports in Azure Import/Export | Microsoft Docs |
| 2 | +title: Use logs to troubleshoot imports and exports via Azure Import/Export | Microsoft Docs |
3 | 3 | description: Learn how to review error/copy logs from imports and exports for data copy, upload issues. |
4 | | -author: alkohli |
| 4 | +author: v-dalc |
5 | 5 | services: storage |
6 | 6 | ms.service: storage |
7 | 7 | ms.topic: how-to |
8 | | -ms.date: 10/01/2021 |
| 8 | +ms.date: 12/22/2021 |
9 | 9 | ms.author: alkohli |
10 | 10 | ms.subservice: common |
11 | 11 | --- |
12 | 12 |
|
13 | | -# Review copy logs from imports and exports via Azure Import/Export |
14 | | -When the Microsoft Azure Import/Export service processes the drives that are associated with an import or export job, it writes copy log files to the storage account you used to import or export blobs. |
| 13 | +# Use logs to troubleshoot imports and exports via Azure Import/Export |
15 | 14 |
|
16 | | -The log file contains detailed status about each file that was imported or exported. |
| 15 | +When the Microsoft Azure Import/Export service processes the drives for an import or export job, the service writes copy logs and verbose logs to the storage account that you used. Both logs are saved for each drive. |
17 | 16 |
|
18 | | -The service returns the URL for each copy log file when you query the status of a completed job. For more information, see [Get Job](/rest/api/storageimportexport/Jobs/Get). |
| 17 | +[!INCLUDE [storage-import-export-verbose-log-copy-log-descriptions.md](../../includes/storage-import-export-verbose-log-copy-log-descriptions.md)] |
19 | 18 |
|
20 | | -## Example URLs |
| 19 | +## Locate the logs |
21 | 20 |
|
22 | | -The following are example URLs for copy log files for an import job with two drives: |
| 21 | +When you use the Import/Export service to create an import or export job in Azure Data Box, you'll view the Import/Export job along with your other **Data Box** resources. |
23 | 22 |
|
24 | | - `http://myaccount.blob.core.windows.net/ImportExportStatesPath/waies/myjob_9WM35C2V_20130921-034307-902_error.xml` |
| 23 | +Use the following steps to find out the status of the data copies for an Import/Export job: |
25 | 24 |
|
26 | | - `http://myaccount.blob.core.windows.net/ImportExportStatesPath/waies/myjob_9WM45A6Q_20130921-042122-021_error.xml` |
| 25 | +[!INCLUDE [storage-import-export-view-jobs-and-drives.md](../../includes/storage-import-export-view-jobs-and-drives.md)] |
| 26 | + |
| 27 | +A copy log is saved automatically. If you chose to save verbose logs when you placed your order, you'll also see the path to the verbose log. |
| 28 | + |
| 29 | +The logs are uploaded to a container (for blob imports and exports) or share (for imports to Azure Files) in the storage account. The container is named `databoxcopylog`. The URLs have these formats: |
| 30 | + |
| 31 | +|Log type |URL format| |
| 32 | +|-----------|----------| |
| 33 | +|copy log |<*storage-account-name*>/databoxcopylog/<*order-name*>_<*device-serial-number*>_CopyLog_<*job-ID*>.xml | |
| 34 | +|verbose log|<*storage-account-name*>/databoxcopylog/<*order-name*>_<*device-serial-number*>_VerboseLog_<*job-ID*>.xml| |
| 35 | + |
| 36 | +For export jobs, a manifest file also is saved to the disk. |
| 37 | + |
| 38 | +Each data transfer for a disk generates a copy log. If you chose to save a verbose log when you created the order, there’s also a verbose log in the same folder. |
| 39 | + |
| 40 | +> [!NOTE] |
| 41 | +> For your earlier orders, you might find an error log (_error.xml) along with the verbose log in a `waies` container in the storage account. The `DriveLog Version`, shown in the error log summary, will be `2018-10-01`. The log formats differ from those described in this article. |
| 42 | +
|
| 43 | +## Review import logs |
| 44 | + |
| 45 | +During an import, the Import/Export service generates a verbose log and a copy log for each disk. |
| 46 | + |
| 47 | +### Verbose logs |
| 48 | + |
| 49 | +The verbose log is an optional file that you can enable during ordering. It's a simple listing of all files that were successfully imported from the drive. The verbose log gives the following information for each file. The verbose log doesn’t provide summary information. |
| 50 | + |
| 51 | +| Field | Description | |
| 52 | +|-------------|----------------------------------------------| |
| 53 | +| CloudFormat | BlockBlob, PageBlob, or AzureFile. | |
| 54 | +| Path | Path to the file within the storage account. | |
| 55 | +| Size | File or blob size. | |
| 56 | +| crc64 | The cyclic redundancy check 64 (CRC64) checksum that was used to verify data integrity during data transfer. | |
| 57 | + |
| 58 | +#### Sample verbose log: import |
| 59 | + |
| 60 | +[!INCLUDE [data-box-disk-sample-verbose-log.md](../../includes/data-box-disk-sample-verbose-log.md)] |
| 61 | + |
| 62 | +### Copy logs |
| 63 | + |
| 64 | +The copy log contains an error entry for each file that failed to import or export, with error detail. The copy log ends with a summary of validation and copy errors that occurred during the data transfer. |
| 65 | + |
| 66 | +Each error entry contains the following information. |
| 67 | + |
| 68 | +| Field | Description | |
| 69 | +|--------------|-----------------------------------------------------------| |
| 70 | +| Path | The destination share within the container or file share. | |
| 71 | +| Category | Identifies the error category. For more information, see [Data transfer errors](#data-transfer-errors). | |
| 72 | +| ErrorCode | The numeric code for the error. | |
| 73 | +| ErrorMessage | Describes the error. | |
| 74 | + |
| 75 | +The summary at the end of the log (look for `CopyLog Summary`) gives the following information: |
| 76 | + |
| 77 | +* Drive log version (in this case, `2021-08-01`) |
| 78 | +* Drive ID |
| 79 | +* Data copy status |
| 80 | +* Summary of validation errors by error category |
| 81 | +* Summary of copy errors by error category |
| 82 | + |
| 83 | +#### Sample copy log: import |
| 84 | + |
| 85 | +[!INCLUDE [data-box-disk-sample-copy-log.md](../../includes/data-box-disk-sample-copy-log.md)] |
| 86 | + |
| 87 | +## Review export logs |
| 88 | + |
| 89 | +During an export, the Import/Export service generates a verbose log and a copy log for each data transfer from Azure Storage to a disk. There's also a manifest file, which is saved to the disk. |
| 90 | + |
| 91 | +### Verbose log |
| 92 | + |
| 93 | +The verbose log for an export is a simple listing of all files that were successfully exported from the Azure storage account to the drive. The verbose log gives the following information for each file. The verbose log doesn’t provide summary information. |
| 94 | + |
| 95 | +| Field | Description | |
| 96 | +|-------------|----------------------------------------------| |
| 97 | +| CloudFormat | BlockBlob, PageBlob, or AzureFile. | |
| 98 | +| Etag | The entity tag (ETag) for the resource, which is used for concurrency checking during the data transfer. | |
| 99 | +| Path | Path to the file within the storage account. | |
| 100 | +| Size | File or blob size. | |
| 101 | +| crc64 | The cyclic redundancy check 64 (CRC64) checksum that was computed while exporting data to disk. | |
| 102 | + |
| 103 | + |
| 104 | +#### Sample verbose log: export |
| 105 | + |
| 106 | +In the following sample verbose log, the export job successfully transferred three blobs from Azure Blob storage. |
| 107 | + |
| 108 | +```xml |
| 109 | +<File CloudFormat="BlockBlob" ETag="0x8D804D87F976907" Path="export-blobs/movie/sc%3Aifi/block.blob" Size="4096" crc64="16033727819182370206"> |
| 110 | +</File><File CloudFormat="BlockBlob" ETag="0x8D804D889880CC6" Path="export-blobs/movie/sc#Aifi/block.blob" Size="4096" crc64="16033727819182370206"> |
| 111 | +</File><File CloudFormat="BlockBlob" ETag="0x8D804D8F1BC81C0" Path="export-blobs/@GMT-2001.03.30-14.44.00/block.blob" Size="4096" crc64="16033727819182370206"> |
| 112 | +</File> |
| 113 | +``` |
| 114 | + |
| 115 | +### Copy log |
| 116 | + |
| 117 | +The copy log for an export contains an error entry for each file that failed to transfer successfully from Azure Storage to the disk, with error detail. The copy log ends with a summary of validation and copy errors that occurred during the data transfer. |
| 118 | + |
| 119 | +The copy log for an export reports issues such as a data transfer that fail because of a damaged drive or a storage account key that changed during data transfer. For a list of issues, see [Data transfer errors](#data-transfer-errors). |
| 120 | + |
| 121 | +#### Sample copy log: export |
| 122 | + |
| 123 | +The following sample is a copy log for an export that came across three file system errors ( `UploadErrorWin32`) that caused the export of three files to fail. Error **267** indicates the directory name is invalid. Error **123** indicates an incorrect filename, directory name, or volume label syntax. |
| 124 | + |
| 125 | +```xml |
| 126 | +<ErroredEntity CloudFormat="BlockBlob" Path="export-ut-invaliddirblobpath/movie/sc:Aifi/block.blob"> |
| 127 | + <Category>UploadErrorWin32</Category> |
| 128 | + <ETag>0x8D804D8840B92C9</ETag> |
| 129 | + <ErrorCode>267</ErrorCode> |
| 130 | + <ErrorMessage>File Create failed</ErrorMessage> |
| 131 | + <Type>File</Type> |
| 132 | +</ErroredEntity><ErroredEntity CloudFormat="BlockBlob" Path="export-ut-invaliddirblobpath/movie/sc-Aifi/block.blob"> |
| 133 | + <Category>UploadErrorWin32</Category> |
| 134 | + <ETag>0x8D804D8AD026B2A</ETag> |
| 135 | + <ErrorCode>123</ErrorCode> |
| 136 | + <ErrorMessage>File Create failed</ErrorMessage> |
| 137 | + <Type>File</Type> |
| 138 | +</ErroredEntity><ErroredEntity CloudFormat="BlockBlob" Path="export-ut-invaliddirblobpath/movie/sc*Aifi/block.blob"> |
| 139 | + <Category>UploadErrorWin32</Category> |
| 140 | + <ETag>0x8D804D8A858F705</ETag> |
| 141 | + <ErrorCode>123</ErrorCode> |
| 142 | + <ErrorMessage>File Create failed</ErrorMessage> |
| 143 | + <Type>File</Type> |
| 144 | +</ErroredEntity><CopyLog Summary="Summary"> |
| 145 | + <DriveLogVersion>2021-08-01</DriveLogVersion> |
| 146 | + <DriveId>cb57dbe8-0b67-45e0-ad40-a08fb5305c60</DriveId> |
| 147 | + <Status>Failed</Status> |
| 148 | + <TotalFiles_Blobs>9</TotalFiles_Blobs> |
| 149 | + <FilesErrored>6</FilesErrored> |
| 150 | + <Summary> |
| 151 | + <ValidationErrors> |
| 152 | + <None Count="3" /> |
| 153 | + </ValidationErrors> |
| 154 | + <CopyErrors> |
| 155 | + <UploadErrorWin32 Count="3" Description="File Create failed because of UploadErrorWin32 exception" /> |
| 156 | + </CopyErrors> |
| 157 | + </Summary> |
| 158 | +</CopyLog> |
| 159 | +``` |
| 160 | + |
| 161 | + |
| 162 | +## Data transfer errors |
| 163 | + |
| 164 | +You'll find the following errors in the copy logs for import jobs and/or export jobs. |
| 165 | + |
| 166 | +| Error category | Error message | Imports | Exports | |
| 167 | +|-------------------------------------|-------------------|---------|---------| |
| 168 | +| `UploadErrorWin32` |File system error. | Yes | Yes | |
| 169 | +| `UploadErrorCloudHttp` |Unsupported blob type. For more information about errors in this category, see [Summary of non-retryable upload errors](../databox/data-box-troubleshoot-data-upload.md#summary-of-non-retryable-upload-errors).|Yes |Yes | |
| 170 | +| `UploadErrorDataValidationError` |CRC computed during data ingestion doesn’t match the CRC computed during upload. |Yes |Yes | |
| 171 | +| `UploadErrorManagedConversionError` |The size of the blob being imported is invalid. The blob size is <*blob-size*> bytes. Supported sizes are between 20971520 Bytes and 8192 GiB. For more information, see [Summary of non-retryable upload errors](../databox/data-box-troubleshoot-data-upload.md#summary-of-non-retryable-upload-errors). |Yes |Yes | |
| 172 | +| `UploadErrorUnknownType` |Unknown error. |Yes |Yes | |
| 173 | +| `ContainerRenamed` |Renamed the container because the original container name doesn't follow [Azure naming conventions](../databox/data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). The original container has been renamed to DataBox-<*GUID*> from <*original container name*>. |No |Yes | |
| 174 | +| `ShareRenamed` |Renamed the share because the original share name doesn't follow [Azure naming conventions](../databox/data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). The original share has been renamed to DataBox-<*GUID*> from <*original folder name*>. |No |Yes | |
| 175 | +| `BlobRenamed` |Renamed the blob because the original blob name doesn't follow [Azure naming conventions](../databox/data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). The original blob has been renamed to BlockBlob/DataBox-<*GUID*> from <*original name*>. |No |Yes | |
| 176 | +| `FileRenamed` |Renamed the file because the original file name doesn't follow [Azure naming conventions](../databox/data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). The original file has been renamed to AzureFile/DataBox-<*GUID*> from <*original name*>. |No |Yes | |
| 177 | +| `DiskRenamed` |Renamed the managed disk file because the original file name doesn't follow [Azure naming conventions for managed disks](../databox/data-box-disk-limits.md#managed-disk-naming-conventions). The original managed disk file was renamed to ManagedDisk/DataBox-<*GUID*> from <*original name*>. |No |Yes | |
| 178 | +| `FileNameTrailsWithSlash` |Blob name or file name ends with a trailing slash. A blob name or file name that ends with a trailing backslash or forward slash can't be exported to disk. |No |Yes | |
| 179 | +| `ExportCloudHttp` |Unsupported blob type. |No |Yes | |
27 | 180 |
|
28 | | - <!--See [Import/Export service Log File Format](/previous-versions/azure/storage/common/storage-import-export-file-format-log) for the format of copy logs and the full list of status codes. ARCHIVED--> |
29 | 181 |
|
30 | 182 | ## Next steps |
31 | 183 |
|
32 | | -<!--* [Setting Up the Azure Import/Export Tool](storage-import-export-tool-setup-v1.md) ARCHIVED--> |
33 | | - * [Preparing hard drives for an import job](storage-import-export-data-to-blobs.md#step-1-prepare-the-drives) |
34 | | -<!--* [Repairing an import job](./storage-import-export-tool-repairing-an-import-job-v1.md)--> |
35 | | -<!--* [Repairing an export job](./storage-import-export-tool-repairing-an-export-job-v1.md)--> |
| 184 | +- [Review hard drive preparation steps for an import job](storage-import-export-data-to-blobs.md#step-1-prepare-the-drives). |
| 185 | +- [Contact Microsoft Support](storage-import-export-contact-microsoft-support.md). |
0 commit comments