I have an ffs_batch to sync multiple folder pairs with versioning (TimeStamp-File) to a dedicated folder. Since there is one versioning config for the batch (<VersioningFolder...>) but multiple folder pairs changes to files on the root of each folder pair are mixed together at the root of the versioning folder. Unless I've configured something wrong, I believe the Versioning should create a subfolder per folder pair at the defined root. With each pair in one batch versioning to one root folder, this could potentially cause conflicts or lower retention count than expected when different folder pairs happen to have files named the same not to mention the merging of unrelated files.
As a work around I can create one ffs_batch per folder pair but since my use case is to use RealTimeSync I would have quite a few instances of RTS running filling up the system tray. :) Not very scaleable.
Thanks!
Mixed file version files when syncing multiple folder pairs in one batch
- Posts: 2
- Joined: 11 Dec 2024
-
- Posts: 2946
- Joined: 22 Aug 2012
If you want to define a specific versioning location for distinct (or all) left-right base folder pairs, via the right gear-icon in between a base folder pair you can define local Synchronization Settings, including a Versioning location, as opposed to the Versioning location defined in the Global Synchronization Settings (F8), via the green gear-icon above your right-side base locations(s).
- Posts: 1
- Joined: 2 Jan 2025
Thanks for the tip Plerry. I was just searching for solutions to the exact same problem. You've described a reasonable workaround which I'll use for the time being, although it is quite tedious to do for a couple of dozen folders. (And also remembering to update them if the source folder changes.)
It would be good if there was an easier way to accomplish this. Perhaps if there were some additional macros that specified the current source folder, then that could be used in the versioning path without having to specifically override each one.
For example, if I was currently syncing "C:\FolderA", the macro variables would be:
I could then specify the versioning path as "D:\Backups\Past Versions\%SourceFolderName%" or "D:\Backups\Past Versions\%SourceFolderPathSanitized%" and each source folder would be placed in its own unique location.
If something like those are not already available, where can I make a feature request for them?
It would be good if there was an easier way to accomplish this. Perhaps if there were some additional macros that specified the current source folder, then that could be used in the versioning path without having to specifically override each one.
For example, if I was currently syncing "C:\FolderA", the macro variables would be:
%SourceFolderName% = FolderA
%SourceFolderPath% = C:\FolderA
%SourceFolderPathSanitized% = C\FolderA
I could then specify the versioning path as "D:\Backups\Past Versions\%SourceFolderName%" or "D:\Backups\Past Versions\%SourceFolderPathSanitized%" and each source folder would be placed in its own unique location.
If something like those are not already available, where can I make a feature request for them?
- Posts: 2
- Joined: 11 Dec 2024
Thanks Plerry. Perfect solution for me. I figured I was missing something. :)