I want to delete no longer used local database files to reduce space on the system disk.
It’s not obvious to me which database files are obsolete.
Welcome to the forum @krissy-jsc
You have to decide what you mean by obsolete, but anything still being used by backup will change (so have a new date) at that point. If you have some that are around for historical use, I suppose you could find them in GUI Database screen, which is another way to proceed. See which jobs you want, delete the unwanted.
If you use the command line interface, it will be harder to figure out what’s what…
Duplicati-server.sqlite files are GUI job settings. Random-letters.sqlite are for jobs. Databases with bak or backup (maybe translated if system doesn’t use English) are generally just-in-case backups when things like DB versions must be updated. Generally these grow stale quite fast (if backups continue) and will have old dates.
Deleting a job database that you find you need is in theory not a big deal, since the job database “should” be possible to recreate from destination files, but why risk it?
It sounds like you think you already know where databases are. If not, say what OS.
OS is Windows 10
attached you will find the list of all files in the duplicati directory
dirlist.zip (1.9 KB)
“Sicherung” is the German word for backup.
Can I delete all older files before 2024?
for all other files I have to look at the placement information of the local databse of all my active backup jobs whether they are still necessary. And the corresponding backup (Sicherung) files.
I hope I understood you right.
Most are Sicherung and have outlived their usefulness, as new versions exist.
While looking into “before 2024”, I think I saw some 2024 ones also obsoleted.
15.06.2022 17:47 283 installation.txt keep
13.04.2022 20:39 897.024 Sicherung FSUISASKMG 20220414020100.sqlite now at 26.03.2025 13:02
13.04.2022 14:00 178.069.504 Sicherung 82827586807289898588 20220414030000.sqlite now at 26.03.2025 14:00
13.04.2022 13:00 113.254.400 Sicherung 71797273817865846885 20220414020001.sqlite now at 26.03.2025 12:34
12.04.2022 22:30 432.992.256 Sicherung 90868170897267738878 20220414123800.sqlite now at 26.03.2025 22:31
12.04.2022 12:05 3.448.832 Sicherung HFRTNSFOCW 20220512010001.sqlite now at 13.03.2025 11:02
09.04.2022 14:30 65.921.024 Sicherung 65707875828779688669 20220416033000.sqlite now at 22.03.2025 14:38
15.02.2022 14:33 725.966.848 Sicherung 75878879677366848179 20220615083834.sqlite now at 26.03.2025 12:32
15.02.2022 14:24 392.228.864 Sicherung 87767279808975698881 20220615070023.sqlite now at 25.03.2025 17:25
15.02.2022 14:01 147.881.984 Sicherung 79898188877782748880 20220615065030.sqlite now at 25.03.2025 15:18
15.02.2022 13:57 40.214.528 Sicherung 68668384726986678489 20220615083317.sqlite now at 25.03.2025 15:00
15.02.2022 13:47 24.375.296 Sicherung 65836681857266677168 20220616013017.sqlite now at 02.11.2024 03:18 with size 34.263.040
15.02.2022 12:51 24.133.632 Sicherung 66698874777678708690 20220616014535.sqlite now at 25.03.2025 14:57
11.05.2021 19:40 151.552 CMNWFYSDOL.backup no longer in use
25.05.2020 13:00 929.792 Sicherung 83677990908685767966 20200526020029.sqlite no longer in use
29.09.2019 13:00 835.584 Sicherung 83677990908685767966 20191010120159.sqlite no longer in use
29.01.2019 14:00 109.137.920 Sicherung 20190130020000.sqlite unknown but old
29.01.2019 13:00 253.952 Sicherung 20190130014655.sqlite unknown but old
29.01.2019 13:00 56.848.384 Sicherung 20190130014653.sqlite unknown but old
29.01.2019 12:06 492.740.608 Sicherung 20190130121915.sqlite unknown but old
28.01.2019 16:45 245.248.000 Sicherung 20190129052335.sqlite unknown but old
26.01.2019 14:30 85.635.072 Sicherung 20190202035255.sqlite unknown but old
04.01.2019 13:46 86.106.112 Sicherung 20190130121913.sqlite unkownn but old
04.01.2019 13:26 87.040.000 Sicherung 20190202052255.sqlite unknown but old
04.01.2019 13:23 198.758.400 Sicherung 20190129033510.sqlite unknown but old
04.01.2019 13:09 13.533.184 Sicherung 20190129032613.sqlite unknown but old
04.01.2019 13:08 11.493.376 Sicherung 20190202015737.sqlite unknown but old
30.08.2018 09:40 131.072 87829072667471737087.sqlite no longer in use
Obsoleted backup versions generally have no value because they no longer match the destination (and they have to match the destination in order to be of much use).
Deleting a job by default (checkmarked) offers to delete the database for the job too. What it doesn’t do is find and delete the old database backup copies that lay around, which leads to the Sicherung ones which I marked as “no longer in use” so obsolete.
is more discussion (and links to other discussions) on improving the DB cleanups.
1 Like
Thanks for your support.
1 Like