Storage being filled up

Hey,

I already checked several threads regarding this issue but it seems like none matches mine.

The instance on my home server is slowly filling up my drive. I use Duplicati in Docker.
The Duplicati config directory uses 141GB with just 2 Backup Plans and the file dates are even from 2020 and 2019.

The version is 2.0.6.3_beta_2021-06-17.
And I even added auto-cleanup to each plan without any success.

This is the folder:

-rw-------  1 root root 1.5G Oct 13 07:00  UCXUKVJSMS.sqlite
-rw-------  1 root root 5.6M Oct 13 07:00  UCXUKVJSMS.sqlite-journal
-rw-------  1 root root 604K Oct 13 06:42  Duplicati-server.sqlite
-rw-------  1 root root 2.5G Oct 13 03:57  UCXUKVJSMS.backup-56
-rw-------  1 root root  38G Oct 13 03:57  88787068678977808683.backup
-rw-------  1 root root 5.6G Oct 13 03:57  88787068678977808683.sqlite
-rw-------  1 root root 2.4G Oct 10 01:00  UCXUKVJSMS.backup-55
-rw-------  1 root root 2.4G Oct  8 01:00  UCXUKVJSMS.backup-54
-rw-------  1 root root 2.5G Oct  7 01:00  UCXUKVJSMS.backup-53
-rw-------  1 root root 2.5G Oct  3 01:00  UCXUKVJSMS.backup-52
-rw-------  1 root root 2.5G Sep 25 01:00  UCXUKVJSMS.backup-51
-rw-------  1 root root 1.8G Sep 18 01:00  UCXUKVJSMS.backup-50
-rw-------  1 root root 1.8G Sep 17 01:00  UCXUKVJSMS.backup-49
-rw-------  1 root root 1.8G Sep 16 01:00  UCXUKVJSMS.backup-48
-rw-------  1 root root 1.9G Sep 15 01:00  UCXUKVJSMS.backup-47
-rw-------  1 root root 2.4G Sep  6 03:00  OXPKYFAMWC.backup-9
-rw-------  1 root root 2.4G Aug 30 03:00  OXPKYFAMWC.backup-8
-rw-------  1 root root 1.6G Aug 19 01:00  UCXUKVJSMS.backup-46
-rw-------  1 root root 1.6G Aug 18 01:00  UCXUKVJSMS.backup-45
-rw-------  1 root root 1.5G Aug 16 01:00  UCXUKVJSMS.backup-44
-rw-------  1 root root 1.5G Aug 15 01:00  UCXUKVJSMS.backup-43
-rw-------  1 root root 1.5G Aug 14 01:00  UCXUKVJSMS.backup-42
-rw-------  1 root root 1.5G Aug 13 01:00  UCXUKVJSMS.backup-41
-rw-------  1 root root 1.5G Aug 11 01:00  UCXUKVJSMS.backup-40
-rw-------  1 root root 1.5G Aug  9 01:00  UCXUKVJSMS.backup-39
-rw-------  1 root root 823M Aug  7 01:00  UCXUKVJSMS.backup-38
-rw-------  1 root root 823M Aug  6 01:00  UCXUKVJSMS.backup-37
-rw-------  1 root root 823M Aug  5 01:00  UCXUKVJSMS.backup-36
-rw-------  1 root root 826M Aug  4 01:00  UCXUKVJSMS.backup-35
-rw-------  1 root root 1.5G Aug  2 03:00  OXPKYFAMWC.backup-7
-rw-------  1 root root 1.5G Jul 26 03:00  OXPKYFAMWC.backup-6
-rw-------  1 root root 1.4G Jul 12 03:00  OXPKYFAMWC.backup-5
-rw-------  1 root root 1.5G Jul  5 03:00  OXPKYFAMWC.backup-4
drwxr-xr-x  2 root root 4.0K Jul  3 04:00  custom-cont-init.d
drwxr-xr-x  2 root root 4.0K Jul  3 04:00  custom-services.d
-rw-------  1 root root 1.4G Jun 21 04:00  XMQGDGVQKA.backup-5
-rw-------  1 root root 1.3G Jun  7 03:00  OXPKYFAMWC.backup-3
-rw-------  1 root root 823M May 27 01:00  UCXUKVJSMS.backup-34
-rw-------  1 root root 823M May 26 01:00  UCXUKVJSMS.backup-33
-rw-------  1 root root 823M May 25 01:00  UCXUKVJSMS.backup-32
-rw-------  1 root root 1.2G May 24 03:00  OXPKYFAMWC.backup-2
-rw-------  1 root root 823M May 24 01:00  UCXUKVJSMS.backup-31
-rw-------  1 root root 849M May 23 01:00  UCXUKVJSMS.backup-30
-rw-------  1 root root 1.2G May 10 02:00  BTLIXKKHGG.backup-2
-rw-------  1 root root 830M May  9 01:00  UCXUKVJSMS.backup-29
-rw-------  1 root root 830M May  8 01:00  UCXUKVJSMS.backup-28
-rw-------  1 root root 830M May  7 01:00  UCXUKVJSMS.backup-27
-rw-------  1 root root 821M May  6 01:00  UCXUKVJSMS.backup-26
-rw-------  1 root root 648M May  4 05:38 'backup BTLIXKKHGG 20210504073805.sqlite'
drwxr-xr-x  4 root root 4.0K May  4 04:00  .config
-rw-------  1 root root 318M May  3 01:51 'backup UCXUKVJSMS 20210504070213.sqlite'
-rw-------  1 root root 318M May  3 01:00  UCXUKVJSMS.backup-25
-rw-------  1 root root  25G May  3 00:23 'backup 88787068678977808683 20210504060044.sqlite'
-rw-------  1 root root 321M May  2 01:00  UCXUKVJSMS.backup-24
-rw-------  1 root root 317M Apr 30 01:00  UCXUKVJSMS.backup-23
-rw-------  1 root root 317M Apr 29 01:00  UCXUKVJSMS.backup-22
-rw-------  1 root root 317M Apr 28 01:00  UCXUKVJSMS.backup-21
-rw-------  1 root root 317M Apr 27 01:00  UCXUKVJSMS.backup-20
-rw-------  1 root root 604M Apr 26 11:04 'backup XMQGDGVQKA 20210505020251.sqlite'
-rw-------  1 root root 558M Apr 26 04:47 'backup OXPKYFAMWC 20210504020234.sqlite'
-rw-------  1 root root 558M Apr 26 03:00  OXPKYFAMWC.backup-1
-rw-------  1 root root  98M Apr 26 02:00  BTLIXKKHGG.backup-1
-rw-------  1 root root 317M Apr 26 01:00  UCXUKVJSMS.backup-19
-rw-------  1 root root 319M Apr 25 01:00  UCXUKVJSMS.backup-18
-rw-------  1 root root 315M Apr 23 01:00  UCXUKVJSMS.backup-17
-rw-------  1 root root 315M Apr 22 01:00  UCXUKVJSMS.backup-16
-rw-------  1 root root 315M Apr 21 01:00  UCXUKVJSMS.backup-15
-rw-------  1 root root 317M Apr 20 01:00  UCXUKVJSMS.backup-14
-rw-------  1 root root 540M Apr 19 03:00  OXPKYFAMWC.backup
-rw-------  1 root root  99M Apr 19 02:00  BTLIXKKHGG.backup
-rw-------  1 root root 315M Apr 18 01:00  UCXUKVJSMS.backup-13
-rw-------  1 root root 315M Apr 17 01:00  UCXUKVJSMS.backup-12
-rw-------  1 root root 315M Apr 16 01:00  UCXUKVJSMS.backup-11
-rw-------  1 root root 315M Apr 15 01:00  UCXUKVJSMS.backup-10
-rw-------  1 root root 315M Apr 14 01:00  UCXUKVJSMS.backup-9
-rw-------  1 root root 317M Apr 13  2021  UCXUKVJSMS.backup-8
-rw-------  1 root root 314M Apr 11  2021  UCXUKVJSMS.backup-7
-rw-------  1 root root 314M Apr 10  2021  UCXUKVJSMS.backup-6
-rw-------  1 root root 314M Apr  9  2021  UCXUKVJSMS.backup-5
-rw-------  1 root root 314M Apr  8  2021  UCXUKVJSMS.backup-4
-rw-------  1 root root 314M Apr  7  2021  UCXUKVJSMS.backup-3
-rw-------  1 root root 314M Apr  6  2021  UCXUKVJSMS.backup-2
-rw-------  1 root root 314M Apr  5  2021  UCXUKVJSMS.backup-1
-rw-------  1 root root 300M Apr  4  2021  UCXUKVJSMS.backup
-rw-------  1 root root 1.7M Mar 30  2021  XMQGDGVQKA.backup-4
-rw-------  1 root root 3.2M Mar 30  2021  XMQGDGVQKA.backup-3
-rw-------  1 root root 1.7M Mar 30  2021  XMQGDGVQKA.backup-2
-rw-------  1 root root 3.2M Mar 30  2021  XMQGDGVQKA.backup-1
-rw-------  1 root root 132K Mar 30  2021  XMQGDGVQKA.backup
-rw-------  1 root root 562M Jan 18  2020 'backup 88787068678977808683 20200120120000.sqlite'
-rw-------  1 root root 120K Jan  5  2020 'Sicherung 20200105115926.sqlite'
-rw-------  1 root root 1.4G Jan  5  2020  66767281859082708788.sqlite
-rw-------  1 root root 2.3M Jan  5  2020  84847975877189658682.sqlite
-rw-------  1 root root 120K Jan  5  2020 'Sicherung 20200105113243.sqlite'
-rw-------  1 root root 120K Sep 29  2019 'Sicherung 20190929084141.sqlite'
-rw-------  1 root root 113M Sep 29  2019  86866589848967869066.sqlite
-rw-------  1 root root 120K Sep 29  2019 'Sicherung 20190929082237.sqlite'
-rw-------  1 root root 124K Sep 29  2019  70897066838571827572.sqlite
-rw-------  1 root root 124K Sep 29  2019  70897066838571827572.backup-1
-rw-------  1 root root 120K Sep 29  2019 'Sicherung 20190929081856.sqlite'
-rw-------  1 root root 120K Sep 29  2019 'Sicherung 20190929081822.sqlite'
-rw-------  1 root root 120K Sep 29  2019 'Sicherung 20190929081754.sqlite'
-rw-------  1 root root 128K Aug 27  2019  70897066838571827572.backup
-rw-------  1 root root 120K Aug 27  2019 'Sicherung 20190827022547.sqlite'
-rw-------  1 root root 120K Aug 27  2019 'Sicherung 20190827022519.sqlite'
-rw-------  1 root root 3.2K Aug 27  2019  windows-backup
drwxr-xr-x  3 root root 4.0K Aug 27  2019  .mono
drwxr-xr-x  2 root root 4.0K Aug 27  2019  control_dir_v2

Welcome to the forum @Anon

Files ending in <date>.sqlite are probably automatic backups when Duplicati upgrades the DB format.
Old ones go stale very quickly, assuming the backup for them is still running, and they can be deleted.
You can probably also use ls -lurt on the folder to check last read times, to confirm no current use:

How to limit or delete automatic local database backups
Limit sqlite database backups - feedback pleas

Some such files will be harder to match to current database because the original DB name isn’t there:

Differens in database files, what are they?

Did it make things worse? I wonder if that’s what’s making files ending in backup or backup-<number>?

Do you run backup in GUI? If so, do you get clean runs without popup warnings, errors, or complaints?
You can see About → Show log → Live → Information at start of backup. Maybe you’ll see above lines.

How many backup jobs do you currently run, or care about? You can look up their Local database path.
Be sure to keep those. I see only two seemingly active. Was OXPKYFAMWC job deleted very recently?
88787068678977808683.sqlite would be one created from an older release, maybe 2.0.4.5 or 2.0.4.23.
I’m not sure how it managed to make a .backup version of the same timestamp and far greater size…

Hey,

thank you and thanks for reply. I haven’t seen that auto-cleanup made it much worse the last days I tested it.

Sadly my Backups have often Errors due to cloud upload limit, 403.

But tbh yesterday I exported the 2 backup plans and deleted the whole Duplicati folder, restarted it and imported the backup plans again. I’ll check soon how the database recreation went and if a backup is possible and how large the folder is now. :slight_smile:

Well after several tries of repair and delete-restore I can’t get the backup working again.

Duplicati.Library.Interface.UserInformationException: The database was attempted repaired, but the repair did not complete. This database may be incomplete and the backup process cannot continue. You may delete the local database and attempt to repair it again.

Please check About → Show log → Stored to see if you can find errors from DB recreation attempts.