On 10/20/2014 13:28, Marco van Wieringen wrote: > 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. >
Success! I now use my local fd to run a VolumeToCatalog verify on a backup job which was created by another computer. The shoe shining is gone. The reason for the tape doing shoe shining is now clear to me: using the original fd (which is located on that other computer), all data read by the local sd was sent to the remote fd just to do the verify calculations. Although my DLT-1 tape does not generate much more than 10 MByte/sec, it was enough to overload the network connection (which right now temporarily is a poor wireless 802.11g because ethernet is being rewired in the whole house), causing the tape to stop-and-go. Backup jobs being sent from that other machine are not a problem. I run data spooling using 4 GByte chunks. A 4 GByte chunk is despooled to the tape in about 6 minutes without any shoe shining. Thanks again for all the help, Marco! This weekend I'll make the final transition from Bacula to Bareos. We'll see how it works out. I'm running Debian 7.6.0 "Wheezy" (stable), will try to use the Debian 7.0 packages you guys provide on your website. Best regards from Chattanooga, TN Markus -- 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.
