Author Topic: Post Age Per Server  (Read 3901 times)

Offline hammer

  • Contributor
  • ***
  • Posts: 6
Post Age Per Server
« on: July 13, 2008, 04:33:37 am »
I use two servers and need Alt.Binz to recognize the post dates when downloading.  One server has less retention then the other one and downloads older then that date will not successfully download.

Offline hammer

  • Contributor
  • ***
  • Posts: 6
Re: Post Age Per Server
« Reply #1 on: July 13, 2008, 04:57:31 am »
If I want two Primary Servers and use the one with the greater retention rate as a backup to the second one with less retention rate, then I shouldn't lose any articles - correct??

Offline Hecks

  • Contributor
  • ***
  • Posts: 2011
  • naughty cop
Re: Post Age Per Server
« Reply #2 on: July 13, 2008, 07:27:30 am »
If I want two Primary Servers and use the one with the greater retention rate as a backup to the second one with less retention rate, then I shouldn't lose any articles - correct??

Yes, correct.

Offline hammer

  • Contributor
  • ***
  • Posts: 6
Re: Post Age Per Server
« Reply #3 on: July 13, 2008, 06:05:10 pm »
Great!  I withdraw my original request then as my problem is solved!

Offline thebeing

  • Contributor
  • ***
  • Posts: 30
Re: Post Age Per Server
« Reply #4 on: November 24, 2012, 05:12:54 am »
I'd like to re-open this request, since the suggested solution of using Primary & Backup servers doesn't seem to work in my case.

I have one IPv6 server with ~900 days retention & 10 connections max & auth, and then I have my ISP's IPv4 server with ~30-60 days retention & 4 connections max w/o auth. My ISP's server temporarily blocks connections when hundreds of requests are made for missing article parts. Setting the IPv6 server as a backup doesn't work, since I'm already using the maximum allowed connections (failure to connect). Reducing it 6 connections IPv6 +  4 connections IPv4 (w/ 4 connections IPv6 backup) doesn't work either. A single part gets download and then failure to connect, and I wouldn't want to do this anyways since it hurts my overall speed significantly.


A way to automatically disable a server based on post age seems to be the optimal solution for this issue, so no missing part failures, fall-backs, or server thrashing ever occurs.

Other enhancements which may be useful:
An option to automatically re-try all missing/corrupt parts on each primary server once in succession, until success or all fail.
An option to set a global connection limit for all servers with the same IP/Domain, instead of adding more connections + logic which prioritizes connections to identical backup servers.
An option to temporarily disable a server for an NZB collection after a user set threshold for missing/corrupt parts is exceeded.

Offline earthcrisis

  • Contributor
  • ***
  • Posts: 11
Re: Post Age Per Server
« Reply #5 on: April 29, 2013, 03:14:03 pm »
+1

I have the same problem here...
1 primary server (900days) and 3 backup blockaccounts(700-1500days)...

1000days old file
5 connections... and after 1minute only 1-3 connections are downloading and 2-4 are retrying to download from the primary and so on... so it will not reach full speed, because it tries every part first from the primary and then switch to backup, after download again switch to primary... and so on. :)