Hi Ana, 

Em Sex, 2014-09-12 às 23:10 -0300, Ana Emília M. Arruda escreveu:
> ... You can try to put a Run Script directive on job definition like
> this:
> RunScript {
>     RunsWhen = After
>     RunsOnFailure = yes
>     Command = "/path/myscript.sh"
> }
> And you could do some kind of shell script that could look for and delete the 
> volume created and not used by your job. This way Bacula should create a new 
> volume for the next job.
> Sorry I didn't had time for thinking about the script, but here is my idea 
> for solving this situation.

Thanks. Excelent idea Ana, in that way I can write a scrit that deletes
the volume if the size is small (an empty one).

I'll let my configuration of an volume per day with all backups from all
services, that I posted before, to complete a cycle. If that works well,
I'll keep that way, if not, I'll follow your suggestion.

Best regards,
Gean




------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users