It'd be nice if I could classify a fill server as 'emergency only'. The idea would be that sabnzbd+ would attempt to download from all primary servers, and all secondary (non-emergency) servers, then if it can't unpack the file try and do a par2 recovery. If all of those fail, only then would it go to the emergency fill server and download whatever was needed.
That way, those of us with a regular all-you-can-eat main server plus a pay-as-you-go fill server would only hit the fill server if was absolutely necessary to do so.
As I understand it now, sab tries the primary servers, then the secondary servers, then tries par2 recovery. This can result in downloads from the secondary server that aren't strictly necessary if enough of the par2 information was downloaded from the non-emergency servers.
Thanks!
(Or rather than calling it an emergency fill server, call it a 'pay as you go' server, the implicit idea being that par2 recovery would be attempted before anything was downloaded from it.)
fill server only if par2 fails ('emergency only' fills)
Re: fill server only if par2 fails ('emergency only' fills)
All primary servers are tried before the first backup.
This is independent of par2 repair.
This is independent of par2 repair.
Re: fill server only if par2 fails ('emergency only' fills)
Yeah, but that's the problem / request. I'd like sab to try the par repair before trying the backup servers. That way if I don't need to download from the backup server (because par has enough to handle the repair), I won't.shypike wrote:All primary servers are tried before the first backup.
This is independent of par2 repair.
Re: fill server only if par2 fails ('emergency only' fills)
That's much to complicated.
It would mean inserting extra articles in the middle of files afterwards.
Sorry, but that would make SABnzbd so much more complicated for just too little gain.
It would mean inserting extra articles in the middle of files afterwards.
Sorry, but that would make SABnzbd so much more complicated for just too little gain.