I've never had a cache drive.  And I've always selected sabtosickbeard postprocessing.  I didn't think there was another option.  Upon setting up cache, I learned that apps with "." are not moved around, and I selected the apps to be installed "only" on cache.  Which gives me lots of confusion now. 

 

Questions I hope people can answer:

 

1. Traditionally, upon install sab, it also creates a download/complete and download/incomplete folder.  This will usually reside inside the sab folder.  Since it won't be moved by the mover script (hidden), what detects new tv shows, and moves it to array for viewing on xbmc?  sabtosickbeard script?  Is there a sickbeard post processing also?  Are they 2 different options?

 

2. What kind of settings need to be done in sab, or sickbeard?  Do anyone only have to do in sab is to set folder in categories?

 

3. Which is more advantageous?  Using sabtosickbeard?  or sickbeard post processing?

 

Thanks

 

 

Hello Jang,

 

I am modifying my post to update you with some better answers, as I was in a hurry before.

 

1. Traditionally, upon install sab, it also creates a download/complete and download/incomplete folder.  This will usually reside inside the sab folder.  Since it won't be moved by the mover script (hidden), what detects new tv shows, and moves it to array for viewing on xbmc?

 

If you don't configure Sabnzbd to do anything it will just dump the files into the complete folder on the cache drive. Then you will have to perform manual post processing after that. In this scenario the mover script won't move anything.

 

If you configure a script like sabtosickbeard, sabnzbd will send information to sickbeard and sickbeard will take over post processing (assuming you have sickbeard properly configured), including renaming it correctly, downloading all the meta info, updating it's database, and then copying it to the correct directory.

 

That last part is where the cache drive comes in. Before when you had no cache drive it was just copied to the array directly. This was likely a slow process, because your server also had to write parity at the same time. Now when sickbeard thinks it is writing to the array, the cache drive is intercepting the copy, and it's actually being copied to the cache drive. Know that this means your data is still outside the protected array, but it's beneficial because the write speed should be much improved.

 

Sometime later (usually 3 am but you can change this) the mover script will kick in, and copy that days downloads to your protected array. This takes just as long as when you had no cache drive, but to you it doesn't matter because you are sleeping (hopefully).

 

2. What kind of settings need to be done in sab, or sickbeard?  Do anyone only have to do in sab is to set folder in categories?

If you have this setup correctly it all starts with sickbeard. Sickbeard checks the TVDB sees that a new episode is available, it uses an nzb search engine (which you must configure in sickbeard) to find the NZB, once it finds it, it sends the link of the NZB to sabnzbd (this is done by grabbing the api key from sabnzbd and configuring it into sickbeard, in the same area you also tell sickbeard to apply a category called "TV")

 

Sabnzbd downloads the NZB file, then downloads the file, un-pars, and un-rars the file. In Sabnzbd you have categories configured and one of them is called TV, this is where you tell sabnzbd to apply a post processing script sabtosickbeard, which sends the file back to sickbeard for post processing.

 

3. Which is more advantageous?  Using sabtosickbeard?  or sickbeard post processing?

Not sure what is better, but I use sickbeard. My reasoning is that sickbeard is the one doing the categorization, not sabnzbd.

Hello Jang,

 

I am modifying my post to update you with some better answers, as I was in a hurry before.

 

1. Traditionally, upon install sab, it also creates a download/complete and download/incomplete folder.  This will usually reside inside the sab folder.  Since it won't be moved by the mover script (hidden), what detects new tv shows, and moves it to array for viewing on xbmc?

 

If you don't configure Sabnzbd to do anything it will just dump the files into the complete folder on the cache drive. Then you will have to perform manual post processing after that. In this scenario the mover script won't move anything.

 

If you configure a script like sabtosickbeard, sabnzbd will send information to sickbeard and sickbeard will take over post processing (assuming you have sickbeard properly configured), including renaming it correctly, downloading all the meta info, updating it's database, and then copying it to the correct directory.

 

guyonphone, when I didn't have cache drive, all I did in sabnzbd was to configure /mnt/user/Media/TV folder under category.  I believe this immediately writes the completed file directly to the array with TV share.  I did the same thing for Movies. 

 

Under Post Processing of Sickbeard, I have under my "TV download dir" as /mnt/user/Media/TV.  Then again, I didn't check "scan and process."  And yet, I find my TV episodes directly in my array. 

 

I have a few clarifications I'd like to make here, namely:

 

1. The app that actually brings the tv and movies to my array in my current setup is actually sabnzbd, and not sickbeard and couchpotato?

2. The app doing post processing (renaming) again will fall under the sabnzbd?  (I have tv sorting enabled under sabnzbd and configured to the format I want)

3. Am I using sabtosickbeard script?  I don't see where that option is enabled.  Neither did I copy any filename.py to sabnzbd installation folder.

 

That last part is where the cache drive comes in. Before when you had no cache drive it was just copied to the array directly. This was likely a slow process, because your server also had to write parity at the same time. Now when sickbeard thinks it is writing to the array, the cache drive is intercepting the copy, and it's actually being copied to the cache drive. Know that this means your data is still outside the protected array, but it's beneficial because the write speed should be much improved.

 

I have another system which I'm currently setting up.  This is the one I have a cache drive installed.  I've configured it in such a way that in categories of sabnzbd, the default directory where all downloads go to is /mnt/user/cache/.apps/sabnzbd/download/complete, and under "folder/path", I only have TV as the folder.  I assume here all downloads go to complete folder, hidden, under TV folder.  This is what you're saying correct? 

 

I also have sickbeard configured as:

 

TV download dir= :/mnt/user/cache/.apps/sabnzbd/download/complete/tv

Scan and post process= checked

Naming=configured to my liking

 

Media share in unraid is also configured to use cache.  Am I right in configuring this?

 

What's happening now:

 

During downloading, there is a file folder of the same tv name under /mnt/user/cache/.apps/sabnzbd/download/incomplete/, I assume this is correct.

After downloading, I don't notice it being inside /mnt/user/cache/.apps/sabnzbd/download/complete/tv.  Since upon checking after a few minutes of download, the show appears in my array already. 

 

A few more clarifications:

 

1. If indeed I don't have sabtosickbeard script functioning above with my old setting, it is sickbeard that is detecting the tv show in /mnt/user/cache/.apps/sabnzbd/download/complete/tv since this is the folder configured under post processing.  And I am actually relying on sickbeard to do the post processing, and sab is only configured to download.

 

2. As you have clarified in below statement, when sickbeard detects the tv show inside the hidden folder it is watching, it moves it to the array.  But since cache drive is part of the Media share in the array, it moves it to a temporary location first inside the cache drive, not in the hidden area, and the mover script moves the file to the actual array at 3 am. 

 

Sometime later (usually 3 am but you can change this) the mover script will kick in, and copy that days downloads to your protected array. This takes just as long as when you had no cache drive, but to you it doesn't matter because you are sleeping (hopefully).

 

2. What kind of settings need to be done in sab, or sickbeard?  Do anyone only have to do in sab is to set folder in categories?

If you have this setup correctly it all starts with sickbeard. Sickbeard checks the TVDB sees that a new episode is available, it uses an nzb search engine (which you must configure in sickbeard) to find the NZB, once it finds it, it sends the link of the NZB to sabnzbd (this is done by grabbing the api key from sabnzbd and configuring it into sickbeard, in the same area you also tell sickbeard to apply a category called "TV")

 

 

A few final clarifications:

 

1. When you put TV under folder in category of sab, is that equivalent to doing post processing via sab?  Or is it just telling sab to put the downloaded file under TV folder in /mnt/user/cache/.apps/sabnzbd/download/complete/? 

 

2. Is sickbeard actually watching the folder /mnt/user/cache/.apps/sabnzbd/download/complete/TV?  Or does it wait for sab to inform it that it is done downloading before it triggers post processing?  And how is sickbeard informed?  Is it through setting category in sab as TV? 

 

3. If I want to have sickbeard do the renaming, then sorting under sabnzbd doesn't have to be configured anymore?

 

Hope you understand what I mean by the clarifications above.  Thanks for the help in clarifying.

 

Sabnzbd downloads the NZB file, then downloads the file, un-pars, and un-rars the file. In Sabnzbd you have categories configured and one of them is called TV, this is where you tell sabnzbd to apply a post processing script sabtosickbeard, which sends the file back to sickbeard for post processing.

 

3. Which is more advantageous?  Using sabtosickbeard?  or sickbeard post processing?

Not sure what is better, but I use sickbeard. My reasoning is that sickbeard is the one doing the categorization, not sabnzbd.