Jason Martin schrieb: > I performed a scheduled incremental backup (to a file-device) of > my system, followed by a VolumeToCatalog verify. The verify failed and > included > the following log entries: > > 07-Nov 23:19 butler-dir JobId 428: Fatal error: verify.c:730 > bdird<filed: bad attributes from filed n=-2 : No data available > 07-Nov 23:19 butler-dir JobId 428: Fatal error: Network error > with FD during Verify: ERR=No data available > 07-Nov 23:19 butler-sd JobId 428: Job > MalVerify.2007-11-07_23.10.03 marked to be canceled. > 07-Nov 23:19 butler-dir JobId 428: Fatal error: No Job status > returned from FD. > > I don't understand why VolumeToCatalog involes the FD -- I would > think the FD is only involved in a DiskToCatalog check. Any > suggestions?
Yes, the verify code is in the FD. You can even use an other client's FD in your config for verify jobs. I use the directors FD for all of my verify jobs, you have just to add 'client = otherfd' to the job config. Ralf ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
