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
Copy file name to clipboardExpand all lines: articles/databox/data-box-logs.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,10 @@ During the data upload to Azure, a copy log is created.
200
200
201
201
For each order that is processed, the Data Box service creates a copy log in the associated storage account. The copy log has the total number of files that were uploaded and the number of files that errored out during the data copy from Data Box to your Azure storage account.
202
202
203
-
A Cyclic Redundancy Check (CRC) computation is done during the upload to Azure. The CRCs from the data copy and after the data upload are compared. A CRC mismatch indicates that the corresponding files failed to upload.
203
+
> [!NOTE]
204
+
> A Cyclic Redundancy Check (CRC) computation is completed during the upload to Azure. The CRCs from the data copy and data upload are compared. A CRC mismatch indicates that the corresponding files failed to upload.
205
+
>
206
+
> You can use the CRC checksum tool script to compare the checksums of the on-premises source data with the data uploaded to Azure. The script can be downloaded from [Azure Samples](https://github.com/Azure-Samples/data-box-samples/tree/main/JavaToolforCRC). See the [README file](https://github.com/Azure-Samples/data-box-samples/blob/main/JavaToolforCRC/README.md) for more information.
204
207
205
208
By default, logs are written to a container named `copylog`. The logs are stored with the following naming convention:
Copy file name to clipboardExpand all lines: includes/data-box-verify-upload-return.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,17 +3,17 @@ author: stevenmatthew
3
3
ms.service: databox
4
4
ms.subservice: pod
5
5
ms.topic: include
6
-
ms.date: 06/08/2022
6
+
ms.date: 06/10/2024
7
7
ms.author: shaas
8
8
---
9
9
10
10
When Microsoft receives and scans the device, order status is updated to **Received**. The device then undergoes physical verification for damage or signs of tampering.
11
11
12
-
After the verification is complete, the Data Box is connected to the network in the Azure datacenter. The data copy starts automatically. Depending upon the data size, the copy operation may take a few hours to days to complete. You can monitor the copy job progress in the portal.
12
+
After the verification is complete, the Data Box is connected to the network in the Azure datacenter. The data copy starts automatically. Depending upon the data size, the copy operation can take between a few hours to a few days to complete. You can monitor the copy job progress in the portal.
13
13
14
14
### Review copy errors from upload
15
15
16
-
When files fail to upload because of an non-retryable error, you're notified to review the errors before proceeding. The errors are listed in the data copy log.
16
+
When files fail to upload due to a nonretryable error, you're notified to review the errors before proceeding. The errors are listed in the data copy log.
17
17
18
18
You can't fix these errors. The upload has completed with errors. The notification lets you know about any configuration issues you need to fix before you try another upload via network transfer or a new import order. For guidance, see [Review copy errors in uploads from Azure Data Box and Azure Data Box Heavy devices](../articles/databox/data-box-troubleshoot-data-upload.md).
19
19
@@ -26,6 +26,11 @@ When you confirm that you've reviewed the errors and are ready to proceed, the d
26
26
27
27
Once the data upload is complete, order status updates to **Completed**.
28
28
29
+
> [!NOTE]
30
+
> A Cyclic Redundancy Check (CRC) computation is completed during the upload to Azure. The CRCs from the data copy and data upload are compared. A CRC mismatch indicates that the corresponding files failed to upload.
31
+
>
32
+
> You can use the CRC checksum tool script to compare the checksums of the on-premises source data with the data uploaded to Azure. The script can be downloaded from [Azure Samples](https://github.com/Azure-Samples/data-box-samples/tree/main/JavaToolforCRC). See the [README file](https://github.com/Azure-Samples/data-box-samples/blob/main/JavaToolforCRC/README.md) for more information.
33
+
29
34
Verify that your data is uploaded to Azure before you delete it from the source. Your data can be in:
30
35
31
36
- Your Azure Storage account(s). When you copy the data to Data Box, the data is uploaded to one of the following paths in your Azure Storage account:
0 commit comments