Truenas to Debian Linux migration questions?

[deprice40 1]

Good morning everyone

I am in the processes of migrating my Truenas apps onto a Debian server install with Docker so i get more control and flexibility of apps and i have couple of questions about the migration process of Emby and just to make sure it goes smooth without much of a hitch ideally so i don't have to install Emby fresh losing all configs.

1 - On Truenas i have a dataset called Program_Data and inside this each app has it's own dataset IE Emby, Nextcloud, Mymediaforalexa etc for storing app configs, users and so fourth. On my new Debian 12 server install i have again create a folder called Program_Data and inside this again folders for each app and Emby has it's own app. For migrating can i just copy the data from the Program_Data/Emby location on Truenas to the Program_Data/Emby location on Debian, spin up a compose file that points to the data and whirl it up with no issues

2 - In terms of media, on Truenas when installing an app i pointed towards my media with a host path so as an example

Hostpath - /mnt/Vol1/Audio
Mountpath - Audio

On Debian i have Samba shares created that auto mount on start up in /etc/fstab and mount to /media/Video, /media/Audio, /media/TV, /media/Audiobook and so fourth. when creating the compose file, do i just add the following for the media.

- /media/Video:/mnt/Video # Media directory

The Samba shares have the same name as the hostpaths on Emby and when loading up Emby which points to my configuration and the media should this load with no issues both on loading my configuration and seeing the media libraries or is there further configurations or anything i need to do in the migration process?

BTW the compose file will look like as followed (more media will be added)

version: "2.3"
services:
  emby:
    image: emby/embyserver
    container_name: embyserver
    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000 # The UID to run emby as (default: 2)
      - GID=100 # The GID to run emby as (default 2)
      - GIDLIST=100 # A comma-separated list of additional GIDs to run emby as (default: 2)
    volumes:
      - /root/Program_Data/Emby:/config # Configuration directory
      - /media/Audio:/mnt/Audio # Media directory
      - /media/Video:/mnt/Video # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    restart: on-failure

Thank you everyone.

Edited July 23, 2024 by deprice40

[Q-Droid 989]

15 hours ago, deprice40 said:

1 - On Truenas i have a dataset called Program_Data and inside this each app has it's own dataset IE Emby, Nextcloud, Mymediaforalexa etc for storing app configs, users and so fourth. On my new Debian 12 server install i have again create a folder called Program_Data and inside this again folders for each app and Emby has it's own app. For migrating can i just copy the data from the Program_Data/Emby location on Truenas to the Program_Data/Emby location on Debian, spin up a compose file that points to the data and whirl it up with no issues

The first part should work as long as everything is there and you used defaults for the paths. The Emby server data files and paths are relative to the data home and /config in the container. You can check from the 3-dot menu on the dashboard (View server info) for some of them like cache, metadata and transcoding temp. If you customized any of those you'll have account for them in the docker config.

If you convert, download (sync) or run the auto-organize plugin you should check those paths too. Same goes for backup & restore, you need to be able to reach the destination from the container.

15 hours ago, deprice40 said:

2 - In terms of media, on Truenas when installing an app i pointed towards my media with a host path so as an example

For the media, as long as the container sees the paths as they were on the original host then it should work as if nothing changed. But now you're dealing with SMB/CIFS and you have to make sure the UID/GID you plan to use for the container has the same access Emby had on the original host. You might need to tweak things to get there and once that's sorted you should be good to go.

 

[deprice40 1]

Thank you for the reply

I have had mostly success doing a test migration of the data to the Debian server machine whilst leaving the Emby install on Truenas just keeping the app powered down so i can easily spin up if all went wrong. Everything went fine other than it no longer showed the media in the libraries. After checking things over i had to update each individual library because of a path change

/Audio to /media/Audio
/Documentaries to /media/documentaries

All the mount points for the Truenas samba shares are mounted in /media

Currently doing a library scan but so far it's loading in stuff fine and a tested a documentary and it's started fine, i don't see any obvious problems so far other than just having to update the library paths. And thank you for reminding me about the Emby backups i would have forgotten then wondered why it's not backing up. Had to do the same as the media libraries and just point to a /media/Private/Backups/Emby location.

Cheers!!

[Q-Droid 989]

If you had preserved the container library path to look like they did on the original host you shouldn't have needed a rescan. How they're mounted on the host itself doesn't matter as much since you can map the bind mounts to different paths.