Backups go to s3, but still a few random local backups stored

[rahim123]

Hi there, I was checking my disk space and I found a significant amount of data in /var/discourse/shared/standalone/backups/default/ despite my backups being configured to s3.

3.6G Sep 15  2023 forum-com-2023-09-15-060642-v20230910021213.tar.gz
3.6G Sep 23  2023 forum-com-2023-09-23-060044-v20230910021213.tar.gz
3.7G Oct  7  2023 forum-com-2023-10-07-060258-v20230910021213.tar.gz
4.6G Mar  1 01:07 forum-com-2024-03-01-060255-v20240122015630.tar.gz
5.1G May 31 01:09 forum-com-2024-05-31-060527-v20240307231053.tar.gz

Would those be failed backups?

If backup to s3 upload fails, backup is stored locally but ignores the backup limit

Multipart upload backups to Scaleway S3 aren’t working for me still. Backup Upload to S3 Fails on scaleway (multipart upload) The problem is, if the upload fails, the backup remains stored locally like when doing normal local backups. Which is good. However the backup limit is ignored, so it will keep filling up the local disk indefinitely with backups until it causes downtime. This is on 2.6.4 stable.

If that’s the case, it seems like they should be automatically deleted according to my maximum backups policy of 15 backups. Or maybe it’s happening because I have not set remove older backups ?

At any rate, I can manually delete them, right?

[pfaffman (Jay Pfaffman)]

This is a long standing bug. I’ve been unable to figure out what causes it. It happens very rarely so it’s difficult to diagnose. The solution is to just delete the local backups.

[omarfilip]

Try changing your backup time.

Local backups not deleted after they are uploaded to Amazon S3

Sixteen days later, it seems like this was the solution—no more undeleted backups. I don’t know what was causing the conflict, but it’s moot now.