Hello,

I believe, if I understand your request, that this feature already exists. 
It works a bit differently from what you suggest, but it also gives you a lot 
more control.  It is called Verify.  First you run a Verify job with your 
FileSet -- normally it will not be the same as your backup FileSet as you 
will see if you try the feature because in reality you do not want all files 
on your system checked.  The first Verify is done with level InitCatalog, 
then subsequent Verify jobs are run with level Catalog that then compares the 
database data that you specify (MD5, SHA1, size, ...) to the files and 
reports any differences.  Please see the manual, there are a good number of 
options.

I think the Verify that already exists has everything you want, and even more. 
As you will see after experimenting, it is not so easy to do an "automatic" 
verification of all files. They need to be carefully chosen.  For example, if 
I am editing files in a directory, I don't want my backups to complain about 
the fact that the files have changed.

Unless I hear back from you otherwise, I am considering that there is no need 
to add this to the list of projects.

Best regards,

Kern

On Friday 01 September 2006 17:47, Jesper Krogh wrote:
> 
> Item 1:   Automatically detection of silent data corruption
>   Date:   1. september 2006
>   Origin: Jesper Krogh <[EMAIL PROTECTED]>
>   Status: Unimplemented.
> 
>   What:   Detect silent data-corruption automatically.
>           When a full backup are performed there is (when configured so)
>           put checksums into the catalog. These checksums can be used to
>           detect silent corruption of data when the subsequent full
>         backup is performed by comparing the checksum with the newly
>           read files if the metadata of the file hasn't been updated
>           since last full backup. The performance cost would be next to
>           zero since all data is read and checksummed anyway.
>   Why:    A verification of diskdata is a very time/performnce comsuming
>           process especially on "large disks". This would be a
>           "shortcut" to get a nearly as good feature to detect silent
>           data corruption.
> 
>   Notes:  The idea came up when our 1TB disk went down with SCSI-errors
>           and the time didnt allow us to make a check.
> 
> 
> -- 
> Jesper Krogh, [EMAIL PROTECTED]
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bacula-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
> 

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to