On 4/14/2011 2:56 PM, Mike Hobbs wrote: > ... > > If using vchanger and a jbod setup, if a disk was to fail, how does this > failure impact bacula? How would you figure out what was on that drive > so you can re-run backups and how would you cleanup the bacula database?
That's not much different than when a tape fails when backing up to tape. If an i/o error occurs, Bacula will fail the job and mark the volume in error. You can query from within bconsole what jobs were on a volume. The difference from tape is that the tape is only one volume, whereas a failed hard drive could contain several volumes. So you would have to re-run jobs that used any of the volumes on that failed drive. With vchanger, a unique "magazine number" is assigned to every drive, and that magazine number is part of the volume file name, (and barcode label), so it is easy to see which volumes are on which drive. This is a good example of why one should always have at least two backups at all times, whether using tape or disk. ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
