![]() The original container/share/Blob has been renamed to: DataBox-6bcae46f-04c8-4385-8442-3a28b962c930 :from: CV :because either name has invalid character(s) or length is not supported The original container/share/Blob has been renamed to: DataBox-f55763d4-8ef7-458f-b029-f36b51ada34f :from: New Folder :because either name has invalid character(s) or length is not supported The error entry gives the original and new file names. One file share was renamed ( ShareRenamed error), and two containers were renamed ( ContainerRenamed error). This copy failed, with no validation errors but with three copy errors. The following sample is a copy log for an import to both Azure Files and Azure Blob storage. Summary of copy errors by error category.Summary of validation errors by error category.The summary at the end of the log (look for CopyLog Summary) gives the following information: For more information, see Data upload errors for Log version. The destination share within the container or file share. The copy log ends with a summary of validation and copy errors that occurred during the import.Įach error entry contains the following information. The copy log contains an error entry for each file that failed to import, with error detail. The following sample verbose log has sample file entries for block blob, page blob, and Azure File imports. The cyclic redundancy check 64 (CRC64) checksum that was used to verify data integrity during data transfer. Path to the file within the storage account. The verbose log doesn’t provide summary information. It's a simple listing of all files that were successfully imported from the drive, with the following information for each file. The verbose log is an optional file that you can enable during ordering. ![]() If you chose to save a verbose log when you placed your order, there’s also a verbose log in the same folder. If you aren't sure which version of the logs you have, see Identify log version.Įach data transfer for a disk generates a copy log. The log formats of copy/error log and verbose log differ for the two log versions. The following illustration shows the DriveLogVersion in the summary section of a copy log. To find out the log release for both the copy/error log and the accompanying verbose log, check the drive log version in the copy/error log. The log versions are discussed separately in the sections that follow.Īlong with the verbose log, you'll see either a copy log ( _copy.xml) or an error log ( _error.xml), depending on the drive release. There are two versions of the copy/error log and verbose log, with different formats. Select each log and download a local copy. The following illustration shows the logs in a waies container. To view the logs, open the container that stores the logs in your storage account. See Identify log version for more information. For help interpreting the logs, use the instructions for the associated drive log version. Logs in the databoxcopylog container have a different format than logs in the waies container. The logs are uploaded to a waies container in the storage account. If there are any errors when uploading the data to Azure, Copy logs displays a path to the folder where the diagnostics logs are located. The URLs have these formats: Log typeįor your earlier orders, the display might look like the following screen. The logs are uploaded to a container (for blob imports) or share (for imports to Azure Files) in the storage account. If you chose to save verbose logs when you placed your order, you'll also see the path to the verbose log. To find the logs from a data upload, do the following steps.Īs the data upload completes for each disk, the Overview pane displays the disk status and the paths to diagnostics logs for the disk.įor new orders, the disk details look like those in the following screen. The verbose log has a listing of all copy operations that succeeded on every blob and file. The copy log ends with a summary of errors by error category. The copy log reports events for all failed copy operations between the disk and the Azure Storage account. These logs are uploaded to the same storage account that was used to upload data. When the data from a Data Box Disk is uploaded in the Azure datacenter, a copy/error log and a verbose log are generated for each storage account. This article describes the issues you see when you upload data in the Azure datacenter using Azure Data Box Disk.
0 Comments
Leave a Reply. |