NZBGet on host1, other apps on host2 - Post processing over NFS?
Posted: 25 Jul 2017, 10:29
I'm looking to replace my current host that runs sab with all my other applications with a more modular server setup. Since I'm running under ESXi, I was thinking of running NZBGet on its own host, and then running other applications like CouchPotato, Sickbeard, etc. on a different host.
I have NZBGet running on a new CentOS 7 host, and all is good. But now that I'm starting to experiment with pointing my existing apps like CouchPotato to this new host I'm starting to wonder if this is the right move.
When NZBGet and CouchPotato are on the same host, they can access the same local hard drive. So when a download is finished, CouchPotato has direct access to that disk and can run the needed post processing tasks before moving the file to the final destination (my NAS).
But when these services are on different hosts, am I making things harder than they need to be?
I believe in my case I need to setup NFS on both servers. The nzbget server becomes the NFS server, and the CouchPotato server becomes the NFS client. After sharing the movie download directory over NFS from the NZBGet server, I need to mount that on the CouchPotato server (using autofs), and update the couchpotato settings to use that mount point as the FROM folder. I also need to update the CouchPotato server to also mount the NAS share point, as that will be the final destination CouchPotato will send to.
Does that sound right? If it does, then doesn't this seem a bit messy?
NZBGet will download locally, then CouchPotato will re-name and (I believe) download the file locally over NFS so that it can then send it over NFS again to the final destination.
I have NZBGet running on a new CentOS 7 host, and all is good. But now that I'm starting to experiment with pointing my existing apps like CouchPotato to this new host I'm starting to wonder if this is the right move.
When NZBGet and CouchPotato are on the same host, they can access the same local hard drive. So when a download is finished, CouchPotato has direct access to that disk and can run the needed post processing tasks before moving the file to the final destination (my NAS).
But when these services are on different hosts, am I making things harder than they need to be?
I believe in my case I need to setup NFS on both servers. The nzbget server becomes the NFS server, and the CouchPotato server becomes the NFS client. After sharing the movie download directory over NFS from the NZBGet server, I need to mount that on the CouchPotato server (using autofs), and update the couchpotato settings to use that mount point as the FROM folder. I also need to update the CouchPotato server to also mount the NAS share point, as that will be the final destination CouchPotato will send to.
Does that sound right? If it does, then doesn't this seem a bit messy?
NZBGet will download locally, then CouchPotato will re-name and (I believe) download the file locally over NFS so that it can then send it over NFS again to the final destination.