Hoping to get some help on a rather specific database management issue…
Duplicati ran multiple backup jobs for an external USB drive which was not connected at the time. As a result, Duplicati thought that all of the files had been deleted and now shows “Source: 0 bytes” on the backup overview.
This drive has 3.5tb of data on it, so the backup tasks can take quite a long time. Is there a way to remove the unwanted backup dates from the Duplicati database so that it doesn’t have to un-necessarily re-scan all the files when it next runs?
I tried looking for posts about this particular case, but everything I found was about deleting the actual backed up files, not the Duplicati Database.
About my system:
Ubuntu 22.04
Linuxserver docker image of Duplicati v2.0.8.1_beta_2024-05-07
There are different places where the metadata is stored: The display on the UI list of all backups is stored in the same place where all the backup configurations are (in the server), while each backup job has its independent database as well. It will only be a problem if you have the empty backups in the actual job database. To check this, you should go on the restore page and see whether the most recent version is actually empty.
If this is the case, you can delete the empty version using the GUI command line. You should use delete <backup URL> --version=0 to delete the latest version. The backup URL should already be filled in on the page, just make sure to remove the other advanced options and the file paths that are in the second text box. There should only be one empty version in the backup, because unchanged data is not recorded as a new version.