Enable FreeFilySync to keep track all file operations at sources.
Then, when it's synchronization time, it doesn't has to compare
the complete source with destination, but only perform the logged
operations on it's list.
Typically there will be only a small percentage of source data
that has to be copied. And - to my experience - the traversing
and comparing ALL data (even it's only filetime and size) takes
more than 90% of the time.
Much quicker, less HD stress, etc.
(Impl. probably with FileSystemWatch. The list will have to be
kept coherent due to entry dependencies...)
[Feature Request] "A-priori mode"
- Posts: 36
- Joined: 30 Jun 2025
- Posts: 36
- Joined: 30 Jun 2025
Addendum:
I just realized that your so-called "Realtime Sync" is somewhat
similiar in what I described above.
(I didn't have a look at it as I took it literal by it's name:
Realtime Sync = Permanent Sync; i.e. kind of RAID etc.)
But what I actually mean is better described by something like
"delayed sync of realtime logging".
If I get your RTS right then it doesn't allow
- more than one folder pair.
- the specific filters of FreeFileSync.
- manual activation of sync of the collected actions.
Use case:
Mirror some folders (with potential exclusions of files/ subfolders).
Destination: external HDD, not connected but for special tasks (i.e. mirroring).
When I want to mirror the collected changes, I connect the HDD,
and then manually start Synchronize.
If I get it right, this isn't possible so far?
I just realized that your so-called "Realtime Sync" is somewhat
similiar in what I described above.
(I didn't have a look at it as I took it literal by it's name:
Realtime Sync = Permanent Sync; i.e. kind of RAID etc.)
But what I actually mean is better described by something like
"delayed sync of realtime logging".
If I get your RTS right then it doesn't allow
- more than one folder pair.
- the specific filters of FreeFileSync.
- manual activation of sync of the collected actions.
Use case:
Mirror some folders (with potential exclusions of files/ subfolders).
Destination: external HDD, not connected but for special tasks (i.e. mirroring).
When I want to mirror the collected changes, I connect the HDD,
and then manually start Synchronize.
If I get it right, this isn't possible so far?
-
- Posts: 2946
- Joined: 22 Aug 2012
Regarding your 1st post:
> Enable FreeFilySync to keep track all file operations at sources.
This would require that FreeFileSync (FFS) is continuously active,
and not just upon being launched manually, time or event scheduled, or by another application (like e.g. RealTimeSync, RTS).
It would mean a dramatic change in the FFS concept and approach, and only would work for a limited amount of use cases (changes only occurring at one side).
Do not expect this to happen.
Regarding your 2nd post:
> (I didn't have a look at it as I took it literal by it's name
Then you better DO take a look at the RTS manual page1 and page2, and e.g. also read this, and pehaps view the RTS tutorial video
> If I get your RTS right then it doesn't allow
> - more than one folder pair.
RTS does not monitor folder pairs, but can monitor as much folders as you want
> - the specific filters of FreeFileSync.
RTS can be used to launch any specified application upon detecting changes in its monitored directories, not just FFS. RTS does/can not observe the in- and/or exclude filter rules as specified for an FFS sync.
> - manual activation of sync of the collected actions.
It would be a bit uncommen use of RTS, but if you specify RTS to launch FFS to run a *.ffs_gui sync configuration, rather than a *.ffs_batch sync configuration, you can review the FFS Compare results and, if OK, start the actual sync manually.
> Enable FreeFilySync to keep track all file operations at sources.
This would require that FreeFileSync (FFS) is continuously active,
and not just upon being launched manually, time or event scheduled, or by another application (like e.g. RealTimeSync, RTS).
It would mean a dramatic change in the FFS concept and approach, and only would work for a limited amount of use cases (changes only occurring at one side).
Do not expect this to happen.
Regarding your 2nd post:
> (I didn't have a look at it as I took it literal by it's name
Then you better DO take a look at the RTS manual page1 and page2, and e.g. also read this, and pehaps view the RTS tutorial video
> If I get your RTS right then it doesn't allow
> - more than one folder pair.
RTS does not monitor folder pairs, but can monitor as much folders as you want
> - the specific filters of FreeFileSync.
RTS can be used to launch any specified application upon detecting changes in its monitored directories, not just FFS. RTS does/can not observe the in- and/or exclude filter rules as specified for an FFS sync.
> - manual activation of sync of the collected actions.
It would be a bit uncommen use of RTS, but if you specify RTS to launch FFS to run a *.ffs_gui sync configuration, rather than a *.ffs_batch sync configuration, you can review the FFS Compare results and, if OK, start the actual sync manually.
- Posts: 36
- Joined: 30 Jun 2025
Thank you for your detailed reply.
I think I understand the concepts of FFS and RTS now
(already having found the RTS manual :) ).
If I get it right, my idea of a "delayed (and manually started) sync of realtime logging"
all in all can't be accomplished, as I can not specify filters (e.g. exclude files/ filetypes/ directories etc.)
for RTS logging.
Everything else would be possible already (?).
I think I understand the concepts of FFS and RTS now
(already having found the RTS manual :) ).
If I get it right, my idea of a "delayed (and manually started) sync of realtime logging"
all in all can't be accomplished, as I can not specify filters (e.g. exclude files/ filetypes/ directories etc.)
for RTS logging.
Everything else would be possible already (?).
