A bit of an update. Someone else in my team was working on this last week but a solution didn’t come so i had another try, this time by editing the DB on my local system.
What i did:
- downloaded old backup that i want to restore
- unzipped files with 7zip
- opened dump.sql with visual studio code
- found the duplicated tags directly in the DB.
- found what appeared to be the tag listing by searching using ’ ’ around the tag. In my case ‘socialmedia’. The tags look to be the 2nd and 3rd from bottom of the found instances.
- edited one to read
132 ‘socialmedia2’:1A socialmedia2 en_GB 3
- Rezipped the dump.sql file in 7zip
- Add to archive
- Archive format .gzip
- Rezipped the main backup file
- Add to archive
- Archive format .tar (gzip is not yet available)
-
You should now see a zipped .tar fixed backup file
-
Zip the .tar file in 7zip to create a .tar.gz file, to match the format used by Discourse
- Add to archive
- Archive format .gzip
- Upload to backups and restore via the admin section
At this point i hit an error message:
Extracting dump file…
[2023-08-08 15:09:15] EXCEPTION: No such file or directory @ rb_check_realpath_internal - /var/www/discourse/tmp/restores/default/2023-08-08-150913/dump.sql.gz
Anyone have any ideas what i missed in the above process?
The only thing i can think of is that the path its looking for is using todays date and not the the date of the backup (i’m writing this on 08-08-2023).