Migration App: Release Date: January 18, 2022
This product is currently in Limited Availability. We invite any customers interested in using the product to engage Egnyte Professional Services or their Customer Success Manager to have it enabled for their domain.
New Improved User Interface
With the most recent release of Migration App we have unveiled a new simplified User Interface (UI) that greatly reduces the number of clicks required of the Migration Operator. The UI also offers additional tooltips and context throughout the migration process.
The new UI includes metacommands that logically combine multiple discrete commands. Previously, the user had to remember to proactively execute these commands sequentially.
In the following table, it compares the old and new UIs for a standard migration job comprised of an initial Data Migration, Sanitization, two True-Ups and a Permissions Migration. In the old UI, it requires 13 atomic commands. In the new UI, the user need only initiate 5 metacommands and Migration App takes care of the rest.
|Old User Interface||New Simplified User Interface with Metacommands|
|Click 1||Create Migration Job||Click 1||Create Migration Job
- creates job
- scans source
|Click 2||Scan source|
|Click 3||Sanitize Source||Click 2||
|Click 4||Scan source|
|Click 5||Migrate Data|
|Click 6||Scan source||Click 3||
Migrate Data (True-Up #1)
|Click 7||Sanitize Source|
|Click 8||Migrate Data (True-Up #1)|
|Click 9||Scan Source||Click 4||Migrate Data (True-Up #2)
- scans source
- sanitizes data
- scans source
- migrates data
|Click 11||Scan Source|
|Click 12||Migrate Data (True-Up #2)||Click 5||
|Click 13||Migrate Permissions|
When you create a new migration job, if you do not want wait for the first scan to complete, you can stop the scan at any time. When you proceed to Migrate Data, the metacommand will take care of scanning the source.
Skip Scan Period
With the new UI, the Migration Operator never needs to manually scan the source, although they always have the option to do so. Remember with the old UI, you had to be sure to scan the source before you initiated data migration, true-ups or sanitization.
By default, a Skip Scan Period of 8 hours has been implemented. This means that if you successfully completed the scan as part of the first step and you proceed to Migrate Data in less than 8 hours, the initial source scan will be skipped. This is done to alleviate any unnecessary time delay for unnecessary scanning, as well as minimizing the logging and compute burden on the back end.
However, you have the option to request the Skip Scan Period to be modified to as little as zero, and up to 24 hours. If you wish to do this, simply submit a ticket to firstname.lastname@example.org.
Now you are offered the option to sanitize the source each time you initiate Migrate Data. However, if nothing needs to be sanitized on the source, Migration App will skip this step.
If you do not want to change file names on the source, do not opt in for sanitizing. However, be advised that if you do not run sanitize, those offending files and folders will NOT be migrated and you will have to handle them manually.
Job Size Limits
We have implemented Job Size limits that are quite liberal, but are designed to keep Migration Operators from getting into trouble with overly cumbersome projects that could more efficiently be handled in smaller batches.
We strongly recommend sizing your jobs at less than 2TB and 1M objects. Many larger migration jobs have been successfully completed, but they do take considerably more time.
Checking for Canonical Differences
Migration App now checks for canonical differences between the source and the destination during data migration. If there are differences, it terminates the command and displays an error message directing the user to a knowledge base article. This is designed to maintain data integrity and minimize unintentional data duplication or deletion.
A Folder with >50k Files Aborts the Job
If a scan detects more than 50,000 files in a folder on the source, it fails the scan command and displays an error message. This is in keeping with the limitations of the Egnyte Cloud itself. Previously, a folder exceeding this limit would simply stall and the Migration Operator would be left to troubleshoot the problem.
Additional Information and Resources
Questions? Feature Requests? Other Feedback?
If you have feature suggestions or requests, feel free to submit them here, and make sure you mention Migration App in the text.
For more complex requests that would benefit from providing screen shots or other attachments, you may submit them to email@example.com. Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.