I made two backup configurations. Not sure that they include no common files. How can I find out easily? What if in fact there is a file common to both?
This question I ask for two reasons:
- Such a case makes a priori little sense (at least: waste of execution time and storage space)
- More important: I guess that such a situation might make problems, may-be at executing one of the backups and even more in case of a restore. Is this guess justified?
To find out, an unpractical way is to choose “modify” (first one config, then the other) until one is on the page about file selection where one can go into details but risks to oversee that a green mark on a folder might not mean that all contents of it has been selected - theoretically it is a “tree” of subfolders to explore. Forgetting the special purpose (look only, no change) one could be tempted to change something in this “opportunity” BTW isn’t changing the selection nearly always risky? Which changes are for sure not creating potential problems? (End of btw)
Moreover the selection shown might be ambiguous: if all subitems of a folder (i.e. files and subfolders contained in the folder) are marked, that might mean: everything in the folder is selected including future content (which will be backed up too after its creation by the same config.) OR only the current content of the folder is selected (and future content will be ignored at execution of the backup config. until this is completed to include the new items). I wonder whether these two possibilities exist. In case only the second one exists, no ambiguity, but this I would describe by saying Duplicati is strictly file-oriented, there is no folder-orientation.and this would be unpractical: imagine for ex.: I open a new period (year) in my accounting SW, which creates a new file and I forget to add it to the backup config. that backs up the older years - and this file will not be protected against losses by backup!
I hoped that using Duplicati from the Command Line might help here - both for my basic question in the title and the mentioned ambiguity - but what is written about that usage in the manual doesn’t seem to confirm this hope, and it doesn’t work any way: the command Duplicati.CommandLine.exe
issues a message that this thing is not found. BTW finding a place to enter such command lines took me much time on my Windows 11 which hides it while it was so simple before (for single commands) so accessing to what they call the Windows shell will again take much time if I try again.