right-click on the job in the Agent UI and select Open Archive (works only for Sync Jobs, only for macOS and Windows Agents) enable hidden items in the file browser and navigate to. File rename is not processed through the Archive. If a file is renamed on the source, it's re-synced to the destination agents on the next job run.If the Agent profile has the option "Delete files absent on source agent (Transfer jobs)" set to Yes, the deleted files are NOT placed in the Archive of the destination agents.Files updated on the source agent end up in the Archive of the destination agents only upon the next job run.Since transfer jobs are not continuously syncing (but rather a one-time file transfer), the Archive on destination agents works differently: With these Jobs, only the destination agents create. Others will move their current file to their Archive folder and download the updated file.Īn important note: the agent where the file was locally updated does not store the older file's version!Īrchive in Distribution and Consolidation jobs Upon change, the Agent will recheck the file and, if it has read-write permission in the job, it will upload the new version to other agents. An Agent understands that a file is updated if it receives a system notification about it or if it detects a change during the period folder scan. An Agent will consider a file to be deleted if the file is no longer located in its original place.Īn important note: the deleted file will not be moved to the Archive on the agent that originated the deletion! If an Agent deletes a file, other Agents will move the file from the syncing folder to their Archive. When an agent renames a file, other agents process it through the Archive: old_filename is moved to the Archive, and instead of re-downloading the new_filename, they take it out from the Archive. Files are kept there for 1 day only and this cannot be changed.Īrchive role in processing file renames and file deletionsįrom the system's point of view, renaming is equivalent to deleting old_filename and creating new_filename.Starting with v3.6.0 this parameter can be configured (as custom parameter) in a Job profile, setting is applied only to the certain job(s) with that profile.Īrchive on mobile devices works similarly with the following caveat: You can manually clear the Archive every now and then so as not to wait for automatic deletion. Decreasing this value makes sense if storage space is limited. The longer it's kept, the longer it takes storage space. Max archive file age (days): number of days a file remains in Archive until automatically removed.Bear in mind that this will require more storage space. Increase it if you work with big files and need to keep previous file versions. Max archive file size (MB): the max size of a file that will keep its versions in Archive.On versions prior to 2.12 change of this setting is not applied to currently existing sync job, it's applied to newly created jobs. Use Archive: disables/enables Archive at all.The archive's behavior is configured in the Agent's Profile: The archive can be a good source for restoring unintentionally deleted or modified files. This directory stores old versions of updated or deleted files: if an Agent updates a file, other Agents move their local copies to the Archive. Archive in Distribution and Consolidation jobsįolders selected for synchronization have a hidden. Archive role in processing file renames and file deletionsĤ.
0 Comments
Leave a Reply. |