Audience
Any user of the Migration App.
What's the Cause of the Error #629 Message?
There are hard limits on the number of files and data size for migration jobs. These limits vary by domain, but the default size is 10TB of data and 15 million files.
However, we strongly recommend that all migration jobs be broken down into smaller subsets of no more than 10TB and 15 million files. This will avoid any potential conflict if the data set increases before finishing the migration project.
This is not a limitation of Migration App, but an operational limitation intended to minimize problems frequently encountered by larger jobs that have not been optimized.
How To Remedy This?
If a given job runs a scan and subsequently receives the error message below, the job will not proceed.
"(Error #629) We're sorry, but this job cannot be run because it exceeds the maximum threshold for the number of files, data size, or both. Please review the results of the Scan..."
If this error message appears, several options are available to rectify it:
- Engage Egnyte Professional Services to manage the entire migration in a white-glove manner.
If engaging Professional Services is not preferred, a few alternative solutions are available: - IF THIS IS A NEW MIGRATION JOB and migration of data has not yet started, the best option is to restructure the data at the source to be within the domain's job limits. Depending on how this is accomplished, re-run the scan and proceed with migration. In some cases, a new migration job may need to be created.
- IF THIS IS AN IN-PROGRESS MIGRATION JOB and migration has already started, do not restructure the data on the source. This would result in creating duplicate content, or potentially deleting content the next time a True-Up is run. If this is the case, please open a ticket by sending an email to support@egnyte.com with the following information:
- Subject: Ongoing Migration Hitting Job Limits
- Include the domain name and the migration job ID
Egnyte support will assist in determining the most effective path forward.
For more guidance around how to structure jobs for migration, see Best Practices for Creating an Egnyte Folder Structure. Also read Best Practices for Migrating Data into Egnyte Using Migration App.
Questions? Feature Requests? Other Feedback?
For any feature suggestions or requests, feel free to submit them here, and make sure to mention Migration App in the text.
For more complex requests that would benefit from providing screenshots or other attachments, submit them to support@egnyte.com. Be sure to include Migration App in the email title. Our Support team will push the comments to the Product team for consideration.