Trying to import a discourse backup ~ 3GB from version v1.3.0.beta5 +97 to latest-release +87. During the import the following sql issue [2015-04-21 08:34:05] psql:/var/www/discourse/tmp/restores/default/2015-04-21-083104/dump.sql:3781134: ERROR: could not create unique index "post_timings_unique…

Your database may still contain old data. Destroy the Discourse container, then backup and delete /var/discourse/shared/standalone. Re-bootstrap and you should end up with a pristine, completely empty Discourse instance that should be able to import your backup. :slight_smile:

This new server has a clean discourse setup however it is perhaps possible from previous failed imports when the versions were initially further out. Will look into this. Thanks

If all else fails, you can delete that line from the import. (I suggest using nano or other terminal editor, NOT a gui editor, to do this, as the import dump.sql file can be large.)

I am the one with the problem. When editing the file, I get this. Trying to delete the line, I get this error when running the restore. The restore fails fairly quickly, right after starting to unzip, and before any text dump [2015-05-03 11:10:16] Marking restore as running... [2015-05-03 11:10:16…

Try this to re-package your backup: tar -cvzf cocos2d-forum-2015-05-01-041307.tar.gz -C cocos2d-forum-2015-05-01-041307 .

What’s the output of this command? tar -tzf cocos2d-forum-2015-05-01-041307.tar.gz

[image] elberet: tar -tzf cocos2d-forum-2015-05-01-041307.tar.gz One gazillion lines, starting with root@forum:/var/discourse/shared/standalone/backups/default# tar -tzf cocos2d-forum-2015-05-01-041307.tar.gz ./ ./meta.json ./dump.sql ./uploads/ ./uploads/default/ ./uploads/default/5458/ ./u…

That looks about right. Are you sure you actually restored that re-packaged backup and not the older version? And just to make sure, what’s the content of cocos2d-forum-2015-05-01-041307/meta.json?

meta.json is 47 bytes. A single line {“source”:“discourse”,“version”:20150422160235} Edit: Unless there is something tricky in the backup system, I am 99.9% certain it was the right file EditEdit: Not sure if it matters, but the original backup came from var/docker. The new install is located i…

SQL Error during import

Product Support Self-hosting

Bahlsen (Bahlsen) May 3, 2015, 2:35pm 7

The output log when compressing is slightly different, but the error is the same

Topic		Replies	Views
Error restoring backup "key is duplicated" Self-hosting	7	1974	August 30, 2017
Failed to restore DB Self-hosting	9	1470	October 17, 2019
Modifying the database inside of a backup to remove a duplicate key tag so that it doesn't fail when restoring Self-hosting	28	1849	August 30, 2023
Backup restoration fails Self-hosting backups	16	529	June 16, 2026
Index_users_on_username_lower error during database restore: import failed Product Support	4	1460	February 17, 2020

SQL Error during import

Related topics