SOLVED: Transferring Jellyfin from HTPC to ITX build

[toastyv]

Hi everyone,

Have searched the forums and can't find specifically the help I need; am fairly new to Jellyfin and am still learning.

I'm transitioning from a large HTPC build to an ITX build for my Jellyfin setup. This is what my setup is for each drive:

• SSD 2.5"- Has Jellyfin running in a docker container within OMV
  
• HDD 3.5"- All movies are contained in a 1TB mechanical drive
  

What I'd like to do is move the current SSD into the ITX build and use a new HDD 2.5" for my movies.

Will I encounter any challenges if I clone my HDD 3.5" and copy this onto a new HDD 2.5"? If there are no issues with this, which program have you used successfully to do this transfer?

[TheDreadPirate]

You shouldn't need to clone anything, really.

One of the main benefits of docker is config and data portability. Whatever directory that corresponds to /config in your container needs to be copied. Point the new container to that folder. Done.

Same with your media. Move your new media to whatever new hard drive/directory, point your container's config to those new folders but keep the same container side path. Done.

If you do both of those things, once you turn on the container it should be like nothing changed. And I am going to emphasize that both be done before turning on the container.

[Deleted User]

if it's in docker going to a docker then it is simpler than you might think

if everything is setup nominally and you use portainer -

in the current docker, edit libraries and turn off real time monitoring, important in case things do not line up jellyfin will not scan bad paths

in your current docker you have paths to media and a path to /config in the container, these are pretty much all you need to duplicate to a new docker

on the omv host make a backup of the path /config points to

on the new system setup a new instance of jellyfin, i use the cli from here - https://hub.docker.com/r/linuxserver/jellyfin

once setup you just need to restore your paths in the container for media and restore the config backup

if you amend the cli with the correct paths using multiple -v (for volume) your paths will be setup in the container
- or you can add them later with portainer

just be sure the container paths match the original, the host paths are not important

if everything goes well, it will be up and running

if somehow you did not use the same uid:gid you will need to chown the files to the new uid:gid

if it goes wrong, shutdown the docker and re-import the backup config as many times as you wish

to make the backup of config, tar or simply cp -a as they will both preserve uid:gid

re-enable real time monitoring after everything is up in the new container

[toastyv]

Thanks for your quick reply Thedreadpirate!

I configured Jellyfin by watching a tutorial on YouTube step by step; it was easy enough to follow so I don't know Docker as well as I'd like to, even though I used it lol! 

So sorry, can you guide me through this? Or is there a tutorial that you can point me in the right direction? Or is it still worth cloning drive?

[TheDreadPirate]

IMO, there is no need to clone at all.

Does OMV allow you to export your docker config to a text file?

[toastyv]

Sorry for the late reply! Rather than go through the hassle of cloning or using docker, I used an external 3.5 enclosure and that solved my problem.