On 6 Sep 2007 at 13:18, Jody McDonnell wrote: > Hi all, > > I spent the day yesterday upgrading the Bacula install on our Solaris > servers from 1.38.11 to 2.2.1. Things initially seemed to work, but > the overnight incremental backup failed with some database issues. > > I should note that I am using MySQL 4.0.18 with Bacula. I've been > using this version since I started using Bacula three years ago with > version 1.34.2. I haven't upgraded our version of MySQL, mainly > because I wasn't exactly sure of the steps required to upgrade MySQL > without risking data loss. > > The only database-related maintenance I performed before the upgrade > was to compact the MySQL database via the mysqldump utility, as per > section 21.2 of the Bacula manual. > > After building and installing Bacula 2.2.1, I ran the > "update_mysql_tables_9_to_10" script to update my database tables from > 1.38-era to 2.0-era. > > I seem to have encountered two issues. The first seems to be related > to the fact that my initial configuration script included the > "--enable-batch-insert" directive. The nightly incremental backup > failed with the following error messages:
Have you tried the old MySQL without the batch insert enabled? -- Dan Langille - http://www.langille.org/ Available for hire: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------------------------- 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
