- setup for RealTimeSync
- Capture_LI.jpg (367.32 KiB) Viewed 498 times
RealTimeSync not syncing
- Posts: 2
- Joined: 19 Apr 2018
I have RealTimeSync on a delay of 3,600 seconds (1 hour), but after the hour has passed, it does not activate the sync process. Is there some type of limit to the delay? or is it something something else?
-
- Posts: 2523
- Joined: 22 Aug 2012
With this setup, RealTimeSync (RTS) will only trigger the defined action (by default launching a FreeFilSync (FFS) sync) 3600 seconds after the last change in any of all the combined monitored folders (and their sub-folders).
Given the amount of folders and which folders are being monitored by this single RTS task, it is very likely that that point is never or hardly ever reached.
It might make sense to split the single RTS task in multiple RTS tasks, each such task monitoring a more limited and more coherent set of folders, and each launching a FFS task specific to the folders monitored by the individual RTS task.
E.g. make a RTS task to monitor J:\ (adding J:\ART, J:\ENGLISH, etc. does not make sense as those are part of J:\ and thus already monitored) and let that RTS task launch a FFS sync just for (parts of) J:\ .
But even then, any change anywhere in the folder tree of J:\ within 3600 second of the previous change will delay the launch of that FFS task for another 3600 seconds.
Similarly, defining the shown subfolders of VOLUME-2 is obsolete, as the entire VOLUME-2 is already monitored for changes. But, monitoring VOLUME-2 means, ANY change anywhere in the folder tree of VOLUME-2 will postpone launching your sync for a renewed 3600 seconds.
Given the amount of folders and which folders are being monitored by this single RTS task, it is very likely that that point is never or hardly ever reached.
It might make sense to split the single RTS task in multiple RTS tasks, each such task monitoring a more limited and more coherent set of folders, and each launching a FFS task specific to the folders monitored by the individual RTS task.
E.g. make a RTS task to monitor J:\ (adding J:\ART, J:\ENGLISH, etc. does not make sense as those are part of J:\ and thus already monitored) and let that RTS task launch a FFS sync just for (parts of) J:\ .
But even then, any change anywhere in the folder tree of J:\ within 3600 second of the previous change will delay the launch of that FFS task for another 3600 seconds.
Similarly, defining the shown subfolders of VOLUME-2 is obsolete, as the entire VOLUME-2 is already monitored for changes. But, monitoring VOLUME-2 means, ANY change anywhere in the folder tree of VOLUME-2 will postpone launching your sync for a renewed 3600 seconds.
- Posts: 7
- Joined: 24 Apr 2018
Solution: if auto sync not run - reduce idle setting until sync work
read viewtopic.php?t=5153
read viewtopic.php?t=5153
