Skip to content

Commit 9f324c1

Browse files
authored
Merge pull request #277782 from stevenmatthew/crc061024
crc061024: CRC checksum validation script call-outs
2 parents e4e28a1 + d9b4fd1 commit 9f324c1

File tree

3 files changed

+12
-4
lines changed

3 files changed

+12
-4
lines changed

articles/databox/data-box-logs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,10 @@ During the data upload to Azure, a copy log is created.
200200

201201
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.
202202

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.
204207
205208
By default, logs are written to a container named `copylog`. The logs are stored with the following naming convention:
206209

includes/data-box-verify-upload-return.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,17 @@ author: stevenmatthew
33
ms.service: databox
44
ms.subservice: pod
55
ms.topic: include
6-
ms.date: 06/08/2022
6+
ms.date: 06/10/2024
77
ms.author: shaas
88
---
99

1010
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.
1111

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.
1313

1414
### Review copy errors from upload
1515

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.
1717

1818
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).
1919

@@ -26,6 +26,11 @@ When you confirm that you've reviewed the errors and are ready to proceed, the d
2626

2727
Once the data upload is complete, order status updates to **Completed**.
2828

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+
2934
Verify that your data is uploaded to Azure before you delete it from the source. Your data can be in:
3035

3136
- 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:
859 Bytes
Loading

0 commit comments

Comments
 (0)