It is critical if all the Agents are on Windows OS and if parameter Resolve filename system conflicts is False in the Agents' Profiles. Creating a job with files/folders of different letter case on different Agents The Resilio Agent will switch to the new directory and will sync the files there: propagate file deletions or file updates to other agents.ĥ) Renaming a file/folder on Windows Agents- changing only letter case. Similar to case 3, but instead of removing the owning Resilio Agent from the job, its path in the job is changed. In this case, the Resilio Agent will check the files and since this is the latest file update, deleted files will be propagated to others.Ĥ) Changing folder path in the job for a Resilio Agent the Resilio Agent is added back to the same job again. Nothing is done to the files on other Agents. this Resilio Agent is removed from the job and after that files are removed from the folder on this Resilio Agent's storage. files are updated on a Resilio Agent and they are synced up with others in a job Therefore the following steps may lead to propagated file deletion: Even though an owning Agent may be already removed from the job, the others still know that the latest file version was made there and will be trying to receive it, until the file is updated somewhere else.
This file version is a reference file version that all other Agents are trying to receive. In a job, all Agents know on which of them the file was edited last. The Resilio Agent has built-in validation to avoid this in some, but not all possible cases. The operating system does not immediately inform the application that the storage is no longer available and until this happens some files may be considered deleted as they are no longer visible to the Resilio Agent on disk. While the Resilio Agent is in any way working with files - is scanning them, uploading, or downloading.
#Resilio sync pieces archive#
It will be required to restore files from the Archive manually.Ģ) Ungraceful ejection or disconnecting of an attached storage Agents won't be able to restore it from Archive since they don't know the file hash, and won't be able to redownload it from the source. Otherwise, if a placeholder is renamed, the corresponding file on a remote Agent will be moved to Archive. Check with Resilio Admin that parameter lazy_indexing in the Profile is set to No/false. For this to be possible, the Resilio Agent needs to know the file hash (see here for more details).īecause of this peculiarity, renames must be done with the utmost care on TSS shares, especially bulk renames of subfolders with a lot of files inside. Renames are processed through the Archive where an Agent first places a file and then restores it without re-downloading over the network. File content and its hash remain the same. Here are some of those examples:įrom a technical point of view, a rename is seen by the Agent as deleting a file with the old name and creating a new file with a new name on the file storage.
To undo those deletions will require manually restoring files from the Archive.
#Resilio sync pieces code#
In this case, the Resilio Agents with Read-Write access in a job will propagate this file deletion to others.ĭespite the fact that a number of validations are implemented in the Resilio Agent code in order to ensure that the file is indeed deleted and avoid false-positive occurrences, there could still be some cases when this is a valid file deletion for the Resilio Agent. But it can, during a folder scan, discover that a file is no longer present in its location or be notified by the operating system about file deletions. It's important to understand that the Resilio Agent itself is technically not capable of making a decision to delete a file from the storage.
0 kommentar(er)
