Immich•3w ago

Problem with restoring database

When following the guide for manulal backup and restore, I am unable to restore the database and end up on the admin registration page. https://docs.immich.app/administration/backup-and-restore/ I do not get any errors from the gunzip command, and have made no changes to the .env and docker-compose file. This is on a new computer and i have immich still running on the old one, which works fine.

env

docker-compose.yml

immich_postgres_Usin...

13 Replies

Immich•3w ago

:wave: Hey @albdert, 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. :blue_square: uploaded the relevant information (see below). 7. :blue_square: 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.

Zeus•3w ago

Please share every step and the output you get when trying to run the restore.

albdertOP•3w ago

I am trying to follow the manual restore guide on the website

docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# rm -rf DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
docker compose pull             # Update to latest version of Immich (if desired)
docker compose create           # Create Docker containers for Immich apps without running them
docker start immich_postgres    # Start Postgres server
sleep 10                        # Wait for Postgres server to start up
# Check the database user if you deviated from the default
# Replace <DB_USERNAME> with the database username - usually postgres unless you have changed it.
gunzip --stdout "/path/to/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 --dbname=postgres --username=<DB_USERNAME>  # Restore Backup
docker compose up -d            # Start remainder of Immich apps

docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# rm -rf DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
docker compose pull             # Update to latest version of Immich (if desired)
docker compose create           # Create Docker containers for Immich apps without running them
docker start immich_postgres    # Start Postgres server
sleep 10                        # Wait for Postgres server to start up
# Check the database user if you deviated from the default
# Replace <DB_USERNAME> with the database username - usually postgres unless you have changed it.
gunzip --stdout "/path/to/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 --dbname=postgres --username=<DB_USERNAME>  # Restore Backup
docker compose up -d            # Start remainder of Immich apps

I am following these steps, deleting the database and only starting immich_postgres, with the DB_SKIP_MIGRATIONS=true setting in addition i am copying the backed up library into the immich folder i cannot see any other steps on the website, but if i did anything wrong, please tell me. and regarding the output, i do not get any errors. I am somewhat new to docker, is there a spesific command to show all output?

Zeus•3w ago

We would need to see full console terminal output of every command that you are actually running. not a copy paste of the instructions

albdertOP•3w ago

Here are the commands and output, tell me if you need anything else

console.txt

Zeus•3w ago

What happens if you just run gunzip --stdout "/home/albert/Backup/20251101-151733/db_dump.sql.gz

albdertOP•3w ago

Here is the log

console2.txt

albdertOP•3w ago

just to clarify, i redid all the previous steps before running the new command

Zeus•3w ago

are you sure that file even exists? how about running ls -lh /home/albert/Backup/20251101-151733/

albdertOP•3w ago

$ ls -lh  /home/albert/Backup/20251101-151733/
total 17G
-rw-r--r-- 1 albert albert 17G Nov  1 15:28 20251101-151739.tar.gz
-rw-r--r-- 1 albert albert  20 Nov  1 15:17 db_dump.sql.gz

$ ls -lh  /home/albert/Backup/20251101-151733/
total 17G
-rw-r--r-- 1 albert albert 17G Nov  1 15:28 20251101-151739.tar.gz
-rw-r--r-- 1 albert albert  20 Nov  1 15:17 db_dump.sql.gz

Zeus•3w ago

so your db dump is only 20 bytes that's an empty file most likely

albdertOP•3w ago

ok, interesting will try to do another db backup and check thank you so much, didn't even think to check the file size. The original dump was made with a script, so not sure what went wrong, but everything seems to be restored now. Again thank you so much 🙂

Immich•3w ago

This thread has been closed. To re-open, use the button below.

Gaming

Programming

Problem with restoring database

Did you find this page helpful?