That too, but no, I was referring to the data/config folders for each container.
For example, radarr it would be the config volume you mounted. Generally, the *arrs use a volume called ‘config’, but other containers will differ.
I’ve only had to recover from backups twice in 5 years, once was my fault after fiddling with databases. But if you’re using the development/nightly branches, it’s best to be cautious and avoid having to reconfigure.
Cannot recommend container approach enough. The learning curve isn’t too bad, initially it can be daunting but best way is to jump straight in and try it.
Few things I recommend:
Same here…
Underpowered server is what I suspect. It’s taking too long to extract subtitles that it times out. Subsequent requests will work as the result is cached once it eventually finishes.
My workaround was to use external subtitles to remove the need to extract. If you’re using the *arrs checkout bazarr.
deleted by creator
A device to allow me to spread cream cheese evenly on a bagel without getting all over my fingers.
I’m thinking some sort of rotating bagel mount with a silicone tapered spike.
If using docker, you can take a copy of the docker data/config and copy it over to the new server.
Make sure to stop both docker containers before copying.
I did this to migrate from nas to nas and ignoring transfer times took me about an hour to get jellyfin, *arrs and about a dozen other containers working.