# Migration version is missing from the filename – can't restore from backup

**URL:** https://meta.discourse.org/t/migration-version-is-missing-from-the-filename-cant-restore-from-backup/77346
**Category:** Support
**Created:** [January 6, 2018, 1:24am UTC](https://meta.discourse.org/t/migration-version-is-missing-from-the-filename-cant-restore-from-backup/77346 "2018-01-06T01:24:53Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [January 8, 2018, 5:29am UTC](https://meta.discourse.org/t/migration-version-is-missing-from-the-filename-cant-restore-from-backup/77346/10 "2018-01-08T05:29:09Z")

</div>

> [@sam](#):
>
> We are already double compressing database which is odd to say the least. I think we should probably change it so our backup file is just a tar, that is more strategic about compression.

The reason we removed the metadata file is because it FORCED a zip compression of the database plus one file.

It is not an issue if you are including downloads, but if you are not.. it means 100% pointless gzip trip to combine 100GB database backup file (which is already streamed compressed from postgres backup) and 512 bytes of metadata file. So ultra-ultra-ultra pointless.

---

_[View the full topic](https://meta.discourse.org/t/migration-version-is-missing-from-the-filename-cant-restore-from-backup/77346)._