best way to backup (lsio) docker jellyfin data?

[bitmap]

please excuse the late followup question - but are you using a smb or an nfs share for the rsync?
i first used smb for smaller docker stuff but realized that smb does not support symlinks easily when i tried to backup nginx proxy manager. since then i have switched everything to nfs, but am not sure if it is a good choice to back up jellyfin AND what parameters to use for the nfs mounting
is file-locking a huge issue? should i go for a hard or a soft moutn? or ignore that and go for a x-systemdautomount? if so, should i set a idletime?

I'm jumping in a little late here, but I've used rsync to backup my LSIO instance several times, including at least one server rebuild. For NFS, you need to preserve anything you want to stay the same (e.g., ownership, permissions if you're particular) but you can also change all of that back if you need. I didn't archive anything, as compression wouldn't save much aside from logs, which are cleaned regularly. I have had ZERO issues with file locking.

I chose to squash file access to a single user, which you can do using anonuid and anongid and the ID number of the user (anonuid) and group (anongid). This has allowed me to avoid permissions issues, but it will not preserve ownership or anything of the sort. It's a bit of a moot point for me, since settings are what I'm interested in rather than data. I use nfs-common and nfs-kernel-server packages on both servers (both are sharing NFS drives), /etc/exports and /etc/fstab for mounting by UUID (rather than device).

Be very careful if you have real-time monitoring enabled as it can create a race condition if JF starts up and can't find any of your media. It will start deleting the entries in the DB until 1) your mount comes up and 2) you restart the container (since Docker won't see the new mount). Without real-time monitoring, I can restart either of my servers (I have a very stupid NFS setup right now) and the client doesn't panic about it. Only thing that may happen is if somebody tries to play media on the server that's currently down they will receive an error and that entry may be marked as missing/removed from the DB. Short restarts have avoided this in the past.