Markus <pet2001 <at> epbfi.com> writes:
> > 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. That might be true but its implemented as a restore job e.g. the FD reads the data and extracts the meta data and that is probably compared to the data in the database. As for the SD the backup stream is some opaque data streams it doesn't extract anything from it. So that explains why the FD is needed. Mind this can be any FD doesn't have to be the original FD that did the backup. So your could probably work around this limitation by "mis-using" the local FD on the same machine as the DIR to do the hard work of extracting the meta data. -- Marco van Wieringen [email protected] Bareos GmbH & Co. KG Phone: +49-221-63069389 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- 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.
