Missing blocks go up when repairing & backup server used.
Posted: April 4th, 2016, 9:15 pm
I have 2 servers, priority 0 (P0) and priority 1 (P1). The P1 account is a set GB amount so I want it for backup only.
1) I want P1 to be a backup only when required. If it's enabled in sab, the bandwidth is being used constantly, but in a smaller amount than P0. Shouldn't this only be accessed if there are missing blocks at the end of the download?
2) Since P1 bandwidth is getting used when I don't need it, I disable the account in sab's settings. I recently had a file that was 610 blocks short. I went into sab's settings, left my main account (P0) used for the original download active and also enabled the P1 account. I selected 'retry' and the original nzb file. After the attempt to repair was complete, it says I am 718 blocks short now. How could I lose blocks?
3) In the 'retry' option there is a space for a password now. Retry seems to work without entering info in here. Is this only required when an nzb requires a password?
1) I want P1 to be a backup only when required. If it's enabled in sab, the bandwidth is being used constantly, but in a smaller amount than P0. Shouldn't this only be accessed if there are missing blocks at the end of the download?
2) Since P1 bandwidth is getting used when I don't need it, I disable the account in sab's settings. I recently had a file that was 610 blocks short. I went into sab's settings, left my main account (P0) used for the original download active and also enabled the P1 account. I selected 'retry' and the original nzb file. After the attempt to repair was complete, it says I am 718 blocks short now. How could I lose blocks?
3) In the 'retry' option there is a space for a password now. Retry seems to work without entering info in here. Is this only required when an nzb requires a password?