The different verify jobs are not that clear to me that they would do what I'm trying to do.
I have very long retention on Full backups, and every so often say 3-6 months I want to read the volumes back and compare the actual data against the catalog checksum. I think this is the VolumeToCatalog level but it refers to attribute data and not the actual data blocks. Because we are making heavy use of disk volumes and not a more durable media like tape we don't want to depend on the storage systems background scrub, but actually make sure the bareos volumes have all data that the catalog expects it to have. How would one do this? Does the VolumeToCatalog actually read the volume data and calculate the checksum to compare to the catalog? \ If it does what happens if it fails a file? Should we purge the job that file is attached to so it gets picked up in the next incremental? Were also looking at making heavy use of Incremental Always and while we have consolidate jobs similar issue, will it just copy blindly the (mostly) unchanging data from the old full forward or will it actually compare the checksums of actual data. Thanks -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
