Recommended for experienced users of Migration App.
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.
Various customizable advanced configuration requirements have been identified for Migration App, particularly in the interest of reaching feature parity with our legacy migration tools -- CMM VM and CMM Agent CLI. We have established a process where a JSON file may be uploaded to the Agent from the Settings section of the Migration Dashboard, which can customize certain settings for the source
Initially, we are offering the ability to control the number of threads used to run jobs. The standard configuration is 4 transfers and 8 checkers. You can decrease or increase the number of transfers and checkers with a custom configuration (from 1 to 20, inclusive), assuming your Windows host machine has the compute power to handle it.
Requesting Advanced Mode for a Domain
Advanced Mode is not enabled by default for all domains. Enabling it requires a settings update on the Egnyte back end. You may request Advanced Mode by submitting a ticket to email@example.com. Please allow 2-3 business days for enablement.
- When you introduce a custom configuration file, if a command is running on a job, the custom settings will not impact that command. Only when you initiate a new command will the custom settings take effect.
- You must select a configName in the JSON file, or it will not upload.
- You can delete a Custom Configuration from the settings by clicking the trash can icon.
How do I change the threads for Migration App jobs?
- From the Migration Dashboard top menu, click on Settings.
- From the list of Available Sources, select the Agent you want to customize.
- From the Source Settings, note that it is currently indicating that no custom configuration is in place. To customize it, click Download Default Configuration File.
- Open the JSON file in Atom or another editor. The default file lists 4 transfers and 8 checkers.
In the editor, change the transfers and checkers to the desired number. You also need to give it a custom configName. You can name it anything you want, but it's a good practice to indicate what settings you specified in the file. Save the JSON file without changing the name Configuration.json.
Guidance for the number of transfers vs. checkers is that you should generally have 2:1 ratio. And the number of threads is limited by the number of cores on the host machine CPU. So keep this in mind if you're going to be running multiple jobs concurrently.
- Return to the Source Settings, and either drag and drop the file or upload it. Now the Source Settings will have some new information displayed. Notice the Custom Configuration name MyConfig-8Ts-16Cs is the name specified in the JSON file.
If you want to delete the Custom Configuration and return the job to default settings, click the trash can icon to the right of the name.
- Return to the Migration Dashboard and select any migration job created for that Source. You can now see that the job reflects a Custom Configuration with the name you provided.
Applying a Custom Configuration will impact all migration jobs created for that Source.
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 firstname.lastname@example.org. Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.