Feature Request: Versioning Updates

[DoS007]

Hello,
after some search for a backup solution I found FreeFileSync to be the best. It would be perfect, if it had an additional feature concerning versioning. At the moment (8.5) versioning is supported for deleted files.

The requested feature is about versioning updated files. See the attached picture. Because versioning would generate masses of data, after some time the versioned data needs to be deleted (after some time or after some run synch-starts). I think the feature request is clear, when there are further questions i can elaborate more informations.

Some additional notes:
- Currently there is one specified directory for versioned files in which the data is stored with the timestamp in name, e.g. ".../specifiedDir/peter-2016-09-25...jpg". In my opinion it would be better if it would be stored like ".../specifiedDir/2016-09-25 .../peter.jpg". The date would be unique for a backup process. This style of directory structure is more clearly (cause more files are versioned) when looking for specific state of e.g. two files in an old version. Versions of specific files are easy to find in this structure as well, due to easy search with e.g. windows explorer for file name.
- This could be also used for deleted files.

In my opinion this feature would make freefilesync even more rich in goodness. I appreciate feedback for the feature, thanks.

DoS007

[Plerry]

That option is already there.
Just look at option 3 in the manual page https://freefilesync.org/manual.php?topic=versioning
and use a macro to specify the format you want.

[DoS007]

Thanks, this does the job. For the deletion operation i write my own script.

Btw. when i start synching (cold start) it needs longer than compared to start synching a second time (warm start). The first one needs serverals seconds, the last needs one second? Why is that (in both cases there are no new files, just comparing)?

[Plerry]

I do not know your specific case, but ...
I have a use-case where I am running a sync against a NAS.
When I run a first sync, my NAS needs to de-hibernate, spinning up the disks.
On any subsequent sync the NAS is still "awake" and reacts faster.