Skip to content

# SABnzbd - Basic Setup

This basic example is based on the use of docker images

Keep in mind the path are setup so it works with hardlinks and instant moves.

More info HERE

The default path setup suggested by some docker developers that encourages people to use mounts like `/movies`, `/tv` and `/downloads` is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.

But you're able to change this, by not using the pre-defined/recommended paths like:

- `/downloads` => `/data/downloads`, `/data/usenet`, `/data/torrents`
- `/movies` => `/data/media/movies`
- `/tv` => `/data/media/tv`

Note

Settings that aren't covered means you can change them to your own liking or just leave them on default.

I also recommend to enable the `Advanced Settings` on the top right.

## General

### Tuning

`Settings` => `General` => `Tuning`

I recommend setting a sane maximum speed and then limiting below that, to keep your internet connection happy. You can use `Settings` => `Scheduling` to toggle the limit on and off based on time, slowing it down while your family is using the internet and speeding it up at night when they're not.

## Folders

### User Folders

`Settings` => `Folders` => `Users Folders`

Here you setup your download path/location.

ATTENTION

1. You set your download location in your download client
2. Your download client ONLY downloads to your download folder/location.
3. And you tell Radarr where you want your clean media library
4. Radarr imports from your download location (copy/move/hardlink) to your media folder/library
5. Plex, Emby, JellyFin or Kodi should ONLY have access to your media folder/library

Your Download and Media Library should be NEVER the same locations

### System Folders

`Settings` => `Folders` => `System Folders`

I recommend the .nzb Backup Folder because sabnzbd doesn't have a hidden history and having remove from history enabled in Sonarr/Radarr is the best method. This allows you to see your past downloads and it is used for duplicate download detection/prevention. Default is empty, I picked history because it is easy. It'll end up in the `/config` folder for Docker, which isn't crazy... but this is literally compressed nzb files, so can end up pretty big. But the choice is yours what you prefer.

## Servers

`Settings` => `Servers` => `Add Server`

USP = Usenet Service Provider

1. Server description.
2. The hostname you get from your USP.
3. The port that you get and can use from your USP.
4. Make sure you enable `SSL` so you get a secure connection to the USP.
5. Username that you got or created with your USP.
6. Password you got or created with your USP
7. Use the lowest possible amount of connections +1 to gain your max download speed.
8. How long the articles are stored on the news server.
9. For unreliable servers, will be ignored longer in case of failures

## Categories

`Settings`=> `Categories`

Covered and fully explained in SABnzbd - Paths and Categories

## Switches

### Queue

`Settings` => `Switches` => `Queue`

1. When during download it becomes clear that too much data is missing, abort the job. and makes sure Sonarr/Radarr will get a notification and can look for another release.
2. Since we have the .nzb history folder, you can decide what you want to do here w/ duplicate downloads. Mine is set to Tag job, but Pause or Fail job may make sense too.
3. In case of "Pause", you'll need to set a password and resume the job. or you set it to "Abort" and Sonarr/Radarr can look for another release.
4. Suggest this sort so that the most likely to still be there stuff is downloaded first.
5. If your hardware isn't up to snuff, including cpu and/or io performance, disabling Direct Unpack and/or enabling Pause Downloading During Post-Processing can help. Defaults are fine for most hardware though.

### Post processing

`Settings` => `Switches` => `Post processing`

1. If your hardware isn't up to snuff, including cpu and/or io performance, disabling Direct Unpack and/or enabling Pause Downloading During Post-Processing can help. Defaults are fine for most hardware though.
2. Only unpack and run scripts on jobs that passed the verification stage. If turned off, all jobs will be marked as Completed even if they are incomplete.
3. Unpack archives (rar, zip, 7z) within archives.
4. This can help with subs that are in folders in the rar because sonarr/radarr don't look in sub-folders.
5. Some servers provide an alternative NZB when a download fails. I have it enabled no guarantee that it works.
6. Helps with de-obfuscation, but probably is handling the same case sonarr/radarr do okay with. Not sure how this one does, I have it enabled, but its also newish.
7. When sorting, use tags from indexer for title, season, episode, etc. Otherwise all naming is derived from the NZB name.

## Sorting

`Settings` => `Sorting`

MAKE SURE THAT SORTING IS ENTIRELY DISABLED

## Recommended Sonarr/Radarr Settings

The following settings are recommended to for Sonarr/Radarr, else it could happen that Sonarr/Radarr will miss downloads that are still in the queue/history. Being that Sonarr/Radarr only looks at the last xx amount in the queue/history.

### Sonarr

Sonarr - [CLICK TO EXPAND]

`Settings` => `Download Clients`

Make sure you check both boxes under `Completed Download Handling` at step 3.

Select Sabnzbd at step 4 and scroll down to the bottom of the new window where it says `Completed Download Handling` and check both boxes.

### Radarr

Radarr - [CLICK TO EXPAND]

`Settings` => `Download Clients`

Make sure you check both boxes under `Completed Download Handling` at step 3,

and both boxes under `Failed Download Handling` at step 4.

Thanks to fryfrog for helping me with the settings and providing the info needed to create this Guide.

Questions or Suggestions?

If you have questions or suggestions click the chat badge to join the Discord Support Channel where you can ask your questions directly and get live support.

Last update: August 15, 2022 16:42:07
Back to top