# 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:** 8

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [March 16, 2020, 10:44am UTC](https://meta.discourse.org/t/after-migration-backup-takes-4-x-more/144305/8 "2020-03-16T10:44:52Z")

</div>

> [@Stephen](#):
>
> Could we get a backup option that only covers original assets?

That’s how backups work. By default, thumbnails aren’t included in backups. We changed that at least a year ago.

You can configure that behavior with the `include_thumbnails_in_backups` site setting.

> Include generated thumbnails in backups. Disabling this will make backups smaller, but requires a rebake of all posts after a restore.

@eextra I’d recommend creating a file based diff of the content of an old and new backup in order to find out why the backup is so much larger.

---

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