SABnzbd Forums

The thing is that I use 2 or 3 different Usenet servers but they all have different retention policies.
So for the sake of explanation Server A (primary) has 100 days and Server B (backup) has 200 if I add an nzb that is 150 days old obviously I'll want to download it with Server B but there is no way I can prevent sabnzbd from trying to get the files from Server A first.
So assigning server specific nzbs would make queue management a lot easier and possibly downloading faster, since sabnzbd doesn't probe server A for the files first! I'm sure there is someone else out there that can relate to this problem!
Anyway... hope it isn't too complicated to implement!

Oh... and keep up the great job!

Have you actually measured that things go slower?
SABnzbd is all about automation and selecting a server per job goes against that.
I don't see how this would make queue management easier.

We have been thinking about a per-server retention threshold, that will
ignore a server when an article is likely beyond it's age.
But that's for a future release.

Well I'm assuming that quering the server for a file takes time... so if before getting the information from the backup server it queries the main server it will waste time since I already know that the main server doesn't have the file!
Anyway that server thing you talked about sound pretty cool!

The bulk of the time is used to receive the actual articles.
Unless the server with the short memory is very slow in reporting that it
doesn't have the article, you'll likely won't notice anything.
However, the higher your (maximum) download speed, the more likely a delay is.