# After migration, backup takes 4 x more

**URL:** <https://meta.discourse.org/t/after-migration-backup-takes-4-x-more/144305>\
**Category:** Product Support\
**Tags:** backups\
**Created:** [March 14, 2020, 11:26am UTC](https://meta.discourse.org/t/after-migration-backup-takes-4-x-more/144305 "2020-03-14T11:26:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [March 14, 2020, 10:55pm UTC](https://meta.discourse.org/t/after-migration-backup-takes-4-x-more/144305/6 "2020-03-14T22:55:02Z")

</div>

I can’t speak for everyone but I would prefer the option to eat a short term CPU hit regenerating assets over needing to allocate 4x more disk for backups.

---

_[View the full topic](https://meta.discourse.org/t/after-migration-backup-takes-4-x-more/144305)._
