Transferring to a new server

[troothdotcom]

I an running the latest Ubuntu Server OS on an old laptop and a bare metal install of Jellyfin 10.9.7 and I would like to transfer the whole instance (settings, libraries, users etc) to a new server also running Ubuntu Server OS. Also I should mention that I am using Nginx to proxy it through a domain to give remote access to it. Is this possible? If so how? 

I have Jellyfin working 99% how I want so I don't want to start from scratch but is that a better option?

[Efficient_Good_5784]

You can keep all your settings. You just need to make a copy of your Jellyfin config folder (preferably with the server turned off).

Simply then just transfer a copy of that config folder to the new machine for the new Jellyfin server to use.

[troothdotcom]

You can keep all your settings. You just need to make a copy of your Jellyfin config folder (preferably with the server turned off).

I'm sorry what do you mean with the server turned off? How would I make the copy then? Sorry I'm still new to this.

[TheDreadPirate]

If you copy the entirety of the two directories below, reset the permissions, it should "transplant" your jellyfin to your new server.

/var/lib/jellyfin
/etc/jellyfin

Once you move the folder into the same locations on the new server you will need to reset the permissions since the Jellyfin use likely has a differrent UID.

sudo chown -R jellyfin: /var/lib/jellyfin /etc/jellyfin

[Efficient_Good_5784]

You can keep all your settings. You just need to make a copy of your Jellyfin config folder (preferably with the server turned off).

I'm sorry what do you mean with the server turned off? How would I make the copy then? Sorry I'm still new to this.

I mean the Jellyfin server. The machine it's installed on stays on obviously.

[Celvin238]

I am new to JellyFin and run it in a docker container on a DS224+ with Celeron CPU (Gemini Lake). I am definitely not a pro user...

I've invested a lot of time in JellyFin working on the Metadata of the files. Now I want to be able to save and restore them. But at the moment I don't have the knowledge to do it...

Here are my questions:

1. Where can i find the two storage locations “/var/lib/jellyfin” and ‘/etc/jellyfin’ TheDreadPirate describes?
In the DSM Filemanager I can only find the “config” folder described by Efficient_Good_5784 (in the “docker” folder). Can't I just copy this one?

2. I understand that I have to reset permissions. But I don't understand how to reset them by using the command prompt "sudo chown -R jellyfin: /var/lib/jellyfin /etc/jellyfin".
Where do I have to execute this command?

3. Another (offtopic) question: Is hardware acceleration still not possible in JellyFin versions > 10.8.11?

Thanks in advance!

[TheDreadPirate]

1) /var/lib/jellyfin and /etc/jellyfin are for package installs and is not applicable to docker installs. /config and /cache are the two directories you need to transfer to a new host.
2) I don't think this applies to DSM installs. @Efficient_Good_5784 would be able to confirm, since I don't have a Synology NAS.
3) Transcoding works, but tone mapping is busted due to Synology NASes using an ancient Linux kernel that Intel no longer supports.

[Celvin238]

Thanks for the quick answer TheDreadPirate!

Regarding No. 3: Does that mean that in newer Versions of JellyFin (> 10.8.11) there is something like a driver from Intel which does not support kernel 4.4?

It is really annoying that such a new Diskstation like the DS224+ has only kernel 4.4 and probably stays at that kernel for the rest of its lifetime.
I even cannot buy a newer one, because there is no new model.

What is the better option: Installing JellyFin 10.8.11 and use tone mapping or installing the latest version of JellyFin and use Transcoding without tone mapping?

[TheDreadPirate]

Correct. We bundle all the Intel media and openCL drivers with our docker image. Intel deprecated support for kernel 4.4.X for the Intel compute runtime that was bundled with 10.9.0+.

The best option, IMO, is to use your NAS as just a NAS and have Jellyfin run on a PC. Even something like an Intel N100 equipped mini PC. That way your OS isn't locked down like DSM is.

Your other option is to use the linuxserver docker image since you can specify a specific version of the Intel compute runtime you want to install. So you could install an older compute runtime that still supports kernel 4.4.X. But the official Jellyfin image and linuxserver image are not easily interchangeable so you may have issues migrating your existing data to the linuxserver image.

[Celvin238]

@TheDreadPirate:

I've tried to create a "new" container version of JellyFin which fully support transcoding (with tone mapping). For that it was necessary to create the container manually and, of course, using JellyFin 10.8.11.

Then I tried to replace the two folders "/config" and "/cache" from that "new" version (10.8.11) with this folders of my "old" version (10.10.1).

But when I try to restart v. 10.8.11 again, an error in DSM shows up: "container jellyfin was unexpectedly terminated".

Maybe the transfer of metadata from a newer (10.10.1) to an older version (10.8.11) of Jellyfin is not possible?

And another question: I created the container manually because I have read that a special command is necessary to enable transcoding, which is not integrated in the normal container file, this one:

" devices:
- /dev/dri/renderD128dev/dri/renderD128
- /dev/dri/card0dev/dri/card0"

Is it possible to modificate a normal container version of JellyFin to get transcoding there, too?