Ryan Novosielski schrieb: > 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?
Wouldn't it be possible that bacula checks these things once every hour? Sure it's no direct limitation for bacula, but it's somehow irritating when you look at the volume status, and don't know if bacula is doing what you think it should do. Especially for someone who just started with bacula ;) 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
