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!
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).
Thanks for the quick help. Very nice!
Regards,
Jody
-------------------------------------------------------------------------
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
