It's not really a huge limitation, as far as Bacula is concerned. It's a
limitation for the USER, as you can't really look at the table and know
what is going to happen right before the next backup. However, I
understand why it might have been done this way, because the media
maniuplation really doesn't matter until the work begins. Perhaps it
should be configurable, but what would be the trigger, if not a job start?
Ralf Gross wrote:
Martin Simmons said:
Maybe you have something like a cron job that runs 'status dir' at 07:00.
Yep ;)
0 7 * * 5 /opt/bacula/etc/jobs.sh | mailx -s "Upcoming Bacula Jobs"
[EMAIL PROTECTED]
It's possible that I wrote and tested this script on Tuesday the week
before, thus I got the voluseduration message then on Tuesday and now on
Friday.
Just one last question: why does this limitation exist, that the volume
state only changes when a job attempts to use the volume?
Ralf
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
