> On Dec 19, 2020, at 10:49, Phil Stracchino <ph...@caerllewys.net> wrote: > > If a volume errors during a job, Bacula will write an EOF and continue > on the next tape. Everything SUCCESSFULLY written to that tape volume > prior to the error should still be restorable, but you should consider > manually flagging the errored tape read-only. >
Thanks, Phil. This is helpful. Is there any way to validate a completed backup against the contents on disk? As it turns out, I think the errors I have been getting have been related to a faulty LTO drive. I’ve switched out the drive mid-backup and things seem to be proceeding normally, but I’m wondering now if I should just restart the backup from the very beginning, since I don’t think I can trust the data written by the faulty drive to be correct without some way of verifying it. >> 3) If I manage to get Bacula to forget about the files on the volume with an >> error, and then do an incremental backup subsequent to the full backup, will >> the incremental backup contain the files on the missing volume, making a >> complete set between the full and incremental volume? > > You can't do that. If you remove a volume containing part of a Full > backup set, then the full backup is no longer valid and Bacula cannot > base a new incremental or differential off it. > So if a volume within a backup set were lost or damaged, would I be able to rebuild the catalog from the remaining tapes using bscan (or some other way), and recover at least some of the files in the backup? Or would the entire backup become useless? Assuming I could somehow partially rebuild the catalog, are you saying that I would not be able to do an incremental backup from the recovered catalog, and would have to start again with a new full backup? Thanks, Yale _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
