Hello!
On the FreeFileSync app, I put 10 files together and if I try to compare, it finds only the modified files from the available files so it works perfectly.
When I put the ffs_batch on RealTimeSync, it will not sync the available files and will keep waiting for all the files to be available first, even when I checked to ignore errors.
(so if I try to sync files A and B but only A is available, it works on FreeFileSync but not on RealTimeSync)
Did I miss something?
Thanks in advance,
Heckaa
Syncing even with not available files
- Posts: 2
- Joined: 26 Jan 2025
- Posts: 2517
- Joined: 22 Aug 2012
For clarity: RealTimeSync (RTS) monitors folders (and their subfolders) for changes; not specific files.
RTS will only do so if all folders in the RTS configuration are available.
This allows RTS to launch a FreeFileSync (FFS) sync when a drive or folder becomes available, e.g. by inserting a memory stick.
If you want RTS to launch syncs when part of you resources are not available, you should create multiple RTS configurations, one per resource that may be temporarily unavailable. And have RTS launch a specific sync associated with that resource.
E.g. have an RTS instance monitoring the folder comprising file A (and potentially the folder of its sync counterpart), and have that RTS instance launch a SyncA.ffs_batch FFS configuration.
And have separate RTS instance monitoring the folder comprising file B (and potentially the folder of its sync counterpart), and have that RTS instance launch a SyncB.ffs_batch FFS configuration.
Etcetera.
Obviously, the names SyncA.ffs_batch and SyncB.ffs_batch are arbitrary.
RTS will only do so if all folders in the RTS configuration are available.
This allows RTS to launch a FreeFileSync (FFS) sync when a drive or folder becomes available, e.g. by inserting a memory stick.
If you want RTS to launch syncs when part of you resources are not available, you should create multiple RTS configurations, one per resource that may be temporarily unavailable. And have RTS launch a specific sync associated with that resource.
E.g. have an RTS instance monitoring the folder comprising file A (and potentially the folder of its sync counterpart), and have that RTS instance launch a SyncA.ffs_batch FFS configuration.
And have separate RTS instance monitoring the folder comprising file B (and potentially the folder of its sync counterpart), and have that RTS instance launch a SyncB.ffs_batch FFS configuration.
Etcetera.
Obviously, the names SyncA.ffs_batch and SyncB.ffs_batch are arbitrary.
- Posts: 2
- Joined: 26 Jan 2025
Okay, perfect then, thank you!