Restarting the job on Agents

Restarting the Job on an Agent can help resolving the following issues:

• Database errors
• Share's identifying errors
• Missing folder errors
• Forcing an Agent to re-download data in Distribution Jobs without having to restart the Job Run.

You can restart a Synchronization Job, a completed or an active Distribution, Consolidation or Script Job Run. Note that restarting the latter will create a new Job Run.

Reference Agents

You cannot initiate a restart on a Reference Agent. To do that, temporarily assign Reference Agent duties to a different Agent, initiate the restart, then re-assign the Reference Agent role to the Agent in question.

Restarting a Job on an Agent:

• Deletes database files (.db, files.db and sf.db) associated with the Job Run and create new ones. If there are a lot of files and/or a lot of Agents in the Job, it will take time for the restarted Agent to scan the files and merge the folder tree with others, days for tens of millions of files.
• Deletes .sync/ID and part files .!sync. New .sync/ID will be created. The partially downloaded files will be downloaded as new.
• Preserves IgnoreList, StreamsList, Archive and other files inside the .sync folder apart from those mentioned above.

Note

This action will produce two events in the job run - Agent was removed from the Job and added back.

Restarting a completed Job Run for an Agent has some peculiarities. If only destination Agent(s) is selected, all sources will be automatically added to the new Job Run. Same if only source Agent(s) was selected - all destinations from the Job will be added to the new Job Run.

Restarting the Job Run where data transfer is complete, but the Agent is still executing a "After all Agents complete downloading" script is not supported and gives an error.

Full re-indexing

As a side effect, the Agent will have to build indices for all files within Job from scratch. If the Job contains millions of files that may take significant time to perform re-indexing.

The Agent remains in Job Run even if the restarting process takes long time. While the Agent is being restarted it will report loading status in the Job Run.