Hello, the last 2 tests:
Tuesday, July 24, 2007, 2:00:43 PM: FS> Actually, that gives me another idea. While I've never used it myself, you FS> may be able to get more details by running some jobs with strict mode turned FS> on on your mysql catalog. FS> http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html FS> If your bacula installation is doing something that would cause the data FS> stored to be wrong, such as storing a value that doesn't fit in the column FS> type, I believe this should turn it from a silent warning into a fatal error, FS> making it easier to track down. 1. I've set for MySQL: sql_mode=TRADITIONAL and run again all the jobs. No errors were reported as it was before. Tested restore jobs. Again 1 of them had errors (one RPM file with wrong size and restored less files). 2. So this was a time to check Julien's ideat to try dbcheck. Run: dbcheck -c /etc/bacula/bacula-dir.conf -v -f (I first created 2 indexes as dbcheck otherwise run forewer) 0 problems found for all the steps! Anyway I tried again a restore - same problem. So it is not one that can be fixed by dbcheck. I don't have any other ideas to check with to provide more cases. It's developers turn now... Regards. ------------------------------------------------------------------------- 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
