With a BCC: to devel On 6 Sep 2007 at 16:21, Jody McDonnell wrote:
> On 9/6/07, Jody McDonnell <[EMAIL PROTECTED]> wrote: > > I have pretty much completed what I'd thought about in my first > > post--and what you said sounded like a good plan--dumped the existing > > database tables to a text file, installed the MySQL 5.0.45 Community > > server, ran the grant_bacula_privileges, create_mysql_database, and > > make_mysql_tables scripts, and read my data back in via the mysql > > executable. The data looks okay--or, at least, I can get a > > decent-looking listing when I run "list volumes". > > > > I've just kicked off an incremental backup; I'll post back with results. > > My incremental backup worked! Good. > So, I would say that MySQL 4.0.18 could be considered too old for > Bacula 2.2.1. At least on Solaris (though I'm not sure if the system > architecture would make a difference). We think 4.1 is new enough. > Thanks for the quick help. Very nice! You were not the first to encounter this problem. We are now updating the release notes and hope to send out an announcement soon letting people know of the new requirement. FYI: MySQL >= 4.1, PostgreSQL > 7.4 -- 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
