Any idea what could caused it and how to fix it? I tried to restore from backup, but it didn’t work. P.S. I renamed the backup file, is it bad for restoring from backups? If so, the file name should be checked before even copying it to a temporary directory for extraction. [2018-01-06 01:19:46] …

Why did you rename it? That’s your problem. Don’t do that.

Original file name: kozovodstvo-v-ukraine-rossii-sng-forum-hozyajstva-rynok-2018-01-05-235903-v20171228122834.tar.gz New file name: bigbackup.tar.gz

This error message is pretty brutal @zogstrip , user uploaded a tar.gz file with an actual backup of discourse and we fail with EXCEPTION: Migration version is missing from the filename. after potentially a gigantic file was uploaded from client to server.

[image] 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…

No, because that means you have to unzip it to get key info for the backup restoration. What if it is a 100gb zip file? You can’t even tell if it is a valid backup until you fully decompress it.

To be fair you can not tell it is a valid backup anyway until we restore it. The metadata clearly belongs in the tar bundle imo not codified into the file name and you can just pull a single file out of a tar bundle instead having to decompress everything. We are already double compressing database…

Even though, the way it works now is it copies the file to /tmp and decompresses the file, and only then does the file name check. Maybe make the check before decompressing?

[image] 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 databa…

Migration version is missing from the filename – can't restore from backup - #11 by sam - Support

Topic		Replies	Views	Activity
Failed to restore from backup because backup file was renamed Support	6	1067	December 7, 2018
Backup Suggestions - Make a large flashing sign to not rename your backups Support	6	495	March 5, 2021
Restore from old version to a new version of discourse failed Self-hosting	16	2563	December 16, 2019
Backup restore failing due to .tar versus .tar.gz file extension Support	6	759	January 24, 2025
Unable to restore backup - No migration with version number Support	6	2494	May 5, 2016