On Tuesday, September 15, 2015 at 3:55:41 PM UTC+2, David Pearce wrote:
> So a verify job will check the signature stored in the database against the 
> files on the client or against what is stored on the tape?

Hi David,

reading your question and the manual, i think the answer is, yes it reads from 
the catalog database.

But we have to read ahead. Following that link
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-160001.8
under verify it looks like the catalog is filled up with signatures when the 
file was written the first time. So you can check the integrity of the files on 
the tapes and on your remote server.

Following that link
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-990008.2
it is described that you can do a manual filling the catalog.
With that information you can compare the files on tape and on disc.
With manual filling the catalog you will get the signature from the file from 
disc on that moment you run a verify job with InitCatatlog.


Now if you have signature enabled catalog database will be filled up directly 
by backing up a file. After that you can compare the files on the tape with the 
signature in the catalog or the files that are still on disc.

Concluding now we know that with signature enabled the catalog gets its data in 
time of doing a backup.
If you run a job with InitCatalog i don't know it. But i think it will read the 
files on disc and writes it to the catalog. This only makes sense if we compare 
the functionality of working like tripwire and checking the files on the tape.

To be 100% sure that information have to be written to the documentation from a 
developer.


Regards Marco

-- 
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.

Reply via email to