Moved DB location and now Immich thinks I have a new install - how do I restore?
Immich has been running just fine on my UnRaid install for a while now. I realized I had not stored the database location to my appdata folder (which is an ssd) and decided to move the location to appdata. I made the updates to the env variables and the docker compose file. When Immich restarted, it appears to think its a fresh install. I think this makes sense since the database data is now in app data, but I cant figure out how to use the backup file (Database Dump) I created before doing all this to restore the install. The Linux example for restoring the backup in the docs is not helping me with my unraid installation. Any help is appreciated.
2 Replies
:wave: Hey @e46forlife,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: 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.The reason the DB restore process was not working for me on UnRaid is because I had to set the DB_SKIP_MIGRATIONS=true in the env variables. The docs explianed this a bit further down the page, but I missed it. Restore was successful and I also updated to 1.133 as well. Moving the database to my SSD is such a huge performance increase when searching...I should have done this on 1.102.
Thank you to the devs! Keep it up!
Thank you to the devs! Keep it up!