Restore test
I make a daily copy of the immich folder structure to a mirror disk and a DB dump is made daily to the same disk as well. Periodically I'll make a copy to a portable disk as well.
I wish to test a restore of the Immich server to see how quick I would be up and running again. I would like to be able to run the test on another machine that will have different mount points / paths. Would that be possible at all, or would I have to run a restore on an exact copy of the server?
7 Replies
:wave: Hey @Carl,
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.You do not have to have the exact same folder structure. However, you'll have to edit your
.env file or docker-compose.yml file appropriately to reflect the changes in path.So definitely possible, and I'd say it even makes the exercise better
Since odds are you'd be restoring to a new/different system in a real DR as well
I like this idea…
So just by changing the paths in the .env file I should be able to do it? What concerns me is that probably the images are referred by their full paths in the database. If so, that means I would have to restore the DB and change all image references. Or am I missing something?
The database references the paths -internal- to the container
Which don't change unless you're doing something odd
Changing the host side of the mount is fine
The piece you're missing is how docker handles persistent storage, specifically bind mounts.
Here is the documentation:
https://docs.docker.com/engine/storage/bind-mounts/
https://docs.docker.com/get-started/workshop/06_bind_mounts/