# Adicionar opção para desativar compactação de backup

**URL:** https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288
**Category:** Feature
**Created:** [30 Dezembro , 2015 22:43 UTC](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288 "2015-12-30T22:43:36Z")
**Posts on this page:** 1
**Showing post:** 21

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [24 Maio , 2016 22:12 UTC](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288/21 "2016-05-24T22:12:05Z")

</div>

Note to self:

Recently [hit space issues again and backups failing](https://meta.discourse.org/t/disk-space-and-backup-failure-notifications/24162/6) so [this post](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288/19) needs revisiting soon.

Note that in order to create a backup resulting in a 12GB gzip file I require ~36GB+ of space dedicated to backups, ~24GB+ of free space:

- 12GB for the backup from the day before
- 12GB for the new backup file
- ~12GB+ tar archive to be compressed into gzip file (original DB file backup + original image files

So as backup sizes increase by 1GB, the backup / space requirements are actually increasing by a ~3GB.

This assumes that you are only keeping a single previous backup - where the Discourse setting `maximum backups` is set to `1`.

The Discourse default is `5`, so using defaults I would need ~84GB dedicated to backups to allow them to work.

---

_[View the full topic](https://meta.discourse.org/t/add-option-to-disable-backup-compression/37288)._