Move completed .nzb's to a "completed" folder instead of bak

[Jere_Tristan]

Well yeah, pretty much move completed .nzb's to a "completed" folder instead of the "bak" folder.

In this case, if you have a catastrophy and lose your whole queue, you already know which ones have been downloaded (and completed).
There could also be a "failed" folder for all the downloads that have failed.
"bak" should only hold the nzbs that are currently in the queue imo.

Thanks.

[Jere_Tristan]

Also, if you delete a queue item, its nzb should move to a "deleted" folder.

[young-einstein]

Well yeah, pretty much move completed .nzb's to a "completed" folder instead of the "bak" folder.

In this case, if you have a catastrophy and lose your whole queue, you already know which ones have been downloaded (and completed).
There could also be a "failed" folder for all the downloads that have failed.

I've just had this exact problem two nights ago ... and it caused me a lot of pain having to sort through my entire backup folder [which is several hundred nzb's].

That's when I realised that it's actually really easy to do this just using a very simple post processing script.

I literally knocked this up in under two minutes, so it's about as basic as it gets, but it still does what I need it to.

[This is a Linux script, but it's essentially the same thing for Windows, you'll just have to re-code it slightly.]

Code: Select all

#!/bin/bash

if [ $7 = "0" ]; then
	mv "/media/sabnzbd/backup/$2.gz" /media/sabnzbd/backup/completed/
else
	mv "/media/sabnzbd/backup/$2.gz" /media/sabnzbd/backup/failed/
fi

Then all you need to do is set that as the default post processing script for your downloads, and it'll automatically move the backup nzb files to either the completed / failed folder when they're finished downloading.

Too easy ...

The only thing it doesn't do ... is remove the backup files if you delete something from the queue.  I really don't do that very often though, so it's not really a big concern for me ...