So far, if I understand everything correctly, we can only have one backup set based on the folder where the backup repository is initialized for?
We can either just init it and get the prefs stored in the .duplicati folder at the root of the repository or use the -pref-dir option to save the preferences/filters etc. for the backup to another location than the root of the repository. But then we get a .duplicati file pointing to the folder defined using -pref-dir. That’s probably meant to be able to have all the backup prefs located close to each other which I quite like.
But I think we’re still limited to a single backup configuration per repository root folder, or did I miss something? We can’t just add a -pref-dir to all other commands and be able to have multiple backups/filterlists for the same root folder?
In my current situation f.i. I do have most of my relevant data in a common/projects folder - but within this I do have active folders I change multiple times a day and others that may be stable for weeks. Another one are the Outlook.pst files, even after a simple mailcheck it’s often usually around 100MB that have to be uploaded to the storage so a backup ever hour is a bit demanding compared with the rest of the changed files that might just be a few kb in a .txt file.
Please tell me if I missed something, or, if not, have you thought about adding the option to provide the -pref-dir for all commands?
Another option would be to just add a -filter option to the backup command, so instead of alway using the same filter file it would be possible to use different filters to define the files included in the backup (which, I guess, basically is the same as multiple backup sets, just rooted in a common repository)?