From: Kern Sibbald Date: Sat, 19 Nov 2005 20:55:40 +0000 (+0000) Subject: Update projects X-Git-Tag: Release-7.0.0~8267 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=dad5389fca544ce28fb80b8134f1a3fecb6613cc;hp=ead004f2a3f292f19216758bf30dfc3831194fe6;p=bacula%2Fbacula Update projects git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@2605 91ce42f0-d328-0410-95d8-f526ca767f89 --- diff --git a/bacula/projects b/bacula/projects index 78f2d18339..fa2e4e824e 100644 --- a/bacula/projects +++ b/bacula/projects @@ -317,6 +317,31 @@ Item 14: Merging of multiple backups into a single one. (Also called Synthetic data can then be pruned (or not) from the catalog, possibly allowing older volumes to be recycled +Item 1: Automatic disabling of devices + Date: 2005-11-11 + Origin: Peter Eriksson + Status: + + What: After a configurable amount of fatal errors with a tape drive + Bacula should automatically disable further use of a certain + tape drive. There should also be "disable"/"enable" commands in + the "bconsole" tool. + + Why: On a multi-drive jukebox there is a possibility of tape drives + going bad during large backups (needing a cleaning tape run, + tapes getting stuck). It would be advantageous if Bacula would + automatically disable further use of a problematic tape drive + after a configurable amount of errors has occured. + + An example: I have a multi-drive jukebox (6 drives, 380+ slots) + where tapes occasionally get stuck inside the drive. Bacula will + notice that the "mtx-changer" command will fail and then fail + any backup jobs trying to use that drive. However, it will still + keep on trying to run new jobs using that drive and fail - + forever, and thus failing lots and lots of jobs... Since we have + many drives Bacula could have just automatically disabled + further use of that drive and used one of the other ones + instead. ============= Empty RFC form ===========