I see many complains about a lost database (which I tested myself, and its horrible).
When database is lost, Duplicati need to build a new database by scanning all the backup files.
Why not adding option to store/backup the DB into the backup directory? (Can be stored/encrypted/zipped/etc)
This way, a Database rebuilding will be rarely made.
it is not hard to implement it (there is an option to run script after backup anyway, maybe this mechanism can be used)
Yes, that is unfortunate, and I hope to fix it.
The problem is that the database can become large, several GiBs, so simply adding it could cause some very large “extra” files to be uploaded.
We could work around that, but I think that it is more a workaround for a problem that is not supposed to be there.
If you want to try something like this, you can use the
--control-files option to inject files into the
dlist files. You can restore from the commandline using the
If we go this way, I would prefer that we do some kind of incremental/differential backup of the database data instead of just copying the database. The reason is that the database layout is wasting space in an attempt to be more efficient, and I would like it to be less space consuming.