>>>>> On Sat, 5 Jul 2008 14:31:36 -0500, Michael Short said:
> 
> Today I am questioning the integrity of a backup archive created for a
> full backup. We created the backup with the intention of an easy
> restore (though we did have other means to recover data). However,
> when we proceeded to run the restore, numerous archive errors were
> found. First we had checksum errors, then the restore failed. The only
> way to recover what was left was to use bextract with the -p argument.
> 
> The backup was made from a Windows 2003 SBS to a local usb drive. The
> windows machine was running the FD and SD version 2.4 and the director
> was running 2.2.7. Though I am willing to bet that this was just a
> freak accident caused by unusual circumstances (and perhaps a faulty
> usb drive.)
> 
> We only had one problem doing the restore and that was bextract
> inability to strip windows paths from backups. Bextract should feature
> all the regex and recovery options that are available via bacula.
> 
> My question is, is there a way to check the integrity of bacula
> archives? I have made full backups to this usb drive before and I am
> unsure if this was an isolated incident.

I think the bls command will test the checkums in the volume.

For the future, I suggesting running a job with Type=Verify
Level=VolumeToCatalog.  It only works with the last job that matches the
VerifyJob option, so you can't use it to check all of the old jobs.

__Martin

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users