How does SAB work if you define 2 Servers and 2 Backup Servers?
Does it download half the queues from each of the 2 servers and for any missing queue items does it download half from each of the 2 backup servers?
Thanks
How does SAB work with 2 Servers and 2 Backup Servers?
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: How does SAB work with 2 Servers and 2 Backup Servers?
Backup servers are only used when the primary servers don't have an article.
So ideally, they're not used.
The two primary servers will be used for different articles.
The fastest one will be used the most.
So ideally, they're not used.
The two primary servers will be used for different articles.
The fastest one will be used the most.
Re: How does SAB work with 2 Servers and 2 Backup Servers?
Great. So if you have two backup servers both are checked?
Re: How does SAB work with 2 Servers and 2 Backup Servers?
Can SAB also handle two two primary servers with different retentions and both are checked before trying a backup?
Re: How does SAB work with 2 Servers and 2 Backup Servers?
The primaries are checked both before using a backup.
Except when you set a retention time for one (or both) of the primary servers
and the article is outside of that retention time.
People use this to avoid wasting time with primary servers that are
very unlikely to have the article due to retention time.
Example: you have a cheap (or free) server with a very low retention time
and a paid block server for backup.
Except when you set a retention time for one (or both) of the primary servers
and the article is outside of that retention time.
People use this to avoid wasting time with primary servers that are
very unlikely to have the article due to retention time.
Example: you have a cheap (or free) server with a very low retention time
and a paid block server for backup.