# Backups keep taking down my forum

**URL:** <https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698>\
**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:** 1

<div class="post-metadata">

**Author:** ![piffy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/piffy/32/254198_2.png) [@piffy](https://meta.discourse.org/u/piffy)\
**Post date:** [February 17, 2024, 5:00am UTC](https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698/1 "2024-02-17T05:00:12Z")

</div>

I keep going through cycles where the backup creation is taking down my site due to space issues.

 ![image](https://global.discourse-cdn.com/meta/original/4X/2/0/3/203093b0f62c86f147e6e3f99af28116181b2f33.png)

I have set it up where I use a separate DO volume to store the backups and uploads. The volume is 300GB

My backup settings:

 ![image](https://global.discourse-cdn.com/meta/original/4X/7/a/7/7a7924a44afe1de315538026885402f9613b8d56.png)

The problem has been reoccurring for months. I will get messages about the backup failing in the admin inbox (see below)

> **No space left on device**
>
> ```plaintext
> [2024-02-14 03:43:34] Finalizing backup...
> [2024-02-14 03:43:34] Creating archive: elite-fourum-2024-02-14-033845-v20240204204532.tar.gz
> [2024-02-14 03:43:34] Making sure archive does not already exist...
> [2024-02-14 03:43:34] Creating empty archive...
> [2024-02-14 03:43:34] Archiving data dump...
> [2024-02-14 03:43:58] Archiving uploads...
> [2024-02-14 03:55:03] Removing tmp '/var/www/discourse/tmp/backups/default/2024-02-14-033845' directory...
> [2024-02-14 03:55:03] Gzipping archive, this may take a while...
> [2024-02-14 04:25:38] EXCEPTION: /var/www/discourse/lib/discourse.rb:138:in `exec': Failed to gzip archive.
> 
> gzip: /var/www/discourse/public/backups/default/elite-fourum-2024-02-14-033845-v20240204204532.tar.gz: No space left on device
> 
> [2024-02-14 04:25:38] /var/www/discourse/lib/discourse.rb:172:in `execute_command'
> /var/www/discourse/lib/discourse.rb:138:in `exec'
> /var/www/discourse/lib/discourse.rb:34:in `execute_command'
> /var/www/discourse/lib/backup_restore/backuper.rb:253:in `create_archive'
> /var/www/discourse/lib/backup_restore/backuper.rb:40:in `run'
> /var/www/discourse/lib/backup_restore.rb:13:in `backup!'
> /var/www/discourse/app/jobs/regular/create_backup.rb:10:in `execute'
> /var/www/discourse/app/jobs/base.rb:297:in `block (2 levels) in perform'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rails_multisite-5.0.0/lib/rails_multisite/connection_management.rb:82:in `with_connection'
> /var/www/discourse/app/jobs/base.rb:284:in `block in perform'
> /var/www/discourse/app/jobs/base.rb:280:in `each'
> /var/www/discourse/app/jobs/base.rb:280:in `perform'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:202:in `execute_job'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:170:in `block (2 levels) in process'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/middleware/chain.rb:177:in `block in invoke'
> /var/www/discourse/lib/sidekiq/pausable.rb:132:in `call'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/middleware/chain.rb:179:in `block in invoke'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/middleware/chain.rb:182:in `invoke'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:169:in `block in process'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:113:in `local'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq.rb:44:in `block in <module:Sidekiq>'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:263:in `stats'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_logger.rb:13:in `call'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_retry.rb:80:in `global'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:124:in `block in dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/job_logger.rb:39:in `prepare'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:123:in `dispatch'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:168:in `process'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:78:in `process_one'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/processor.rb:68:in `run'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/component.rb:8:in `watchdog'
> /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.12/lib/sidekiq/component.rb:17:in `block in safe_thread'
> [2024-02-14 04:25:38] Deleting old backups...
> [2024-02-14 04:25:38] Cleaning stuff up...
> [2024-02-14 04:25:38] Removing '.tar' leftovers...
> [2024-02-14 04:25:39] Marking backup as finished...
> [2024-02-14 04:25:39] Notifying 'system' of the end of the backup...
> 
> ```

But then what will happen is I will get a series of partially(?) complete backups that I am not notified about afaik. They will accumulate until it gets to the point where a new backup is attempted to be created every day and it takes down my site at the same time.

 ![image](https://global.discourse-cdn.com/meta/original/4X/b/a/0/ba0325370d94922692df372686916e21da1c3f22.png)

I have to manually ssh in and remove these because they don’t show up on the /admin/backups page.

I know it’s hard to replicate this issue and therefore hard to fix, but I was wondering if there was something obvious I am doing wrong or if others face the same issue?

---

_[View the full topic](https://meta.discourse.org/t/backups-keep-taking-down-my-forum/295698)._
