Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drives to OneDrive for Business Copy Google Drive to an Office 365 Group Copy Google Drive to Microsoft Teams Copy File Shares to OneDrive for Business Copy File Shares to SharePoint Online Copy File Shares to an Office 365 Group Copy File Share to Microsoft Teams Copy My Sites to OneDrive for Business Copy OneDrive for Business to OneDrive for Business Copy Box to OneDrive for Business Copy Box to SharePoint Online Copy Box to an Office 365 Group Copy Box to Microsoft Teams Copy Dropbox Business to OneDrive for Business Copy Dropbox to an Office 365 Group Copy Dropbox to Microsoft Teams OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Analysis Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Reprocess Failed Items Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Azure Turbo Mode Migration

Follow these steps in order to perform Azure Turbo Mode Migration.

1.From within Essentials, initiate a migration as you typically would and continue through the Migration wizard until you reach the final page with the Advanced Options section. (For more information about various Migration wizard options see one of the Site Migration Wizard section, and any of its dependent sections)

info

NOTE: Please note that the user account provided requires Site Collection Administrator access to each destination SharePoint Online Site Collection.

2.Under the Advanced Options section of most migration wizards there is a option labeled "Enable Azure Turbo Mode". Select this option.
Azure Turbo Mode 1

3.Next to the User Provided Storage Option, click the Select button. This will a window that will allow you to connect to your Azure account.

info

NOTE: As of the October 31, 2016 release, you may now choose between using your own Azure Provided Storage for this use or Microsoft's Provided Storage.  Please refer to this page for more information: Microsoft vs User Provided Storage.

azure turbo mode 2

4.In the Azure window, enter your Storage Account name. For information on how to get the account key name see this section. Click Connect.
azure turbo mode 3

5.In the next Connect to Azure window enter the Account Key for the Storage Account you entered in the previous step. For information on how to get the account key see this section. Click Connect.
azure turbo mode 4

6.If both values are correct, you will return to the original dialog where the OK button will now be enabled, Click Ok.  If either of the values entered was incorrect, you will receive an authentication failure message and you will have an opportunity to try again.
azure turbo mode 5

7.Once the Enable Azure Turbo Mode option is enabled and the correct values have been provided (if the option is enabled and no values are supplied, then Azure Turbo Mode will not be used for this migration), you may continue with the migration wizard.

8.For future migrations, you may decide to save the Azure Storage User Account key into Essentials by clicking the lock icon next to the Storage Account Name. While this step is optional, it may save some time in configuring future migrations.
azure turbo mode 6
In order to do this you must know your Master Password - to manage the master password go to the Help tab, select Profile Manager, and then go the Password Manager section.

info

NOTE: As of February 2016, there is a new Azure Turbo option named "Defer Upload to Azure" which will process the packages from the source but not upload them to Azure.  Please read the Defer Upload to Azure section for additional information.

Monitoring Azure Turbo Migration

To see more information about the queued jobs, their status, GUIDs, results, and more, simply select the destination SharePoint Online site from the Navigator tree, right click and select Open Azure Turbo Queue.
azure turbo mode 7

 
The Azure Turbo Queue perspective options in Essentials allows you to see a wealth of information related to each job that is in the queue. Here you can sort the jobs by each column, or you can simply use the "search by GUID" bar to easily navigate to a specific Azure Turbo job.

info

NOTE: If you do not see any jobs then either they have not been queued yet (it can take anywhere from 2 to 5+ minutes for the first job to be queued) or you need to refresh the list since it has not done so in real time.

AzureTurbo-QueueList

As jobs complete (and their status reloads), the status will change from Queued to Processing to Completed.

info

NOTE: Job Status is not updated in real time, so you should select one or more jobs and choose the option "Reload Job Status" to view the current state.

Once it reaches the Completed state, the content should now have been migrated to SharePoint Online.  

For additional log details, select this or any completed job and choose the option View Job Log.

This will open the log file that the Migration API generated,, which includes a very detailed report pertaining to this operation.  
azure turbo mode 8

Supported Specification for Essentials Azure Turbo Mode

Essentials' Azure Turbo Mode utilizes Microsoft API, as Microsoft updates the API for both optimization as well as additional support, so too will Essentials be updated.

Currently supported and required:

·Azure Storage Account

oAn Azure Storage Account of your own is required.  If you already have a subscription then you can utilize it, however if you do not this may require an additional license that would be purchased from Microsoft.  Some Office 365 plans include Azure Storage, so check with your Plan or IT manager first.

oAs of the October 31, 2016 release, you may now choose between using your own Azure Provided Storage for this use or Microsoft's Provided Storage.  Please refer to this page for more information: Microsoft vs User Provided Storage.

·Content Only (but the rest still migrates too)

oThe SharePoint Online Migration API at this time is designed to handle content and content related attributes (metadata and item permissions) only.  Site creation, permissions, views, workflows, content types and countless other objects that makeup SharePoint will still be created using a number of other available APIs outside of this new functionality.  This means you should not expect to see an increase in performance around these other objects, but they will still be migrated the same as they were before or without the Azure Turbo Mode option.

·Queue Times and Processing

oWe don’t control the process, order or operation of the Azure queue.  Once Essentials submits the job to the queue, it has been completely handed over to the Microsoft function and we no longer have any ability to predict the order or processing times of any job.  In fact, once the Essentials log appears letting you know they have been queued, you can shut down our application and the queue will still process in Azure.  This means the job may immediately be picked up and processed or it may sit and wait for its turn before beginning (could be minutes or hours).

·File Size Limitation

oAt present the SharePoint Online Migration API only supports files up to 2GB in size.

Defer Upload to Azur

There are scenarios in which you would like to utilize another method (for example, AZ Copy) to upload your Azure Turbo packages to Azure - the Defer Upload to Azure option is designed to provide you with that flexibility.

The option is only available when Enable Azure Turbo has been selected (User Provided Storage only) and configured, and you must specifiy a local file share location which has enough available disk space to accommodate the size of all combined packages.

When enabled, the Azure Turbo function will still read and create packages from the content in your source location, but rather than upload it immediately (or in parallel) the packages are saved to your local storage to processing at a later time.  Once all packages have been created, you must then upload these files independent of the software. When all uploads are complete, use the software to queue the jobs to begin the import process.

Please review the steps below to properly enable and use the Defer Upload to Azure option:

1.Initiate the migration using the same method you perform when using Azure Turbo. (See the Azure Turbo Mode Migration section for more information)

2.Once successfully connected to your Azure storage account, check the Defer Upload to Azure option.
azure turbo mode 9

3.Click the Select button and choose a file location where the packages will be saved locally.  

·During the process, two folders will be created for each package, one containing the content and a second containing the manifest files.

·Each package will be up to approximately 125MB in size (depending on the amount of content being migrated), so please remember that there must be enough available disk space to accommodate all the packages.

·The total number of packages and their average size depends entirely on the amount of content that was included with this specific migration.  You will always have a minimum of 2 folders, but could have many, many more for larger migrations.
azure turbo mode 10

4.When the operation begins, you will observe the same migration process bar.  After all packages have been created, you can choose to view the log file by selecting "View Log" from the Summary pop up window. This will open the Log Viewer window which displays the queued results.
Azure Turbo Mode 12
 

5.Open the Azure Turbo Queue job list (See the Monitoring Azure Turbo Migration section on details about viewing the Azure Turbo Queue), all migrations that have been processed using the "Defer Upload to Azure" option will display a status of "Deferred".
AzureTurbo-DeferUpload-Queue2

6.At this time, you must now upload the content from your local drive to your Azure storage using your utility of choice.

info

NOTE: Job Status is not updated in real time, so you should select one or more jobs and choose the option "Reload Job Status" to view the current state.

AzureTurbo-DeferUpload-Containers2

7.After all the content from each folder has been successfully uploaded to the correct Azure storage container, refresh the Azure Turbo Queue job list again and the status should update from "Deferred" to "Pending".

8.Select one or more Pending jobs, right click and choose "Process Pending or Completed Jobs" to begin the import process.
AzureTurbo-Pending-ProcessJob

9.As the job(s) become queued in Azure, the status will change to "Queued". Over time, each Queued job will begin processing and once it has completed, the status will switch to the final stage of "Completed" and the content should now be available in your destination location.

Related Documents