-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Read information from MySQL about what it takes to upgrade MySQL from
4.x to 5.x. That is not Bacula specific.
Bacula doesn't care, except it can't be linked with the wrong version of
MySQL shlibs. Check the daemons with ldd -v and you'll see what dyn
I'm still getting the error after trying the ALTER command (I ran it
on the FILE table which was absent minded of me since the error was on
the batch table, ah well). I learned some more about the batch table
and found out from a mailing list that it is a temp table meaning the
ALTER solution will
Yups. You could switch to postgres ?
Michael
On Nov 16, 2007 1:49 AM, Jason Martin <[EMAIL PROTECTED]> wrote:
> MySQL has its own size limits on files. See:
> http://wiki.bacula.org/doku.php?id=faq#why_does_mysql_say_my_file_table_is_full
>
> -Jason Martin
>
>
> On Thu, Nov 15, 2007 at 05:44:44PM
Sorry my mistake:
You are using a MyISAM table and the space required for the table
exceeds what is allowed by the internal pointer size. MyISAM creates
tables to allow up to 4GB by default (256TB as of MySQL 5.0.6), but
this limit can be changed up to the maximum allowable size of 65,536TB
(256
Hello,
I was hoping someone could help me identify what is going wrong with
my backup job?
I recently updated from 2.0.3 to 2.2.5 so that building of directory
trees for restores were faster (and I am quite pleased). After I
updated, everything seemed fine, I was able to run several incremental
MySQL has its own size limits on files. See:
http://wiki.bacula.org/doku.php?id=faq#why_does_mysql_say_my_file_table_is_full
-Jason Martin
On Thu, Nov 15, 2007 at 05:44:44PM -0600, Nick Jones wrote:
> Hello,
>
> I was hoping someone could help me identify what is going wrong with
> my backup job
