Hi,
Marcus wrote:
Ok. I thought the verify and fileset I'd set up was
supposed to verify by MD5 checksums, but I might have
messed that up.
Nonetheless, I deleted all files from the ../dlt
directory, ran the verify again, and it passed.
Could I be verifying against the verify or something
crazy? Thanks for the help!
I assume that you do a VolumeToCatalog verify - that's what your
configuration set up at least.
When you look at the manual description, you will find
"VolumeToCatalog
This level causes Bacula to read the file attribute data written to
the Volume from the last Job. The file attribute data are compared to
the values saved in the Catalog database and any differences are
reported. This is similar to the Catalog level except that instead of
comparing the disk file attributes to the catalog database, the
attribute data written to the Volume is read and compared to the catalog
database. Although the attribute data including the signatures (MD5 or
SHA1) are compared the actual file data is not compared (it is not in
the catalog)."
Which means you compare what you backed up with the catalog, not the
catalog with what you have on disk. DiskToCatalog or Catalog might
better fit your needs.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
