On 10/19/2014 14:14, Marco van Wieringen wrote: > Marco van Wieringen <marco.van.wieringen <at> bareos.com> writes: > >>> [3] Verify Jobs and File Daemons >>> For a "VolumeToCatalog" verify job, can someone please explain why I >>> need a file daemon? Can I define the job without a file daemon? I am >>> asking because I would like to be able to run verify jobs without the >>> need to have the file daemon available which created the backup in the >>> first place. >> You probably run into the fact that Bacula has made the client a >> required keyword so every Job needs one even when it makes little >> sense for that particular Job type. In 14.2 (which is in beta) we >> lifted that for Copy and Migration Jobs but as the Job assumes >> everywhere there always is a Client it means you run from one crash >> to an other. We could maybe add support for not needing it for this >> particular JobType but I'm afraid we are then in for some freak show >> again in unexpected crashes along the way. I think the client is not >> used at all so you can do the same what was possible with Copy and >> Migration Jobs e.g. use some "dummy" client. >> > To follow up a VolumeToCatalog needs indeed a client and the reason > for that is simple. It asks the client for the meta data for the file > like ctime/mtime/atime, mode etc and compares that with the database. > So it may be that you use the wrong verify option. > Hmm ... according to the manual, VolumeToCatalog reads the meta data from the volume (aka the backup) and compares it to the data in the catalog. Anyway, I'll try with a dummy client and we'll see what happenes.
-- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
