Restore faulty Immich from backup
I have a Immich instance installed on my home server using docker (on Ubuntu server, on an old HDD).
Last month I was uploading several pictures on my Immich, and it was very busy extracting metadata and running AI on the new assets (it was like 1000 new assets). Suddenly the power went out.
Once the power was back my server was no longer booting, I was stuck in Initramfs.
I run
fsck /dev/sda1 -y
and it repaired the faulty file system. Then I booted correctly.
Unfortunately almost all docker container (pihole, radar, ecc…) were working fine but Immich.
Immich (immich_server and immich_postgres) containers were stuck in a reboot loop. Stopping them and restarting didn’t work.
Fortunately I had a weekly backup, therefore I rolled back ALL the subfolders in /var/lib/docker/ (overlay2 included), and I also restored my postgres folder (but not my library folder, I left it as it is).
Still it was not working properly, Immich was rebooting and not healthy in docker.
Then I followed the guide at “https://docs.immich.app/administration/backup-and-restore/“, the part about manual restore.
I restored everything from the *.sql.gz backup archive that Immich automatically created. This worked perfectly and now my Immich server seems to be working!
But I am quite uneasy on this installation now. Is there something on Immich that I should run? Is there something I should do or check? What about the photos that were uploaded after my backup, they should still be in the upload_location but not indexed by the database, is this an issue?
4 Replies
:wave: Hey @Bianconiglio,
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.What about the photos that were uploaded after my backup, they should still be in the upload_location but not indexed by the database, is this an issue?Yeah, this is the way around that you want it to be; anything the database doesn't know about should get reuploaded by your phone (or if you uploaded them manually, just do that again), and the worst case is that you have some forgotten duplicates on disk which isn't the end of the world.
Ok not a problem, thanks. Should I re-run all the jobs? Should I do something more?
Running for missing shouldn't hurt