Restoring from backup error

I recently ran into a massive issue with my server and had to start over. I backups of the database that I’m trying to restore however following the instructions I’m getting a -bash: syntax error near unexpected token ‘newline’ I’m not sure what that means also seeing as it looks like all my photos were deleted from my synology when I downed my Immich instance before delete then entire system to start over. I’m not sure if this is really going to help me out as I will have to reimport all my photos again. Any ideas?
16 Replies
Immich
Immich5d ago
:wave: Hey @SlimDayspring, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
JTtornado
JTtornado5d ago
I'm having the exact same issue. My PC crashed in the middle of the docker compose pull and it broke my server. I'd backed up my DB beforehand thankfully. But not I'm getting the exact same error in powershell on the cat "/dump.sql" | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" | psql --dbname=postgres --username=<DB_USERNAME> command after bashing into postgres
SlimDayspring
SlimDayspringOP5d ago
Did you photos get deleted too?
JTtornado
JTtornado5d ago
Nope. All 326gb of photos are still in the library folder
Zuri3l
Zuri3l5d ago
use the old restoration script
gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres
gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres
I had a similar problem with the new script
Mraedis
Mraedis5d ago
This is for Linux, the cat script is for windows Are you guys restoring to the same version your backup was from? If you have to re-import then restoring the DB won't do you any good
Zuri3l
Zuri3l5d ago
i used the script in linux always linux i dont have windows machines and works perfectly
Mraedis
Mraedis5d ago
It only works if your dump is not zipped, which it is by default
SlimDayspring
SlimDayspringOP5d ago
Yea same Linux but and different version of Ubuntu Fun!
Mraedis
Mraedis5d ago
Immich version my friend
SlimDayspring
SlimDayspringOP5d ago
Haha gotcha. Yeah I guess it was in 1.33 then I installed 1.34. Either way I have to start from scratch. Due to my photos being deleted from my synology. Luckily I have backups
Mraedis
Mraedis5d ago
1.133* 1.134* just FYI if you ever do need to specify the version
SlimDayspring
SlimDayspringOP5d ago
🤦🏻‍♂️you’re right.
Immich
Immich5d ago
This thread has been closed. To re-open, use the button below.
JTtornado
JTtornado4d ago
I'm on windows using Docker + WSL hitting the same issue. Is there an equivalent script for windows?
Zuri3l
Zuri3l4d ago
@JTtornado If you are using WSL, use this script. In my case, it worked perfectly. Just change the path to your backup.
gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres
gunzip < ./backup/dump.sql.gz \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| docker exec -i immich_postgres psql --username=postgres

Did you find this page helpful?