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
### How do I verify the data I copied onto my Data Box?
213
+
214
+
After the data copy is complete, when you run **Prepare to ship**, your data is validated. Data Box generates a list of files and checksums for the data during the validation process. You can download the list of files and verify the list against the files in the source data. For more information, go to [Prepare to ship](data-box-deploy-picked-up.md#prepare-to-ship).
215
+
212
216
## [Data Box only](#tab/data-box)
213
217
214
218
### The system fault indicator LED on the front operating panel is on. What should I do?
@@ -418,13 +422,13 @@ sections:
418
422
419
423
For error information and steps to proceed with your order, see [Review copy errors in uploads from Azure Data Box and Azure Data Box Heavy devices](data-box-troubleshoot-data-upload.md).
420
424
421
-
### How do I verify the data I copied onto my Data Box?
425
+
### I'm seeing date entries with "Fri, 31 Dec 9999 23:59:59" on some files. What does that mean?
422
426
423
-
After the data copy is complete, when you run **Prepare to ship**, your data is validated. Data Box generates a list of files and checksums for the data during the validation process. You can download the list of files and verify the list against the files in the source data. For more information, go to [Prepare to ship](data-box-deploy-picked-up.md#prepare-to-ship).
### What happens to my data after I return the Data Box?
426
430
427
-
Once the data copy to Azure is complete, the data from the disks on the Data Box is securely erased as per the NIST SP 800-88 Revision 1 guidelines. For more information, go to [Erasure of data from Data Box](data-box-deploy-picked-up.md#erasure-of-data-from-data-box).
431
+
Once the data upload to Azure is complete, the data from the disks on the Data Box is securely erased as per the NIST SP 800-88 Revision 1 guidelines. For more information, go to [Erasure of data from Data Box](data-box-deploy-picked-up.md#erasure-of-data-from-data-box).
Copy file name to clipboardExpand all lines: includes/data-box-data-upload-caveats.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ author: alkohli
3
3
ms.service: databox
4
4
ms.subservice: heavy
5
5
ms.topic: include
6
-
ms.date: 01/11/2022
6
+
ms.date: 01/13/2022
7
7
ms.author: alkohli
8
8
---
9
9
@@ -25,5 +25,5 @@ ms.author: alkohli
25
25
- If there are any errors when uploading data to Azure, an error log is created in the target storage account. The path to this error log is available when the upload is complete, and you can review the log to take corrective action. Don't delete data from the source without verifying the uploaded data.
26
26
- File metadata and NTFS permissions can be preserved when the data is uploaded to Azure Files using guidance in [Preserving file ACLs, attributes, and timestamps with Azure Data Box](../articles/databox/data-box-file-acls-preservation.md).
27
27
- The hierarchy of the files is maintained while uploading to the cloud for both blobs and Azure Files. For example, you copied a file at this path: `<container folder>\A\B\C.txt`. This file is uploaded to the same path in cloud.
28
-
-If the **CreateTime** or **LastWriteTime** field for a file exceeds the allowable size during an upload, “Fri, 31 Dec 9999 23:59:59” replaces the original date in the Azure file property. The file upload succeeds, and no error is raised.
If the **CreateTime** or **LastWriteTime** field for a file exceeds the allowable size during an upload, “Fri, 31 Dec 9999 23:59:59” replaces the original date in the Azure file property. The file upload succeeds, and no error is raised.
0 commit comments