I've seen recommendations to call FreeFileSync.exe with a batch job when a filesystem change has been detected by RealTimeSync, but on slow disks with 500,000+ files I can't simply run a batch job on all the files for each file change, because it scans the whole directory.
I thought that RealTimeSync would simply sync the files, but it just calls commands. Since calling a batch job would take much to long, is the recommended action to just call windows batch commands like copy and move depending on the value of %change_action% ?
This seems like what RealTimeSync should do for me, no?
I can code, but I'm not super familiar with batch or powershell so this will take me more than a moment to write. I just want to confirm that this feature is not available, and I cannot simply listen for changes and mirror the changes on the fly? If not, I think I might rather look for another program that can do it before I start writing a batch script to copy, move or delete and mirror the directory.
RealTimeSync just sync the changes?
- Posts: 4
- Joined: 17 Dec 2021
- Posts: 4
- Joined: 17 Dec 2021
Just for the tldr: How do I listen for single file changes and mirror the change on each individual file on the fly, instead of calling an entire batch job on a whole directory when a single file changes?
- Posts: 4
- Joined: 17 Dec 2021
I tested it out to make sure and it did what I expected. It scanned 500,000 files over an hour and a half and then immediately started scanning the files from the beginning.
I'm now testing out a batch script to see if I can sync things semi-manually but I've noticed that it's reporting a "Create" action on a "%change_path%" of "". So I don't quite understand that, what does it mean to create nothing? I guess I'll just ignore those.
I'm now testing out a batch script to see if I can sync things semi-manually but I've noticed that it's reporting a "Create" action on a "%change_path%" of "". So I don't quite understand that, what does it mean to create nothing? I guess I'll just ignore those.
-
- Posts: 2451
- Joined: 22 Aug 2012
RTS only launches its specified application (mostly FFS) after an idle time. Also make sure to read the Limitations.
So, RTS only knows a single name of a file that has changed, not names of all other files that may possibly have changed until the expiration of the idle time.
Furthermore, files may have changed while running an FFS sync or during other moments that RTS is not active, and hence only a full FFS Compare makes sure you covered all changes to be synced.
Having said that: if running a full Compare upon each detected change is objectional, consider chopping up your total FFS sync (and corresponding RTS task) in syncs with a smaller scope, each launched by a separate RTS task of a correspondingly smaller scope. See also here.
So, RTS only knows a single name of a file that has changed, not names of all other files that may possibly have changed until the expiration of the idle time.
Furthermore, files may have changed while running an FFS sync or during other moments that RTS is not active, and hence only a full FFS Compare makes sure you covered all changes to be synced.
Having said that: if running a full Compare upon each detected change is objectional, consider chopping up your total FFS sync (and corresponding RTS task) in syncs with a smaller scope, each launched by a separate RTS task of a correspondingly smaller scope. See also here.
- Posts: 4
- Joined: 17 Dec 2021
Thank you for the suggestion. There are a lot of directories and that might be cumbersome to set up, but I'll try it next time if need be.
I got too frustrated in the few days before you replied that I found an alternative solution for the entire reason I needed to sync files.
Thanks again and best wishes for the new year.
I got too frustrated in the few days before you replied that I found an alternative solution for the entire reason I needed to sync files.
Thanks again and best wishes for the new year.
