Maybe this is more of a comment than a question, as I've scoured the docs and haven't found and answer.
But... I'm using Bacula for my home development network, web server, mail server, etc. I'm offsite except for 2 weekends a month. I don't have an autoloader, so I have 2 tape drives, and usually time it so one backup fits on one tape, and switch tapes every other weekend. A week ago I had just done more work than usual on one of the machines, and filled the tape prematurely. So, I woke up to a Nagios screen that looked like the set of a bad slasher movie. Not only had the tape runs stopped half way through (asking to label a new tape), but the subsequent differentials to disk were queueing up behind the failed tape runs - all just because of a filed tape. More importantly, I had another tape drive with an empty tape sitting there in the same pool. So, is there any way to, or any plans to add (in future releases) an option to: 1) allow backups to move to another storage resource in the same pool when the first one is full (if implemented, I guess a config file option) 2) NOT have backups pile up - i.e. if a backup to a tape pool "A" is waiting or failed, and another backup comes up going to a disk pool "B", let the other backup run? Thanks, Jason ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
