Today I have downloaded some really old and broken stuff. I have 1 primary and 2 backups, but still some nzbs fell below the health threshold and were paused, others failed the par repair. This is the stuff I need and there's no other place to get it. I am thinking of getting 1 or 2 additional block accounts for backup from other backbone providers, to try and complete the downloads.
What I would like to ask is this:
- Can NZBGet re-download the nzbs, but ONLY try and re-download the missing/broken blocks/parts of the files? I mean, after I've setup the additional backup servers. You see, these nzbs were pretty broken, so they already used a lot of traffic from my backup block accounts (hundreds of GBs). And the question is, does NZBGet is capable of "smart" re-downloading, when it skips already successfully downloaded blocks/parts of the broken files, so not to waste the backup block account's traffic again. Or does it simply re-download the complete nzb and all the files (good and broken) from scratch?
- If it doesn't support "smart" re-downloading of missing blocks/parts, does NZBGet at least support the skipping of files already present (like for example Alt.Binz)? I mean, is there any way to re-download with NZBGet and minimize the waste of traffic in any way?
- So what does Download Again exactly do, and how it works? Why and when would you use it (that is, if it doesn't work as I described in the questions above)?
- Same for Post-Process Again. How does it work and why/when would I use it? I mean if it failed the post-processing before, what do you people do, to make the Post-Processing Again useful?
Thanks in advance for any help.