Yes, the documentation seems to indicate that the "Verify" mode was
mainly designed to verify integrity on tape rather than on disk. I can
see the point for "VolumeToCatalog" that only the last backup is used.
For "DiskToCatalog" I may want to be able to compare with a less recent
backup and also w
Looking at the docs (
https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213),
it says that DiskToCatalog only operates on the last backup:
*DiskToCatalog*This level causes Bacula to read the files as they currently
are on disk, and to compare the curre
Having seen no response so far I guess Verify jobs are not used very
often. Is this behavior of Verify just a bug or result of an incomplete
implementation? Or should this be turned into a feature request? I
really think a new "verify" command similar to the "restore" command may
be the right appro
Hi all,
I am trying to run a verify that compares the md5 checksums in the
catalog with the files on disk. Although I am using DiskToCatalog, the
verify job seems to only compare with the last backup job. If that last
job was not a Full backup then, apparently, only the changed files are
verified.
Hi Guys,
I am trying to get Bacula installed on our system, but I have a problem
that is kind of a deal breaker.
I have set it up so that when a backup runs it will always be followed by a
DiskToCatalog check, followed by a VolumetoCatalog check. This way I can
confirm that the catalogue