# Reduce local disk space needs by not (redundantly) gzipping backups

**URL:** <https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763>\
**Category:** Feature\
**Tags:** backups\
**Created:** [November 16, 2022, 12:38pm UTC](https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763 "2022-11-16T12:38:03Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [August 30, 2024, 8:02pm UTC](https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763/10 "2024-08-30T20:02:15Z")

</div>

Hmm that wouldn’t help me at all! (Likewise others who’ve had the same problem with limited disk space.)

If tar were being used, it could be used with z or j options. If a subshell were being used, the output of tar could be piped into gzip. But I think in fact some higher level ruby functions may be in use.

---

_[View the full topic](https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763)._