Merge pull request #78783 from alkohli/mig

added SPO article

Author: American-Dipper

articles/databox/TOC.yml

@@ -161,8 +161,12 @@
         href: data-box-disk-contact-microsoft-support.md 
       - name: Migrate
         items:
+        - name: To SharePoint Online
+          href: data-box-heavy-migrate-spo.md
         - name: To Azure File Sync
           href: ../storage/files/storage-sync-offline-data-transfer.md?toc=/azure/databox/toc.json&bc=/azure/databox/breadcrumb/toc.json
+        - name: From HDFS store
+          href: ../storage/blobs/data-lake-storage-migrate-on-premises-hdfs-cluster.md?toc=/azure/databox/toc.json&bc=/azure/databox/breadcrumb/toc.json
   - name: Resources
     items:
     - name: Data Box product

articles/databox/data-box-heavy-migrate-spo.md

@@ -0,0 +1,91 @@
+---
+title: Use Azure Data Box Heavy to migrate file share content to SharePoint Online| Microsoft Docs
+description: Use this tutorial to learn how to migrate file share content to Share Point Online using your Azure Data Box Heavy
+services: databox
+author: alkohli
+
+ms.service: databox
+ms.subservice: heavy
+ms.topic: tutorial
+ms.date: 06/05/2019
+ms.author: alkohli
+---
+
+# Use the Azure Data Box Heavy to migrate your file share content to SharePoint Online
+
+Use your Azure Data Box Heavy and the SharePoint Migration Tool (SPMT) to easily migrate your file share content to SharePoint Online and OneDrive. By using Data Box Heavy, you can remove the dependency on your Wide-area network (WAN) link to transfer the data.
+
+The Microsoft Azure Data Box is a service that lets you order a device from the Microsoft Azure portal. You can then copy terabytes of data from your servers to the device. After shipping it back to Microsoft, your data is copied into Azure. Depending on the size of data you intend to transfer, you can choose from:
+
+- [Data Box Disk](https://docs.microsoft.com/azure/databox/data-box-disk-overview) with 35-TB usable capacity per order for small-to-medium datasets.
+- [Data Box](https://docs.microsoft.com/azure/databox/data-box-overview) with 80-TB usable capacity per device for medium-to-large datasets.
+- [Data Box Heavy](https://docs.microsoft.com/azure/databox/data-box-heavy-overview) with 770-TB usable capacity per device for large datasets. Data Box Heavy is currently in preview.
+
+This article specifically talks about how to use the Data Box Heavy to migrate your file share content to SharePoint Online.
+
+## Requirements and costs
+
+### For Data Box Heavy
+
+- Data Box Heavy is only available for Enterprise Agreement (EA), Cloud solution provider (CSP), or Azure sponsorship offers. If your subscription does not fall in any of the above types, contact Microsoft Support to upgrade your subscription or see [Azure subscription pricing](https://azure.microsoft.com/pricing/).
+- There is a fee to use Data Box Heavy. Make sure to review the [Data Box Heavy pricing](https://azure.microsoft.com/pricing/details/databox/heavy/).
+
+
+### For SharePoint Online
+
+- Review the [Minimum requirements for the SharePoint Migration Tool (SPMT)](https://docs.microsoft.com/sharepointmigration/how-to-use-the-sharepoint-migration-tool).
+
+## Workflow overview
+
+This workflow requires you to perform steps on Azure Data Box Heavy as well as on Share Point online.
+The following steps relate to your Azure Data Box Heavy.
+
+1. Order Azure Data Box Heavy.
+2. Receive and set up your device.
+3. Copy data from your on-premises file share to folder for Azure Files on your device.
+4. After the copy is complete, ship the device back as per the instructions.
+5. Wait for the data to completely upload to Azure.
+
+The following steps relate to Share Point online.
+
+6. Create a VM in the Azure portal and mount the Azure file share on it.
+7. Install the SPMT tool on the Azure VM.
+8. Run the SPMT tool using the Azure file share as the *source*.
+9. Complete the final steps of the tool.
+10. Verify and confirm your data.
+
+## Use Data Box Heavy to copy data
+
+Take the following steps to copy data to your Data Box Heavy.
+
+1. [Order your Data Box Heavy](data-box-heavy-deploy-ordered.md).
+2. After you receive your Data Box Heavy, [Set up the Data Box Heavy](data-box-heavy-deploy-set-up.md). You'll cable and configure both the nodes on your device.
+3. [Copy data to Azure Data Box Heavy](data-box-heavy-deploy-copy-data.md). While copying, make sure to:
+
+    - Use only the *AzureFile* folder in the Data Box Heavy to copy the data. This is because you want the data to end up in an Azure file share, not in block blobs or page blobs.
+    - Copy files to a folder within *AzureFile* folder. A subfolder within *AzureFile* folder creates a file share. Files copied directly to *AzureFile* folder fail and are uploaded as block blobs. This is the file share that you will mount on your VM in the next step.
+    - Copy data to both nodes of your Data Box Heavy.
+3. Run [Prepare to ship](data-box-heavy-deploy-picked-up.md#prepare-to-ship) on your device. A successful prepare to ship ensures a successful upload of files to Azure.
+4. [Return the device](data-box-heavy-deploy-picked-up.md#ship-data-box-heavy-back).
+5. [Verify the data upload to Azure](data-box-heavy-deploy-picked-up.md#verify-data-upload-to-azure).
+
+## Use SPMT to migrate data
+
+After you receive confirmation from the Azure data team that your data copy has completed, you can now proceed to migrate your data to SharePoint Online.
+
+For best performance and connectivity, we recommend that you create an Azure Virtual Machine (VM).
+
+1. Sign into the Azure portal, and then [Create a virtual machine](../virtual-machines/windows/quick-create-portal.md).
+2. [Mount the Azure file share onto the VM](../storage/files/storage-how-to-use-files-windows.md#mount-the-azure-file-share-with-file-explorer).
+3. [Download the SharePoint Migration tool](http://spmtreleasescus.blob.core.windows.net/install/default.htm) and install it on your Azure VM.
+4. Start the SharePoint Migration Tool. Click **Sign in** and enter your Office 365 username and password.
+5. When prompted **Where is your data?**, select **File share**. Enter the path to your Azure file share where your data is located.
+6. Follow the remaining prompts as normal, including your target location. For more information, go to [How to use the SharePoint Migration Tool](https://docs.microsoft.com/sharepointmigration/how-to-use-the-sharepoint-migration-tool).
+
+> [!IMPORTANT]
+> - The speed at which data is ingested into SharePoint Online is affected by several factors, regardless if you have your data already in Azure. Understanding these factors will help you plan and maximize the efficiency of your migration.  For more information, go to [SharePoint Online and OneDrive migration Speed](/sharepointmigration/sharepoint-online-and-onedrive-migration-speed).
+> - There is a risk of losing existing permissions on files when migrating the data to SharePoint Online. You may also lose certain metadata, such as *Created by* and *Date modified by*.
+
+## Next steps
+
+[Order your Data Box Heavy](./data-box-heavy-deploy-ordered.md)

articles/storage/blobs/data-lake-storage-migrate-on-premises-HDFS-cluster.md

@@ -5,21 +5,21 @@ services: storage
 author: normesta
 
 ms.service: storage
-ms.date: 03/01/2019
+ms.date: 06/05/2019
 ms.author: normesta
 ms.topic: article
 ms.component: data-lake-storage-gen2
 ---
 
 # Use Azure Data Box to migrate data from an on-premises HDFS store to Azure Storage
 
-You can migrate data from an on-premises HDFS store of your Hadoop cluster into Azure Storage (blob storage or Data Lake Storage Gen2) by using a Data Box device.
+You can migrate data from an on-premises HDFS store of your Hadoop cluster into Azure Storage (blob storage or Data Lake Storage Gen2) by using a Data Box device. You can choose from an 80-TB Data Box or a 770-TB Data Box Heavy.
 
 This article helps you complete these tasks:
 
-:heavy_check_mark: Copy your data to a Data Box device.
+:heavy_check_mark: Copy your data to a Data Box or a Data Box Heavy device.
 
-:heavy_check_mark: Ship the Data Box device to Microsoft.
+:heavy_check_mark: Ship the device back to Microsoft.
 
 :heavy_check_mark: Move the data onto your Data Lake Storage Gen2 storage account.
 
@@ -33,23 +33,23 @@ You need these things to complete the migration.
 
 * An on-premises Hadoop cluster that contains your source data.
 
-* An [Azure Data Box device](https://azure.microsoft.com/services/storage/databox/). 
+* An [Azure Data Box device](https://azure.microsoft.com/services/storage/databox/).
 
-    - [Order your Data Box](https://docs.microsoft.com/azure/databox/data-box-deploy-ordered). While ordering your Box, remember to choose a storage account that **doesn't** have hierarchical namespaces enabled on it. This is because Data Box does not yet support direct ingestion into Azure Data Lake Storage Gen2. You will need to copy into a storage account and then do a second copy into the ADLS Gen2 account. Instructions for this are given in the steps below.
-    - [Cable and connect your Data Box](https://docs.microsoft.com/azure/databox/data-box-deploy-set-up) to an on-premises network.
+    - [Order your Data Box](https://docs.microsoft.com/azure/databox/data-box-deploy-ordered) or [Data Box Heavy](https://docs.microsoft.com/azure/databox/data-box-heavy-deploy-ordered). While ordering your device, remember to choose a storage account that **doesn't** have hierarchical namespaces enabled on it. This is because Data Box devices do not yet support direct ingestion into Azure Data Lake Storage Gen2. You will need to copy into a storage account and then do a second copy into the ADLS Gen2 account. Instructions for this are given in the steps below.
+    - Cable and connect your [Data Box](https://docs.microsoft.com/azure/databox/data-box-deploy-set-up) or [Data Box Heavy](https://docs.microsoft.com/azure/databox/data-box-heavy-deploy-set-up) to an on-premises network.
 
 If you are ready, let's start.
 
 ## Copy your data to a Data Box device
 
 To copy the data from your on-premises HDFS store to a Data Box device, you'll set a few things up, and then use the [DistCp](https://hadoop.apache.org/docs/stable/hadoop-distcp/DistCp.html) tool.
 
-If the amount of data that you are copying is more than the capacity of a single Data Box, you will have to break up your data set into sizes that do fit into your Data Boxes.
+If the amount of data that you are copying is more than the capacity of a single Data Box or that of single node on Data Box Heavy, break up your data set into sizes that do fit into your devices.
 
-Follow these steps to copy data via the REST APIs of Blob/Object storage to your Data Box. The REST API interface will make the Data Box appear as a HDFS store to your cluster. 
+Follow these steps to copy data via the REST APIs of Blob/Object storage to your Data Box device. The REST API interface will make the device appear as an HDFS store to your cluster. 
 
 
-1. Before you copy the data via REST, identify the security and connection primitives to connect to the REST interface on the Data Box. Sign in to the local web UI of Data Box and go to **Connect and copy** page. Against the Azure storage account for your Data Box, under **Access settings**, locate and select **REST(Preview)**.
+1. Before you copy the data via REST, identify the security and connection primitives to connect to the REST interface on the Data Box or Data Box Heavy. Sign in to the local web UI of Data Box and go to **Connect and copy** page. Against the Azure storage account for your device, under **Access settings**, locate, and select **REST**.
 
     !["Connect and copy" page](media/data-lake-storage-migrate-on-premises-HDFS-cluster/data-box-connect-rest.png)
 
@@ -59,14 +59,14 @@ Follow these steps to copy data via the REST APIs of Blob/Object storage to your
 
      !["Access storage account and upload data" dialog](media/data-lake-storage-migrate-on-premises-HDFS-cluster/data-box-connection-string-http.png)
 
-3. Add the endpoint and the Data Box IP address to `/etc/hosts` on each node.
+3. Add the endpoint and the Data Box or Data Box Heavy node IP address to `/etc/hosts` on each node.
 
     ```    
     10.128.5.42  mystorageaccount.blob.mydataboxno.microsoftdatabox.com
     ```
     If you are using some other mechanism for DNS, you should ensure that the Data Box endpoint can be resolved.
     
-4. Set a shell variable `azjars` to point to the `hadoop-azure` and the `microsoft-windowsazure-storage-sdk` jar files. These files are under the Hadoop installation directory (You can check if these files exist by using this command `ls -l $<hadoop_install_dir>/share/hadoop/tools/lib/ | grep azure` where `<hadoop_install_dir>` is the directory where you have installed Hadoop  ) Use the full paths. 
+4. Set a shell variable `azjars` to point to the `hadoop-azure` and the `microsoft-windowsazure-storage-sdk` jar files. These files are under the Hadoop installation directory (You can check if these files exist by using this command `ls -l $<hadoop_install_dir>/share/hadoop/tools/lib/ | grep azure` where `<hadoop_install_dir>` is the directory where you have installed Hadoop) Use the full paths. 
     
     ```
     # azjars=$hadoop_install_dir/share/hadoop/tools/lib/hadoop-azure-2.6.0-cdh5.14.0.jar
@@ -118,22 +118,30 @@ Follow these steps to copy data via the REST APIs of Blob/Object storage to your
   
 To improve the copy speed:
 - Try changing the number of mappers. (The above example uses `m` = 4 mappers.)
-- Try running mutliple `distcp` in parallel.
-- Remember that large files perform better than small files.       
+- Try running multiple `distcp` in parallel.
+- Remember that large files perform better than small files.
     
 ## Ship the Data Box to Microsoft
 
 Follow these steps to prepare and ship the Data Box device to Microsoft.
 
-1. After the data copy is complete, run [Prepare to ship](https://docs.microsoft.com/azure/databox/data-box-deploy-copy-data-via-rest) on your Data Box. After the device preparation is complete, download the BOM files. You will use these BOM or manifest files later to verify the data uploaded to Azure. Shut down the device and remove the cables. 
-2.	Schedule a pickup with UPS to [Ship your Data Box back to Azure](https://docs.microsoft.com/azure/databox/data-box-deploy-picked-up). 
-3.	After Microsoft receives your device, it is connected to the network datacenter and data is uploaded to the storage account you specified (with hierarchical namespaces disabled) when you ordered the Data Box. Verify against the BOM files that all your data is uploaded to Azure. You can now move this data to a Data Lake Storage Gen2 storage account.
+1. After the data copy is complete, run:
+    
+    - [Prepare to ship on your Data Box or Data Box Heavy](https://docs.microsoft.com/azure/databox/data-box-deploy-copy-data-via-rest).
+    - After the device preparation is complete, download the BOM files. You will use these BOM or manifest files later to verify the data uploaded to Azure. 
+    - Shut down the device and remove the cables.
+2.	Schedule a pickup with UPS. Follow the instructions to:
+
+    - [Ship your Data Box](https://docs.microsoft.com/azure/databox/data-box-deploy-picked-up) 
+    - [Ship your Data Box Heavy](https://docs.microsoft.com/azure/databox/data-box-heavy-deploy-picked-up).
+3.	After Microsoft receives your device, it is connected to the datacenter network and the data is uploaded to the storage account you specified (with hierarchical namespaces disabled) when you placed the device order. Verify against the BOM files that all your data is uploaded to Azure. You can now move this data to a Data Lake Storage Gen2 storage account.
+
 
 ## Move the data onto your Data Lake Storage Gen2 storage account
 
 This step is needed if you are using Azure Data Lake Storage Gen2 as your data store. If you are using just a blob storage account without hierarchical namespace as your data store, you do not need to do this step.
 
-You can do this in 2 ways. 
+You can do this in two ways.
 
 - Use [Azure Data Factory to move data to ADLS Gen2](https://docs.microsoft.com/azure/data-factory/load-azure-data-lake-storage-gen2). You will have to specify **Azure Blob Storage** as the source.