upgrade Server Version: v1.125.6 and migration to new server
Hi All,
I have this particular scenario and not sure how to proceed on it.
Currently have Immich on raspberry pi and its running Server Version: v1.125.6
- The machine is very low on disk space ~90% full
- Portainer is used to manage the containers
I do not think upgrading on the current machine will be feasible due to space limitations and a newer image causing disk issues.
https://github.com/immich-app/immich/releases/tag/v1.125.6 I am aware of the release notes for that version
I would like to migrate to another VM on a much more powerful host, I am unsure the best way to do this.
I believe I need to deploy a new Immich stack on the new VM and then attempt to do a backup on the old host and restore on the new one of the database.
Secondly should I be installing the version that is on the current old machine or attempt to do an upgrade to a later version?
2 Replies
:wave: Hey @Kangaroodog,
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. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: 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. :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.If you can post your current
compose.yml + .env (or Portainer equivalent) we can give more tailored advice.
It would be safer to migrate using the same version and verify that v1.125.6 works fine on the new host/VM before upgrading further.
I believe I need to deploy a new Immich stack on the new VM and then attempt to do a backup on the old host and restore on the new one of the database.This is the safest way, as you might have different CPU architectures between hosts and Postgres does not guarantee 100% compatibility. (Though it works fine in practice between arm64<->x64 on the same OS/container). So alternatively, as an experiment, you can copy all your asset data (folders) + Postgres data folder + deploy compose and env (assuming you use the same paths in your new VM). Re: upgrade. In you case I suggest to upgrade to
v1.132.3, verify that it works fine.
- Follow the upgrading doc https://docs.immich.app/install/upgrading/
- Check release notes for breaking changes; the link from the doc above: https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_created
- Also be aware of https://docs.immich.app/errors/ - possible upgrade caveats (if not following the recommended upgrading path)