Jellyfin Backup/Restore Synology NAS

[polilla]

On a Synology NAS DS1522+ Jellyfin was installed via container manager and configured it to show movies, tv shows. Updated the image to the latest version 10.11.0 and lost all the metadata, libraries, etc.

After researching, I realized that the configuration resides only on the container; it doesn't persist on the NAS and cannot be backed with hybperbackup. I have just recreated the metadata but want to make sure I can back it up. I want to be able to save the configuration on /volume1/docker/jellyfin/config and the backup in  /volume1/docker/jellyfin/config.

Looking at the details on the container manager for the Jellyfin container, I see there is no information to persist the data. Is there a way to edit the configuration to do what I explained above?

If I try to duplicate the container and add paths to map the container to a NAS folder for the config, cache, and backup, then I cannot see the configuration I had just recreated.  

Using Jellyfin backup tool, I created a zip file with a backup of the recently recreated config/metadata. If I move the data to the proper folder on the NAS, how can I point the new container to the restored data?

Please advise. I have little to no experience with docker/container manager. Many thanks.

[JellyJeff]

Hi,
your configuration is missing the mounts for the config dir and cache dir. In the section "Volume" you need to add the following lines:

Code:

      /volume1/docker/jellyfin/config:/config
      /volume1/docker/jellyfin/cache:/cache

With these additional mounts, Docker will persist everything Jellyfin is writing in /config and /cache and you can access the files there via Synology File Manager and other tools, back them up (eg. by copying them while Jellyfin isn't running) and restart/recreate/upgrade the Jellyfin container without losing them.

You may have to create the folders /volume1/docker/jellyfin/config and /volume1/docker/jellyfin/cache before updating the container configuration in Container Manager and it will lead to losing the metadata and other information stored in Jellyfin once again because Jellyfin will start over with these new (initially empty) folders. But then you won't lose them again.

Every time you want to upgrade Jellyfin, you should stop the container and make a copy of the folder /volume1/docker/jellyfin/config before upgrading so you can revert everything if something goes wrong during or after the upgrade.

You may also want to change the docker image tag from "latest" to "10.11.0" so that you can better control which version of docker you are using and prevent Synology from upgrading Jellyfin automatically.

I personally prefer to use Docker Compose to do the configuration because it's easier to maintain. You need a bit of knowledge about Docker (Compose) for that, but you can do so in Synology Container Manager by creating a "Project" and providing a YAML configuration for it (which is a regular Docker Compose configuration file).

[JellyJeff]

Here is an example Docker Compose configuration derived from https://jellyfin.org/docs/general/instal...er-compose that should work for you:

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin:10.11.0
    container_name: jellyfin
    ports:
      - 8096:8096/tcp
    volumes:
      - /volume1/docker/jellyfin/config:/config:rw
      - /volume1/docker/jellyfin/cache:/cache:rw
      - /volume1/video:/media:rw
      - /volume1/Books:/books:rw