New user here, liking Duplicati a lot but have come across some odd behaviour relating to file/folder selection.
I’m trying to back up an Adobe Lightroom Classic catalogue. This essentially comprises a file and folder both living in the same directory so I have: main.lrcat (the file) and main.lrcat-data (the folder) living in the \main\ folder. The lrcat-data folder is marked as a system folder. The file is about 3GB, the folder 5GB.
If I create a job with just the file - it works.
If I create a job with just the folder - it works.
If I create a job with both - then I ONLY get the file and not the folder. There is nothing in the log indicating any issue. I have no filters, advanced settings - just a plain vanilla job.
However, if I select the containing folder (Main\) and put an exclusion filter to get rid of the other cache folders that I don’t want backing up (using -*\*.lrdata\) then I do successfully get both the file and folder I do want.
So, while I have a working solution, this doesn’t explain why my original approach didn’t work. Any thoughts?
was a similar recent topic. I think the problem is in
It may think that a folder which starts with some other source is a subfolder.
It might just be a folder which starts with the name of a file, and not a folder.
This doesn’t seem to matter. Adding a filter may, as case is coded differently.
Any of the cases there will wind up saying something like this in Verbose log:
2026-08-19 09:41:18 -04 - [Verbose-Duplicati.Library.Main.Controller-RemovingSubfolderSource]: Removing source "C:\backup source\main\main.lrcat-data\" because it is a subfolder or subfile of "C:\backup source\main\main.lrcat"
I tested with a completely fresh example where I had a file and a folder which takes the root of the file name, and it only backs up the file and NOT the folder.
The log file has that “Removing source” line and I agree that the code snippet suggests that. Clearly just another manifestation of the other problem you referred to.
