Enhancement proposal of Versioning for backup needs.

[lokyo520]

Dear developer,

I am a designer who frequently needs to back up my design files and track the history versions of the files. I have noticed that FFS includes a very useful feature called Versioning, but it currently appears as an additional option within the synchronization settings and requires specific triggering conditions.

I would like to propose an improvement suggestion to make the Versioning feature more convenient to use. I would like to be able to set up a monitoring directory on left only and designate the right-side directory as the incremental backup folder. This way, when I make changes to files in the monitoring directory, the software can automatically save the new changes as files with timestamps and back them up in the right-side directory, allowing me to track and restore historical versions.

I believe this enhancement would make it easier for me and other designers to manage and protect our design files. It would be fantastic if you could consider this suggestion for future updates and provide the Versioning feature as a standalone option.

BTW, here is one more thing. I am a bit confused by the logic of the folder selecting. When I have a big folder A and I try to back it up in folder A' ,that works excellent. If I wanna to backup series folder in A to A' but not all of them, it seems I have to select B/C/D on the left side and create all the folder B' for B, C' for C, D' for D on the right side one by one: it has backup the files under the folder but not as a foler. So if I only give it a command of 'backup B/C/D to A', it sends the files under the folders to A' without create the folderB'/C'/D'. I notice it will be a big change and great infulence for the currently users. So I suggerst make it a selection but not as default.

Thank you very much for reading and considering my suggestion, and I look forward to your response.

Thank you!

[Plerry]

I am not the developer, but ...

Ad 1)
Note that FreeFileSync (FFS) is first and foremost a synchronization program.
As an added feature, FFS can move files that are overwritten or deleted by the sync to either the recycle-bin or to a Versioning location where, depending on your settings, you may be able to recover one or more previous versions.
However, FFS is not a full-fledged version control system. There is other, dedicated software for that purpose, like SVN and GIT.

Ad 2)
If folder A comprises e.g. folder B, C, D, E and F, you can use a single left-right base folder pair A <=> A', and then add E and F to the Exclude Filter.
Conversely, if folder A comprises e.g. folder B, C, D and E through Z, you can use a single left-right base folder pair A <=> A', and then add B, C and D to the Include Filter (replacing the default * =everything).
Simply use either of these two approaches, whichever best fits your use case.
In either case, FFS will then automatically create the folders B, C and D in A'

[lokyo520]

I am not the developer, but ...

Ad 1)
Note that FreeFileSync (FFS) is first and foremost a synchronization program.
As an added feature, FFS can move files that are overwritten or deleted by the sync to either the recycle-bin or to a Versioning location where, depending on your settings, you may be able to recover one or more previous versions.
However, FFS is not a full-fledged version control system. There is other, dedicated software for that purpose, like SVN and GIT.

Ad 2)
If folder A comprises e.g. folder B, C, D, E and F, you can use a single left-right base folder pair A <=> A', and then add E and F to the Exclude Filter.
Conversely, if folder A comprises e.g. folder B, C, D and E through Z, you can use a single left-right base folder pair A <=> A', and then add B, C and D to the Include Filter (replacing the default * =everything).
Simply use either of these two approaches, whichever best fits your use case.
In either case, FFS will then automatically create the folders B, C and D in A'

Thanks for Plerry!

Your suggetion of using Filter make sense for me. It works reliable and gives more option for users indeed.

And yes you're right. It is unreasonable to expect a synchornization software to resolve a versioning problem with an immature function. It may cause unexpect management issue when I have a tons of files. I have found Git or SVN are shells command in needed and rying Git GUI instead.

Your help was invaluable, thank you! :)

[xCSxXenon]

You should actually just use "File History" built into Windows. Unless you are wanting an indefinite version history, it is designed to do exactly what you describe.