Hi, We are currently taking a full backup of our discourse instance once a day. This backup is then pushed to S3. Our S3 bucket is configured to expire files after 30 days. Discourse is configured to keep two backups locally and to skip S3 removal when removing a local backup. However i have noticed that Removing a backup from the console also removes it from s3 Even with the 2 backup max option, I see we are keeping more than 2 backups locally. Config: [image] Result: [image] Is this the expected behavior? Did I miss something? We are using [v2.2.0.beta4 +19] Thx Seb

[image] sebastien: We are using [v2.2.0.beta4 +19] The behavior for backups changed in beta 3. See Backup location for more information on that. Essentially, backups are either store locally or on S3. In your case it’s S3 and since you disabled the cleanup on S3 it will ignore the maximum_backups setting. Backups aren’t stored on your local disk anymore. The “Backups” tab in the admin section will show you the files stored on S3 and deleting a backup on that tab will remove it from S3.

Maximum backups setting ignored

Product Support

sebastien November 21, 2018, 1:14am 3

Ok thx for the clarification!

Topic		Replies	Views
Discourse not respecting the number of S3 backups to keep Self-hosting backups , s3	7	1097	April 10, 2024
's3 disable cleanup' settings has a wrong description UX	4	970	August 22, 2026
Backup location Announcements backups , new-feature	12	5408	March 14, 2019
Backups go to s3, but still a few random local backups stored Self-hosting backups	2	134	August 10, 2024
S3 daily backups issue? Discourse also keeps backups locally every 4 days and I don't know why Product Support backups , s3	2	804	March 11, 2022

Maximum backups setting ignored

Related topics