I feel like something with such a major backend change that will affect compatibility deserves a higher version number. I'm going to tweak my docker compose file to ensure I dictate when this big database update happens

[–] ShortN0te@lemmy.ml 10 points 2 months ago

Be aware,

Jellyfin uses semantic versioning. All releases will have versions in the X.Y.Z format, starting from 10.0.0. Note however that the 10.Y.Z release chain represents the "cleanup" of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases if required for later cleanup work

[–] mushroomman_toad@lemmy.dbzer0.com 1 points 2 months ago

Yeah, there's going to be a long, uninterruptable database migration at the next startup and they recommend taking backups before. My renovate is fully disabled for Jellyfin right now.

[–] imsufferableninja@sh.itjust.works 9 points 2 months ago (2 children)

According to the release notes, the DB migration could take "up to several days" depending on library size. Oof.

[–] Chewy7324@discuss.tchncs.de 3 points 2 months ago (2 children)

Hopefully no one has their DB on an HDD...

[–] AtariDump@lemmy.world 1 points 2 months ago

Or a Pi

[–] crazyminner@lemmy.ml 1 points 2 months ago (1 children)

Couldn't I just rebuild the database completely? Start from scratch and have it just remake all the metadata?

[–] imsufferableninja@sh.itjust.works 3 points 2 months ago

Well you would lose the watched status for all your media, as well as any custom settings and whatnot.

My plan, when the time comes to upgrade, is to copy the DB and bring up an isolated container using the copy, let the upgrade proceed in the background, then swap to the new container when the upgrade is done. That way there's minimal downtime and no data loss.

[–] notfromhere@lemmy.ml 9 points 2 months ago (1 children)

I hope the EFCore migration will make it easier to eventually support external databases like Postgres

[–] mushroomman_toad@lemmy.dbzer0.com 6 points 2 months ago (1 children)

There's a PR already!

[–] domi@lemmy.secnd.me 4 points 2 months ago (1 children)

Do you have a link for that PR?

[–] Mountaineer@aussie.zone 5 points 2 months ago (1 children)

Looks like this is it: https://github.com/jellyfin/jellyfin/pull/13451 Also looks like the intention is to stabilise the new data layer before adding extra backends to avoid rework.

[–] domi@lemmy.secnd.me 3 points 2 months ago

Thanks, Github thinking it is merged explains why I was not able to find it.

[–] Appoxo@lemmy.dbzer0.com 3 points 2 months ago

Looking forward to the release :)

[–] timeslip1974@lemmy.world 3 points 2 months ago (1 children)

While a lot of backend changes,nothing from a user perspective wants to me jump on board...no new features and your extensions will break......I think I'll wait lol

[–] mushroomman_toad@lemmy.dbzer0.com 3 points 2 months ago

There should be much better performance for browsing the library

[–] firepenny@lemmy.world 3 points 2 months ago (1 children)

This is a great update. All said, this will break my system as i have a lot of configurations.

[–] faercol@lemmy.blahaj.zone 2 points 2 months ago

Yeah, I'm using the OIDC plugin, so I'll need to wait as well

[–] HereIAm@lemmy.world 1 points 2 months ago (1 children)

So when a full backup is recommended, does that include media files, or is it just the cache(?) and jellyfin database?

[–] Mountaineer@aussie.zone 2 points 2 months ago* (last edited 2 months ago)

Backup of the jellyfin cache, Configs and database.
Your media should be outside of all that.

Exactly where those things are depends on your exact install method (native/docker/Linux/windows).

https://jellyfin.org/docs/general/administration/backup-and-restore/