TLDR can the *arr stack be setup to move the completed files to another server?
Before I potentially waste many hours trying to get this setup, need a bit of advice.
Been old school for a couple of decades. Running a Linux box on bare metal with a torrent client. Client gets downloads from a RSS feed and when completed, I manually copy them to my Linux server (Big JBOD), and use filebot to rename and move them to the various directories.
Been interested in switching to something more automated for a while and want to give sonarr etc. a go.
I already have a proxmox box running a few VMs so was thinking of setting up docker on there with the various sonarr, radarr, etc. and then have the completed files moved over to my linux server. The server was built around 2010 and great for streaming but I think running docker and everything else would kill it.
It is possible to set it up so that when the download is finished on the docker box, it’s copied across to the server?
All the guides I’ve read suggest having the docker stack on the same box as the server but I’m reluctant because if it’s age.
Yes, that’s possible. The *arr’s need to be able to access the path on your storage server though. I’m using syncthing to move files between two locations.
While I don’t use my *arr stack in quite the same way, I do not see why you wouldn’t be able to do it.
You’ll need to set up mount points, and the permissions can be a bit finicky but other than that you shouldn’t have an issue.
I currently have my download client setup on a separate server (VM on esxi) and my *arr stack set up on unRAID and it will kick off the download, then move the downloads between servers no problem.
Your severs are on different networks?
(edit) and yes the hardest part for me was the permission to setup between NFS and then both system without setting up everything on 777
Sorry, I guess kbin doesn’t notify you of replies to your comments? Just now saw this. My servers are on different vlans actually. My esxi node is on my old infra vlan, where as the unraid server is on my new one. I just haven’t gotten around to moving everything off the old vlan.
Was easier for me just to create an exception for those two servers to talk across vlans than to bother moving everything over. It’s one of those “i’ll get to that one day” kind of projects.
I think the main reason to keep the data on the same datastorage is to continue seeding your torrents without duplicating the files.
*arr services are renaming the downloaded file into a library with metadata that are used by your player or service (Kodi/Jellyfin/Plex) therefore if you want that your torrents client continue seeding after the download you need to keep the file like it was: The solution is hardlink and it only works on the same datastorage, because you just copy the links to a file not the data itself (basically)
if your server and datastorage are on the same local network you could simply mount a remote folder on the server hosting the torrent client so it download directly on the other system that has the storage?
That’s what I’m doing currently as “temporary” solution (almost a year now…)
Services (sonarr, radarr, Jackett, Jellyfin, transmission/…) on a Raspberry Pi 4
Raid 5 storage on my computer for the TV Shows Raid 1 storage on a NAS for the movies
Both shared via NFS and mounted on the raspberry pi
(yeah it means i have to keep my computer, my Nas and the raspberry pi ON all the time)
Totally possible. In fact, I do it.
Honestly, I feel like the majority of users do, since using gdrive for storage has been so popular.
You just need a way for *arr to access the filesystem of the server, whether that’s SMB/NFS shares or whatever.
