Proposed Pull Request Change

title description author ms.service ms.topic ms.date ms.author ms.custom
Tutorial to verify data upload from Azure Data Box Disk to storage account Use this tutorial to learn how to verify the data uploaded from your Azure Data Box Disk to Azure storage account. stevenmatthew azure-data-box-disk tutorial 05/05/2022 shaas sfi-image-nochange
πŸ“„ Document Links
GitHub View on GitHub Microsoft Learn View on Microsoft Learn
Raw New Markdown
Generating updated version of doc...
Rendered New Markdown
Generating updated version of doc...
+0 -0
+0 -0
--- title: Tutorial to verify data upload from Azure Data Box Disk to storage account description: Use this tutorial to learn how to verify the data uploaded from your Azure Data Box Disk to Azure storage account. author: stevenmatthew ms.service: azure-data-box-disk ms.topic: tutorial ms.date: 05/05/2022 ms.author: shaas ms.custom: sfi-image-nochange # Customer intent: As an IT admin, I need to be able to order Data Box Disk to upload on-premises data from my server onto Azure. --- ::: zone target="docs" # Tutorial: Verify data upload from Azure Data Box Disk This is the last tutorial of the series: Deploy Azure Data Box Disk. In this tutorial, you will learn about: > [!div class="checklist"] > * Verify data upload to Azure > * Erasure of data from Data Box Disk ## Prerequisites Before you begin, make sure that you have completed the [Tutorial: Return Azure Data Box Disk](data-box-disk-deploy-picked-up.md). ## Verify data upload to Azure Once the disks are picked up by your carrier, the order status in the portal updates to **Picked up**. A tracking ID is also displayed. ![Screenshot of the Overview pane for a Data Box Disk import order in Picked Up state. The Overview option and Picked Up order status are highlighted.](media/data-box-disk-deploy-picked-up/data-box-portal-picked-up.png) When Microsoft receives and scans the disk, job status is updated to **Received**. ![Screenshot of the Overview pane for a Data Box Disk import order in Received state. The Overview menu option and Received order status are highlighted.](media/data-box-disk-deploy-picked-up/data-box-portal-received.png) The data automatically gets copied once the disks are connected to a server in the Azure datacenter. 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. Once the copy is complete, order status updates to **Completed**. The **DATA COPY DETAILS** show the path to the copy log, which reports any errors during the data copy. As of March 2022, you can choose **View by Storage Account(s)** or **View by Managed Disk(s)** to display the data copy details. [![Screenshot of the Data Copy Details.](media/data-box-disk-deploy-picked-up/data-box-portal-completed.png)](media/data-box-disk-deploy-picked-up/data-box-portal-completed-inline.png#lightbox) If you have an order from before March 2022, the data copy details will be shown as below: :::image type="content" source="media/data-box-disk-deploy-picked-up/data-box-portal-completed-old.png" alt-text="Screenshot of the Data Copy Details prior to March 2022."::: If the copy completes with errors, see [troubleshoot upload errors](data-box-disk-troubleshoot-upload.md). Verify that your data is in the storage account(s) before you delete it from the source. Your data can be in: - Your Azure Storage account(s). When you copy the data to Data Box, depending on the type, the data is uploaded to one of the following paths in your Azure Storage account. - For block blobs and page blobs: `https://<storage_account_name>.blob.core.windows.net/<containername>/files/a.txt` - For Azure Files: `https://<storage_account_name>.file.core.windows.net/<sharename>/files/a.txt` Alternatively, you can go to your Azure storage account in Azure portal and navigate from there. - Your managed disk resource group(s). When creating managed disks, the VHDs are uploaded as page blobs and then converted to managed disks. The managed disks are attached to the resource groups specified at the time of order creation. - If your copy to managed disks in Azure was successful, you can go to the **Order details** in the Azure portal and make a note of the resource group specified for managed disks. ![Screenshot of the Order Details pane for a Data Box Disk import order. The Order Details menu item and Managed Disk Resource Groups setting are highlighted.](media/data-box-disk-deploy-picked-up/order-details-resource-group.png) Go to the noted resource group, and locate your managed disks. ![Screenshot of a Resource Group resource for a Data Box Disk order. The resource group name and disks in the resource group are highlighted.](media/data-box-disk-deploy-picked-up/resource-group-attached-managed-disk.png) > [!NOTE] > If a page blob isn't successfully converted to a managed disk during a data copy, it stays in the storage account and you're charged for storage. - If you copied a VHDX, or a dynamic/differencing VHD, then the VHDX/VHD is uploaded to the staging storage account as a block blob. Go to your staging **Storage account > Blobs** and then select the appropriate container - StandardSSD, StandardHDD, or PremiumSSD. The VHDX/VHDs should show up as block blobs in your staging storage account. ::: zone-end ::: zone target="chromeless" ## Verify data upload to Azure After the data is uploaded to Azure, verify that your data is in the storage account(s) before you delete it from the source. Your data can be in: - Your Azure Storage account(s). When you copy the data to Data Box, depending on the type, the data is uploaded to one of the following paths in your Azure Storage account. - **For block blobs and page blobs**: `https://<storage_account_name>.blob.core.windows.net/<containername>/files/a.txt` - **For Azure Files**: `https://<storage_account_name>.file.core.windows.net/<sharename>/files/a.txt` - Your managed disk resource group(s). When creating managed disks, the VHDs are uploaded as page blobs and then converted to managed disks. The managed disks are attached to the resource groups specified at the time of order creation. ::: zone-end To verify that the data has uploaded into Azure, take the following steps: 1. Go to the storage account associated with your disk order. 2. Go to **Blob service > Browse blobs**. The list of containers is presented. Corresponding to the subfolder that you created under *BlockBlob* and *PageBlob* folders, containers with the same name are created in your storage account. If the folder names do not conform to Azure naming conventions, then the data upload to Azure will fail. 3. To verify that the entire dataset has loaded, use Microsoft Azure Storage Explorer. Attach the storage account corresponding to the Data Box Disk order and then look at the list of blob containers. Select a container, click **…More** and then click **Folder statistics**. In the **Activities** pane, the statistics for that folder including the number of blobs and the total blob size is displayed. The total blob size in bytes should match the size of the dataset. ![Screenshot showing Folder Statistics for a Blob in Azure Storage Explorer. A Blob Container, Blob, and Folder are selected. The Folder Statistics option and a statistics set are highlighted.](media/data-box-disk-deploy-picked-up/folder-statistics-storage-explorer.png) ## Erasure of data from Data Box Disk Once the upload to Azure is complete, the Data Box Disk service erases the data on its disks as per the [NIST SP 800-88](https://csrc.nist.gov/News/2014/Released-SP-800-88-Revision-1,-Guidelines-for-Medi) standard. After the erasure is complete, you can [Download the order history](data-box-portal-admin.md#download-order-history). ::: zone target="docs" ## Next steps In this tutorial, you learned about Azure Data Box Disk topics such as: > [!div class="checklist"] > * Verify data upload to Azure > * Erasure of data from Data Box Disk Advance to the next how-to to learn how to manage Data Box Disk via the Azure portal. > [!div class="nextstepaction"] > [Use Azure portal to administer Azure Data Box Disk](./data-box-portal-ui-admin.md) ::: zone-end
Success! Branch created successfully. Create Pull Request on GitHub
Error: