>>>>> "AL" == Arno Lehmann <[EMAIL PROTECTED]> writes:
AL> That might be one option, but I guess the main problem is that Bacula AL> simply doesn't handle things very well when the writing-to-disk phase AL> has problems. You'd need something more integrated into the SD, or AL> implement some way to signal "re-try this part to the next disk" to AL> the SD. I have a hard time believing there is no way to say "whoops, I accidentally lost volume 5 in a fire.... Please continue as if it doesn't exist and all the files that were on it should no longer exist in the catalog". That's really what I need at the moment (I know which volumes are bad). Trying to guess at how the schema works (danger!) it looks like you might be able to look at the jobmedia table and use it to remove stuff for a broken volume from the Files table so it would get backed up next time and suddenly be needed again. But that's based on not reading any documentation on what the columns actually mean; but if someone says I'm on the right track I might go down that road :-) -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
