# Backups keep taking down my forum **URL:** \ **Category:** Bug\ **Tags:** backups\ **Created:** [February 17, 2024, 5:00am UTC](https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698 "2024-02-17T05:00:11Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [March 11, 2024, 2:25pm UTC](https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698/10 "2024-03-11T14:25:18Z")
> [@gerhard](#): > > That won’t happen if the process gets terminated by the out-of-memory killer. Maybe that’s what’s happening! I’ve seen this “interrupted backups leave partial backups that fill the disk” scenario on a few sites. My best explanation has been an OS reboot in the middle of a backup, but I’ve seen it where there are no OS reboots.. Having the backup process get terminated by out-of-memory seems like a likely explanation that is sufficiently hard to replicate that it could explain this. . . . . Oh. Darn. One site that I remembered having this problem has 16GB of ram, so I don’t think that explains it. On that site the issue is that every week or so a backup is left on the local disk after it gets (or maybe does not get) pushed to S3. They also have over 100GB of free disk space, so it takes months for the issue to become a big enough problem that the disk gets full. Here’s the set of files I just deleted: ```plaintext forum-2024-03-11-123904-v20240202052058.tar.gz forum-2024-03-09-123159-v20240202052058.tar.gz forum-2024-03-07-123727-v20240202052058.tar.gz forum-2024-03-05-123019-v20240202052058.tar.gz forum-2024-03-03-123934-v20240202052058.tar.gz ``` --- _[View the full topic](https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698)._