resent, to bacula-users On 24 Feb 2007 at 17:58, Rex Wheeler wrote:
> Does anyone know if bacula keeps track of tape soft errors? (Soft errors > being correctable errors that were corrected by the tape drive > hardware.) Bacula does not keep track of this. > I like to use the number of soft errors as an early warning indicator as > to tape failure. > > I am currently using Veritas Backup Exec and it tracks total read and > write errors both soft and hard per tape. I will typically toss a tape > if it gets any hard errors and consider tossing it when the soft error > count starts to get high. I don't like the linux support on Veritas and > I am a couple of versions behind on it. I would like to switch something > that handles linux better and doesn't require me to fork out a bunch of > cash. > > I took a look at the bacula table structure and there is a VolErrors > column in the Media table. I glanced at the source code and it seems the > column is related to higher level problems then tape soft errors. > > Does anyone know what kind of errors that the "VolErrors" column totals? See http://www.bacula.org/developers/Catalog_Services.html Number of errors during Job > > > I am currently running version 1.36.3 as offered by the default ubuntu > package repositories. I realize that the current version is 2.x, but I > haven't found a repository that allows me to install a current version > via a package manager. I will get around to building from source soon so > I can be on the current version. You might want to look at how I test tapes (when I get second hand tapes). http://www.freebsddiary.org/tape-testing.php Of note is the script that pulls back corrected errors per GB. That is at: http://www.freebsddiary.org/samples/dlt The script is FreeBSD specific, but I know one person who has taken it and converted it for use by another OS. Each OS may have its own method for querying the hardware. FWIW, I've long wanted to start using this script for pulling such information from the drive and collecting stats. For example, this is the current state. I believe this is a new tape, previously unused, but with a used DLT drive. I have no idea of the history of this drive, but it is in very good condition. I consider anything under 20 corrected errors / GB to be "good enough". But I've tested and seen correct backups with up to 600 errors / GB. $ sudo ~/bin/dlt sa0 The tape is 'sa0' Corrected errors with substantial delay: 0 Corrected errors with possible delay : 0 Total errors : 0 Total errors corrected : 0 Total times correction algorithm used : 0 Total bytes processed : 36291200 Total corrected errors / GB : 0 Total uncorrected errors : 0 Read compression ratio : 600% On tape Mbytes read : 0 On tape kbytes read residual : 71265 WRITING Corrected errors with substantial delay: 0 Corrected errors with possible delay : 0 Total errors : 7 Total errors corrected : 7 Total times correction algorithm used : 0 Total bytes processed : 763642480 Total corrected errors / GB : 9 Total uncorrected errors : 0 Write compression ratio : 270% Host requested Mbytes written : 1555 Host requested kbytes written residual : 327680 On tape Mbytes written : 576 On tape kbytes written residual : 0 -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php PGCon - The PostgreSQL Conference - http://www.pgcon.org/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
