Any user of the Migration App.
If you have a long-running migration job where you’ve completed multiple commands over time, you may experience this. This is due to the job logs accumulating on your local Windows host machine. Once they have consumed all the available disk space, the Agent is no longer able to upload the most recent log, which stalls the migration job.
This is something we’re fixing in an upcoming build of the Agent. Meanwhile, there’s a simple fix. You can delete all logs associated with completed jobs that you no longer plan to continue running, and you may also remove logs for active jobs prior to the last three iterations.
The Solution: Phase 1
- On the Migration App Web UI, identify any migration jobs that you are no longer going to operate and copy their respective Job IDs with corresponding source and destination folder paths to a .txt file or spreadsheet. Keep this for future reference and troubleshooting.
- Using your notes, delete all these unnecessary migration jobs using the Delete Migration function in Web UI.
- On the Windows host machine where the Agent is installed, go to
- Open the egnyte-agent folder to view folders for each migration job, which are labeled with their migration job IDs.
- Delete folders for the jobs you have deleted from Migration App Web UI.
This may be sufficient to free up needed space, but if you have a lot of ongoing jobs, you will need to proceed to the next set of steps.
The Solution: Phase 2
For most users, Phase 1 of the Solution will fix your problem by removing all the local logs for unneeded migration jobs. However, some domains have multiple jobs that need True-Ups to continue running periodically over a longer period of time.
If you have completed Phase 1 and you are still concerned that there isn't enough local storage available on the Windows Host machine, you will need to proceed with Phase 2 steps. This entails recreating all your migration jobs so that you can delete all the historical logs and start with a clean slate.
- For jobs that are still needed, identify the biggest job logs by looking at the size of their local folders at C:\Users\[username]\AppData\Local\egnyte-agent
- Each folder is named with the individual migration job ID.
- Go to Migration App Web UI and create a new corresponding job for each folder pair that you need to continue working on (use the same source and the same destination).
- Perform Phase 1, Steps 1-5, for the original jobs to eliminate the extraneous job logs.
This will free up space on your host machine and allow you to continue running migration jobs.
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 screenshots 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.