Interface Overview
The application consists of two primary panes: (1) Navigator and (2) Contents/Objects Area. The primary focus of this area is a set of wizards that are displayed when selecting the required operation from the ribbon. A complete listing and description of these wizards is in a separate section of the manual labeled Common Functions.
The navigator can be loaded with individual or enterprise level drives that allow for simple drag and drop migrations between several of these Drive locations.
The Drive's tab also gives you access to a Progress tab, also located in the contents pane area, under the Progress tab. This tab has detailed information about each single current user migration status. For more information about the progress bar see this section.
The Drive's tab also gives you access to a Hyper Migration tab, also located in the Contents pane area, under the Hyper Migration tab. This tab is where all hyper migration jobs are saved, displayed, and managed. For more information on managing your Hyper Migrations, please see this section.
|
|
NOTE: Hyper Migration is currently only available for Migrations where the source is Dropbox, FileShare, or Box. |
Migration Job Structure
The Migration Tab within the Drives Tab, is where all Drive jobs are saved and displayed.
|
|
NOTE: ·Hyper Migration is currently only available for Migrations where the source is Dropbox, FileShare, Box, OneDrive, Google Drives, or Google Shared 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. |
|
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 paused. A red X indicates an item failed to migrate. |
|
Project Name |
The Project Name. If no project name was assigned this column will be blank. |
|
Source |
The source user or path. If an account is not using OAuth then it will say (Basic) by source name. |
|
Target |
The target user or path. |
|
Type |
The type of job performed, whether it be migration or a csv creation etc. |
|
Started |
The date and time the operation was started. |
|
Finished |
The date and time the operation completed. |
|
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 |
This is 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.
Connecting to Resources
In order to be able to use the Metalogix Essentials Content and Navigator panes in order to copy the contents of your various Drives by dragging and dropping, you will first need to connect to them within Essentials. The following are detailed steps on how to connect to your respective Drives.