If these changes are result of our own sync, they will produce no new changes to be synced.If changes occur during Analyze/Sync, they are still detected and sent to the next Analyze.We recommend to set it to at least 120 seconds (2 minutes), so that GoodSync does not start syncing until files were stable for at least 2 minutes. Note that if you had several changes (including changes performed by this or other sync jobs), the delay countdown will start with the last change that was detected. If not zero then GoodSync will wait this many seconds since the last change detected by On File Change, before starting the Analyze and Sync. If only one side of the job can be monitored, then GS will get changes only from one side.None of traditional server file systems can be monitored: FTP, SFTP, S3, SkyDrive, etc. Any of the above file systems, remotely accessed via GSTP protocol used in GS Connect.Windows shares, except some broken NAS shares that do not report changes.Windows File System, local disks, except root folder.These files systems can do file monitoring, so they can do On File Change Real Time Sync: Full Analyze is performed only on the first iteration of Real Time Sync.It Analyzes only files that were reported changed by file system, no full Analyze. Our new Real Time Sync mechanism performs On File Change synchronization: From the Goodsync website:Īnalyze and Sync this job when any file changes in left or right sync folder or its sub-folder. It appears one has to enable the “on file change” option for the real time sync function to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |