In course of transferring files Agents perform a range of background operations to read and write the files. Knowing these greatly helps to correctly evaluate the progress on a job run. For example, if a job run seems to be stuck, check whether the Agent is busy with some other tasks on files.
The list of Agent's activities can be seen in Jobs - > Job Runs -> (Select desired Job name ) -> Agents -> (Select an Agent) -> Activity.
(Not available for Script jobs)
This table shows the Agents' activity, the number of pending operations (see below), and the details on each of the activities. Empty details imply that the current Agent operation is not being performed at the moment.
The pending operations does not correspond to the number of files yet to be processed, but is the number of internal Agent operations. Seeing the pending queue change means that Agent is functioning normally.
Checking file blocks
Before uploading a file, the Agent will check the local copy, read its pieces, and hash them. Simultaneously you will see Hashing file operations.
The receiving Agent will check the local file blocks when it needs to download some file pieces. At the same time it will show some hashing, and reading file operations.
Copying local file blocks
Means that Agent does not re-download file but instead searches through the local files and copies them, piece by piece. May cause increased disk usage. Read more about this feature here.
(The pending queue does not appear for this operation)
Hashing file
Means that Agent calculates the file hash. It will do so right when transferring the file. Also, all files are hashed for a newly created job if custom parameter lazy_indexing in OFF in Agent profile. After disabling the parameter, new files in an already created job will also be hashed before syncing.
Also, receiving Agents will be hashing their local files for pre-seeded folders (apart from Read-Only Agents). When files are being hashed it's OK to see disk and CPU usage increase.
Merging folder tree
Each of the Agents exchange and compare their files/folders metadata to verify which of them need to be synced. Syncing speed may be slower if Agent performs merge at the moment. Merging may fail if a files or subdirectory cannot be rechecked (for example, folder tree changed during merge ). Agent will attempt to merge it again.
Processing Archive
Appeared in Resilio Connect v3.0.0. This operation means that the Agent is either moving to or copying files from the Archive. Usually it's a quick operation, but in case of massive files move, rename or deletion on a remote Agent, others will require some time to have it processed. During this, the job itself may seem as if stuck, which is actually not true.
Processing file attributes
Appears on agents that receive files and apply NTFS permissions or POSIX ACL. This operation may delay other agent's threads. If the operation hangs for a reason or agent fails to apply the permissions due to lack of access, e.g., a corresponding error will appear.
Reading file from disk
The Agent reads the file while uploading it to other Agents. It will read and hash the file at the same time if lazy_indexing in set to ON.
Resource usage
Shows disk usage (sum of IO threads load) and the main Agent working thread load (mt).
(The pending queue does not appear for this operation)
Running script
This means that an Agent is executing one of the triggers in a Consolidation or Distribution job.
(The pending queue does not appear for this operation)
Scanning files
Basically it’s a list of files that will be uploaded marking their size, timestamp, and acl. The Agent scans the files in folder right after it has been added to a job (initial folder scan). It will later hash and read files when once it starts uploading them. This operation will also appear if new files are added to the folder.
This operation also appears when an Agent performs its' periodic folder scan.
Transferring
The data transfer itself. Shows the upload and download speed in bits per second (bps).
The pending queue shows the socket queue that's pending for upload (not download). It's not the total bytes yet to be synced.
Writing file to disk
The Agent writes the downloaded or locally copied file pieces to disk. This appears when an Agent is copying local file blocks.