#Having Trouble with v3.0 Migration - Database Issues, Rollback Issues

26 messages · Page 1 of 1 (latest)

cosmic nebula
#

Hello!

I was using the 'release' version in my .env before today. I pulled the 3.0 image without properly following the migration steps. Now I'm in a bit of a weird spot.

I did copy my ./immich folder to a 'BU_immich' folder, which is supposed to be untouched, but it gave me weird behavior when trying to roll back to 2.7.5.

The timeline looks like:

  • Take immich stack down
  • Backup ./immich folder (postgres)
  • Pull 3.0
  • Bring it up, notice the page doesn't load
  • Check logs, work with Gemini to diagnose & troubleshoot (disaster lol)
  • Attempt to migrate DB
  • Attempt to roll back by changing .env to point to v2 instead of release, point to a copy of the 'BU_immich' backup folder (didn't work, got the admin registration page)

Could someone please advise me on the next steps here? I see there are steps to migrate to VectorChord: https://docs.immich.app/install/upgrading/#migrating-to-vectorchord
Am I able to do that in the state that I'm in?

I understand and own up to the fact that I did this wrong. Any help / advice would be appreciated!

📎 compose-snippet.txt 📎 env.txt
marsh kestrelBOT
#

:wave: Hey @cosmic nebula,

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

#

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. :ballot_box_with_check: 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.

cosmic nebula
#

These are the initial error logs on the first v3 attempt

marsh kestrelBOT
icy plinth
#

You can't copy postgres folders, you need to restore a backup

marsh kestrelBOT
cosmic nebula
icy plinth
#

That should work in theory but it's also not very good practice

#

Are you hosting on windows perchance @cosmic nebula ?

cosmic nebula
cosmic nebula
#

I'll have time to look into it furthet today. Might try the backup restore. I assume I'll need to spin up a brand new instance to do the restore? Considering I can't "get into" my old instance

icy plinth
#

Right so to properly migrate you need to stay on 2.7.5 when switching the DB image

#

You can't yeet right into 3.0 with the new DB

#

If that gives you errors, post those errors

cosmic nebula
#

Lol yeah, that was my bad for missing that. I was naive for sure.

#

Just to clarify: I should spin up a brand new 2.7.5 instance, restore from backup from that folder I copied, then do the DB migration?

#

Do backups happen periodically/automatically? I may or may not have backups TBH

icy plinth
#

They happen nightly in UPLOAD_LOCATION/backups

#

But you should try simply grabbing the new DB image with both vector extensions and v2.7.5

#

So:
docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0
turns into
ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0

cosmic nebula
#

Okay, I'll try that and report back. Thanks much for the help/direction!

plush root
plush root
#

2026-07-05T01:03:01.918365010Z [postgresql14] 2026-07-05 02:03:01.918 BST [4532] FATAL: role "root" does not exist

#

my postgres container is unhealthy