# 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:** Product 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:** 6

<div class="post-metadata">

**Author:** ![meglio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/meglio/32/71444_2.png) [@meglio](https://meta.discourse.org/u/meglio)\
**Post date:** [January 8, 2018, 3:19am UTC](https://meta.discourse.org/t/migration-version-is-missing-from-the-filename-cant-restore-from-backup/77346/6 "2018-01-08T03:19:03Z")

</div>

> [@codinghorror](#):
>
> Why did you rename it? That’s your problem. Don’t do that.

Renaming it back did it.

I renamed it because the file name was toooooo long and was spoiling my commands in terminal, and was unreadable. Such names come from long website titles, which are used as part of file name. Maybe the domain name should be used instead of the website title? So I just named it `bigbackup.tar.gz`.

I was under impression that the `.tar.gz` file will contain all information needed for restoration within it, so you can rename it freely to whatever you like, and following whatever naming conventions you have for organising your backups. To be fair, I find it counterintuitive that the backup consistency depends on the backup filename, same as it would be weird if a Word document couldn’t be read after it gets renamed.

---

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