Skip to content

Commit 9eeda42

Browse files
authored
Merge pull request #183656 from v-dalc/logtweaks
Import/Export: [Update] Review logs - tweaks (logtweaks)
2 parents 9232c35 + f8aff5c commit 9eeda42

File tree

6 files changed

+25
-7
lines changed

6 files changed

+25
-7
lines changed
64.4 KB
Loading

articles/import-export/storage-import-export-data-from-blobs.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: alkohli
55
services: storage
66
ms.service: storage
77
ms.topic: tutorial
8-
ms.date: 11/29/2021
8+
ms.date: 12/27/2021
99
ms.author: alkohli
1010
ms.subservice: common
1111
ms.custom: "tutorial, devx-track-azurepowershell, devx-track-azurecli, contperf-fy21q3"
@@ -442,6 +442,15 @@ Here is an example of the sample input.
442442

443443
`WAImportExport.exe Unlock /bk:CAAcwBoAG8AdQBsAGQAIABiAGUAIABoAGkAZABkAGUAbgA= /driveLetter:e`
444444

445+
You can use the copy logs from the job to verify that all data transferred successfully:
446+
447+
- Use the *verbose log* to verify each successfully transferred file.
448+
- Use the *copy log* to find the source of each failed data copy.
449+
450+
To find the log locations, open the job in the [Azure portal/](https://portal.azure.com/). The **Data copy details** show the **Copy log path** and **Verbose log path** for each drive that was included in the order.
451+
452+
[ ![Screenshot showing a completed export job in Azure Import Export. In Data Copy Details, the Copy Log Path and Verbose Log Path are highlighted.](./media/storage-import-export-data-from-blobs/import-export-status-export-order-completed.png) ](./media/storage-import-export-data-from-blobs/import-export-status-export-order-completed.png#lightbox)
453+
445454
At this time, you can delete the job or leave it. Jobs automatically get deleted after 90 days.
446455

447456
## Next steps

articles/import-export/storage-import-export-data-to-blobs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: alkohli
55
services: storage
66
ms.service: storage
77
ms.topic: tutorial
8-
ms.date: 11/29/2021
8+
ms.date: 12/27/2021
99
ms.author: alkohli
1010
ms.subservice: common
1111
ms.custom: "tutorial, devx-track-azurepowershell, devx-track-azurecli, contperf-fy21q3"

articles/import-export/storage-import-export-tool-reviewing-job-status-v1.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: v-dalc
55
services: storage
66
ms.service: storage
77
ms.topic: how-to
8-
ms.date: 12/22/2021
8+
ms.date: 12/27/2021
99
ms.author: alkohli
1010
ms.subservice: common
1111
---
@@ -44,7 +44,7 @@ Each data transfer for a disk generates a copy log. If you chose to save a verbo
4444

4545
During an import, the Import/Export service generates a verbose log and a copy log for each disk.
4646

47-
### Verbose logs
47+
### Verbose log
4848

4949
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.
5050

@@ -59,7 +59,7 @@ The verbose log is an optional file that you can enable during ordering. It's a
5959

6060
[!INCLUDE [data-box-disk-sample-verbose-log.md](../../includes/data-box-disk-sample-verbose-log.md)]
6161

62-
### Copy logs
62+
### Copy log
6363

6464
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.
6565

63.1 KB
Loading

includes/storage-import-export-verify-data-copy.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,20 @@ services: storage
66

77
ms.service: storage
88
ms.topic: include
9-
ms.date: 12/21/2021
9+
ms.date: 12/27/2021
1010
ms.author: alkohli
1111
ms.custom: include file
1212
---
1313

14-
Track the job to completion. Then make sure that your data has been uploaded to Azure successfully. Use the *verbose log* to verify each successfully transferred file and the *copy log* to find the source of each failed data copy. For more information, see [Review copy logs from imports and exports](..\articles\import-export\storage-import-export-tool-reviewing-job-status-v1.md).
14+
Track the job to completion. Then make sure that your data has been uploaded to Azure successfully.
15+
16+
Review the **Data copy details** of the completed job to locate the logs for each drive included in the job:
17+
18+
- Use the *verbose log* to verify each successfully transferred file.
19+
- Use the *copy log* to find the source of each failed data copy.
20+
21+
[ ![Screenshot showing a completed import job in Azure Import Export. In Data Copy Details, the Copy Log Path and Verbose Log Path are highlighted.](./media/storage-import-export-verify-data-copy/completed-import-order.png) ](./media/storage-import-export-verify-data-copy/completed-import-order.png#lightbox)
22+
23+
For more information, see [Review copy logs from imports and exports](..\articles\import-export\storage-import-export-tool-reviewing-job-status-v1.md).
1524

1625
After you verify the data transfers, you can delete your on-premises data. Delete your on-premises data only after you verify that the upload was successful.

0 commit comments

Comments
 (0)