Page 1 of 1

NZB Backup Behaviour

Posted: June 15th, 2018, 8:49 am
by methanoid
When you add an NZB to the queue it goes to the backup folder. Even if the download fails cos incomplete or whatever.

1) Would like to only backup successful downloaded NZBs

When you add a NZB to a category it still just goes to the same backup folder

2) Would like the category to be preserved by storing the backup NZB in the same category folder in the backup dir.



Personally I don't worry about duplicated downloads. But I do find that some TV shows that are subject to DMCA takedowns mean I end up downloading 5 or 6 diff NZBs (all same name) before I find a live one.

Why do I care? Well, if you think about it, if you have an NZB then you have a form of cloud backup of the file. I'd like to store my SUCCESSFUL NZBs, sorted out by categories.

Re: NZB Backup Behaviour

Posted: June 16th, 2018, 2:36 am
by safihre
The NZB Backup is a bit of a bonus-feature and not used by a lot of users so creating additional options/switches for it would not be beneficial.
If you want specialized behavior, you should maybe write your own post-processing script that after each job handles the moving of the NZB to the right place?

Re: NZB Backup Behaviour

Posted: June 16th, 2018, 3:49 am
by methanoid
Except it moves it before job is finished :-(

Re: NZB Backup Behaviour

Posted: June 16th, 2018, 7:39 am
by sander
methanoid wrote: June 16th, 2018, 3:49 am Except it moves it before job is finished :-(
After the download your own post-processing script can decide to remove the faulty NZB from the backup directory? See https://sabnzbd.org/wiki/scripts/post-p ... ng-scripts

Re: NZB Backup Behaviour

Posted: June 16th, 2018, 9:46 am
by safihre
I think at time of post processing script you can also access the specific temporary directory of the job (only removed at the very end).
In there is an __admin__ folder that contains the original NZB file. You could also use that :)