I haven't read all the details of this bug report, but it seems to me that the basic problem is that normally in major Bacula upgrade, e.g. 1.36.x -> 1.38, Bacula has new table formats. This has nothing to do with upgrading the SQL engine, but is due to the fact that the Bacula SQL table format has changed.
Updating the table require running a special update script that is supplied with the new release of Bacula. If you do not run the script, you will get an error such as: bacula-dir: Fatal error: Version error for database "bacula". Wanted 9, got 8 as reported in this bug. This indicates that Bacula was upgraded, but Bacula's tables were not upgraded. The upgrade can either be done manually by invoking the appropriate update script, or it can be automatically done when installing the new package (the rpms do an automatic update for the user). The procedure (what to do, where to find the script) is documented in the ReleaseNotes file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
