FreeFileSync Version: 14.3 (Donation Edition)
Operating System: macOS
Issue Description:
I'm trying to sync Samsung phone photos with reused filenames using FreeFileSync's versioning feature to preserve conflicting files. The sync works, but the versioning folder doesn't preserve the original folder structure.
Configuration:
Comparison: File content
Sync Mode: Custom (due to database conflicts in Update mode)
Versioning: Enabled with %Date% macro
Versioning Path: /Volumes/16TB2/A_FreeFileSyncVersions/%Date%
Naming Convention: Replace
Expected Behavior:
When a conflicting file test.mp4 exists in subfolder FreeFileSync Test/, the versioned file should be saved as: /Volumes/16TB2/A_FreeFileSyncVersions/2025-07-07/FreeFileSync Test/test.mp4
Actual Behavior:
The versioned file is saved as: /Volumes/16TB2/A_FreeFileSyncVersions/2025-07-07/test.mp4
The original folder structure (FreeFileSync Test/) is lost, making it impossible to know where the versioned file originated.
Questions:
Is folder structure preservation expected to work in Custom sync mode?
Should I use Update mode instead, despite first-run database conflicts?
Is there a setting I'm missing to preserve folder structure in versioning?
Use Case:
Managing Samsung phone photos where filenames are reused for different images (e.g., multiple different photos named IMG_001.jpg).
Versioning folder structure not preserved in Custom sync mode
- Posts: 2
- Joined: 28 Jan 2024
-
- Posts: 2978
- Joined: 22 Aug 2012
Versioning is not/should not be sync variant dependent.
All files that are overwritten or deleted by the sync get Versioned.
If your left and right base location definition includes the FreeFileSyncTest folder FFS will/should sync (and Version) the contents of the FreeFileSyncTest folder, but not the FreeFileSyncTest folder itself.
So, then the described behavior is correct.
If your left and right base location definition is to the respective parents of the FreeFileSyncTest folder, FFS will/should sync (and Version) the contents of those parent folders, including the FreeFileSyncTest folder itself.
All files that are overwritten or deleted by the sync get Versioned.
If your left and right base location definition includes the FreeFileSyncTest folder FFS will/should sync (and Version) the contents of the FreeFileSyncTest folder, but not the FreeFileSyncTest folder itself.
So, then the described behavior is correct.
If your left and right base location definition is to the respective parents of the FreeFileSyncTest folder, FFS will/should sync (and Version) the contents of those parent folders, including the FreeFileSyncTest folder itself.