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

Hyper Migration

The Hyper Migration Tab is where all hyper migration jobs are saved and displayed.

info

NOTE:

·Hyper Migration is currently only available for Migrations where the source is Dropbox, FileShare, Box, OneDrive, or Google Drives.

·Truncating Long Paths in Hyper Migration works only for folders, file names are not changed. There are no overflow folders, no changes to folder structure, and no MD5 checked sum algorithms - the folder names are simply cut down to 400 characters.

 
Drives Hyper Migration 2
 

Column Title

Description

Icon

Indicates whether the migration was successful. A green check-mark indicates a successful migration. A Pause icon indicates that the migration was either paused or some of the items failed to migrate.

Hyper Migration Type

Indicates the type of migration that was used.

Started

Indicates when the migration was started for each user.

Source User

Indicates the source user or path.

Target User

Indicates the target user or path.

Summary Record

Is a summary of the content that was migrated - this includes the successful, warning, and failed states for migrated content, as well as size and duration information.

Duration

Indicates the time spent on the migration. If it is an Azure Turbo Synchronized migration, then a double record will appear - indicating the time spent on creating the Azure Turbo job and the uploading of the content to Azure, as well as the time spent for Azure Turbo to finish and refresh its logs.

Recommended Configuration

In order for Essentials Drives to provide optimal performance on your hyper migrations, it is recommended that users set the configuration settings based on their work machine's hardware and Ethernet connection.  These settings can be accessed in the Essentials.ini file, where the Essentials tool is installed (C:\Program Files\Quest\Essentials\Essentials.ini).

The following are the settings available for configuration:

· -DeMigrationPoolSize: This is the number of parallel threads that the tool will run to read from the source and then upload to the target. Note that this value is used for both 'Read from source' and 'Write to target' operations while in CSOM mode, while only for Read operations when in Azure Turbo mode. It is critical that resources are allocated appropriate (CPU, RAM and Internet speed) to match an increase of thread count since the content size increases rapidly as each thread load is multiplied by the Chunk Size settings.

·-DeMigrationChunkSize: This number dictates how many packages are to be copied from the source and then uploaded to the target in one thread. Note that this value is used for both 'Read from source' and 'Write to target' operations while in CSOM mode, while only for Read operations when in Azure Turbo mode.

·-DazurePacketMaxCapacity: This value is used for 'Write to target' operations while in Azure Turbo mode. This number dictates how many objects are to be created in Azure Storage within one package. Ensure that the number of packages are limited to have less than 1000 objects and have less than 100MB within each package. This will result in a faster upload speed to Azure.

·-DazureBatchingUploadThreads: This value is used for 'Write to target' operations while in Azure Turbo mode. This number dictates how many parallel threads are to be uploaded to Azure Storage. Again, this value will change depending on CPU, RAM and Internet speed.

It is also recommended that you reserve more RAM for the Essentials tool, particularly for hyper migration purposes, setting the RAM at 8GB-16GB. See the Memory Management section for an overview of how to manage the memory used by Essentials.

 

 

 

 

Intelligent Permissions Migration

Intelligent Permission MIgration

We recommend that you set up your environment to allow for Intelligent Permission Migration. Do so from within the Profile Manager, under the Hyper Migration/Backup tab.

intelligent permissions migration 1

 

Intelligent permissions migration performs a comparison of the permissions of the parent object (folder) and child objects (sub-folders or files) on the source environment. If permissions are the same, it will not break permission inheritance on Office 365 locations. Intelligent permissions migration gets lists of source object users/groups and child object users/groups and if these users/groups are the same, the tool compares permission levels. This will help significantly reduce the issue often seen when migrating file level permissions with Box, Dropbox, Google and File Shares.

 

info

NOTE: Intelligent permissions migration does not limit the number for unique permissions scopes. Target locations may still have more than 50K unique permissions scopes because of source environment structure, even after "Intelligent permissions migration" settings are applied.

OneDrive to OneDrive Hyper Migration Configuration

OneDrive to OneDrive Hyper Migration

 

In order to perform OneDrive to OneDrive using the Hyper Migration feature, you must first activate the feature through the Profile Manager, by selecting "OneDrive to Onedrive" under the Hyper Migration\Backup Tab, in the Hyper Advanced Options section.

 

onedrive to onedrive hyper migration 1

 

Select Apply to apply the changes.

Related Documents