Re: [Bacula-users] backup issue with batch table

2007-11-19 Thread Ryan Novosielski
-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 dynamic
objects it's using.

Nick Jones wrote:
> 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 not work for this.
> 
> Are there any serious implications in migrating the tables from v 4.x
> to 5 by recompiling?  I only found this in the docs:
> "If you upgrade MySQL, you must reconfigure, rebuild, and re-install
> Bacula otherwise you are likely to get bizarre failures. If you
> install from rpms and you upgrade MySQL, you must also rebuild Bacula.
> You can do so by rebuilding from the source rpm. To do so, you may
> need to modify the bacula.spec file to account for the new MySQL
> version."
> 
> It doesn't mention the catalog needing recreation so hopefully this
> will be smooth and easy.  Does anyone recommend against this for any
> reason?
> 
> Thanks alot
> 
> Nick
> 
> 
> 
> 
> On Nov 15, 2007 5:49 PM, 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 -0600, Nick Jones wrote:
>>> 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
>>> backups of the same identical job except on a different / identical
>>> tapeset that is now offsite.
>>>
>>> I am trying to create a new backup on the secondary set of tapes and I
>>> keep running into this error after a day and a half.  Table 'batch' is
>>> full.  I'm using a large my.cnf config
>>>
>>> Another error is:   Attribute create error. sql_find.c:333 Request for
>>> Volume item 1 greater than max 0 or less than 1 I may have read
>>> somewhere that this is caused by a disk space issue so I suspect I'm
>>> running out of space.
>>>
>>> The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
>>> space.  I have 16GB free on the root partition where mysql lives,
>>> however the bacula sql tables and working directory are symbolically
>>> linked to a RAID with 80GB of free space.  I had hoped this would be
>>> enough.  Is it not?
>>>
>>> Thanks for any hints on identifying the problem.
>>>
>>> Nick
>>>
>>>
>>>
>>> -- Forwarded message --
>>> From: Bacula <[EMAIL PROTECTED]>
>>> Date: Nov 15, 2007 5:05 PM
>>> Subject: Bacula: Backup Fatal Error of lcn-fd Full
>>> To: [EMAIL PROTECTED]
>>>
>>>
>>> 14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
>>> 14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
>>> in catalog. Doing FULL backup.
>>> 14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
>>> Job=Job1.2007-11-14_09.29.05
>>> 14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
>>> 14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
>>> 14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
>>> 0" command.
>>> 14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
>>> result is Slot 1.
>>> 14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
>>> "Ultrium" (/dev/tape), all previous data lost.
>>> 14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
>>> device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
>>> 14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
>>> 14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
>>> Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
>>> 14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
>>> 14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
>>> 1, drive 0" command.
>>> 14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
>>> drive 0" command.
>>> 14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
>>> 0", status is OK.
>>> 14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
>>> 0" command.
>>> 14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
>>> result is Slot 4.
>>> 14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
>>> "Ultrium" (/dev/tape), all previous data lost.
>>> 14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
>>> "Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
>>> 15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808

Re: [Bacula-users] backup issue with batch table

2007-11-19 Thread Nick Jones
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 not work for this.

Are there any serious implications in migrating the tables from v 4.x
to 5 by recompiling?  I only found this in the docs:
"If you upgrade MySQL, you must reconfigure, rebuild, and re-install
Bacula otherwise you are likely to get bizarre failures. If you
install from rpms and you upgrade MySQL, you must also rebuild Bacula.
You can do so by rebuilding from the source rpm. To do so, you may
need to modify the bacula.spec file to account for the new MySQL
version."

It doesn't mention the catalog needing recreation so hopefully this
will be smooth and easy.  Does anyone recommend against this for any
reason?

Thanks alot

Nick




On Nov 15, 2007 5:49 PM, 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 -0600, Nick Jones wrote:
> > 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
> > backups of the same identical job except on a different / identical
> > tapeset that is now offsite.
> >
> > I am trying to create a new backup on the secondary set of tapes and I
> > keep running into this error after a day and a half.  Table 'batch' is
> > full.  I'm using a large my.cnf config
> >
> > Another error is:   Attribute create error. sql_find.c:333 Request for
> > Volume item 1 greater than max 0 or less than 1 I may have read
> > somewhere that this is caused by a disk space issue so I suspect I'm
> > running out of space.
> >
> > The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
> > space.  I have 16GB free on the root partition where mysql lives,
> > however the bacula sql tables and working directory are symbolically
> > linked to a RAID with 80GB of free space.  I had hoped this would be
> > enough.  Is it not?
> >
> > Thanks for any hints on identifying the problem.
> >
> > Nick
> >
> >
> >
> > -- Forwarded message --
> > From: Bacula <[EMAIL PROTECTED]>
> > Date: Nov 15, 2007 5:05 PM
> > Subject: Bacula: Backup Fatal Error of lcn-fd Full
> > To: [EMAIL PROTECTED]
> >
> >
> > 14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
> > 14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
> > in catalog. Doing FULL backup.
> > 14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
> > Job=Job1.2007-11-14_09.29.05
> > 14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
> > 14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
> > 14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > 0" command.
> > 14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > result is Slot 1.
> > 14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
> > "Ultrium" (/dev/tape), all previous data lost.
> > 14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
> > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > 14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
> > 14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
> > Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
> > 14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
> > 14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> > 1, drive 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
> > drive 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
> > 0", status is OK.
> > 14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > result is Slot 4.
> > 14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
> > "Ultrium" (/dev/tape), all previous data lost.
> > 14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
> > "Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
> > 15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808:12641 on
> > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > 15-Nov 15:53 lcn-sd JobId 375: Re-read of last block succeeded.
> > 15-Nov 15:53 lcn-sd JobId 375: End of medium on Volume "tape4"
> > Bytes=808,763,784,192 Blocks=12,536,640 at 15-Nov-2007 15:53.
> > 15-Nov 15:53 lcn-dir JobId 375: Recycled volume "tape3"
> > 15-Nov 15:53 lcn-sd JobId 375: 3307 Issuing autochanger "unload sl

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Michael Lewinger
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 -0600, Nick Jones wrote:
> > 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
> > backups of the same identical job except on a different / identical
> > tapeset that is now offsite.
> >
> > I am trying to create a new backup on the secondary set of tapes and I
> > keep running into this error after a day and a half.  Table 'batch' is
> > full.  I'm using a large my.cnf config
> >
> > Another error is:   Attribute create error. sql_find.c:333 Request for
> > Volume item 1 greater than max 0 or less than 1 I may have read
> > somewhere that this is caused by a disk space issue so I suspect I'm
> > running out of space.
> >
> > The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
> > space.  I have 16GB free on the root partition where mysql lives,
> > however the bacula sql tables and working directory are symbolically
> > linked to a RAID with 80GB of free space.  I had hoped this would be
> > enough.  Is it not?
> >
> > Thanks for any hints on identifying the problem.
> >
> > Nick
> >
> >
> >
> > -- Forwarded message --
> > From: Bacula <[EMAIL PROTECTED]>
> > Date: Nov 15, 2007 5:05 PM
> > Subject: Bacula: Backup Fatal Error of lcn-fd Full
> > To: [EMAIL PROTECTED]
> >
> >
> > 14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
> > 14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
> > in catalog. Doing FULL backup.
> > 14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
> > Job=Job1.2007-11-14_09.29.05
> > 14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
> > 14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
> > 14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > 0" command.
> > 14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > result is Slot 1.
> > 14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
> > "Ultrium" (/dev/tape), all previous data lost.
> > 14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
> > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > 14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
> > 14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
> > Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
> > 14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
> > 14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> > 1, drive 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
> > drive 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
> > 0", status is OK.
> > 14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > 0" command.
> > 14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > result is Slot 4.
> > 14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
> > "Ultrium" (/dev/tape), all previous data lost.
> > 14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
> > "Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
> > 15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808:12641 on
> > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > 15-Nov 15:53 lcn-sd JobId 375: Re-read of last block succeeded.
> > 15-Nov 15:53 lcn-sd JobId 375: End of medium on Volume "tape4"
> > Bytes=808,763,784,192 Blocks=12,536,640 at 15-Nov-2007 15:53.
> > 15-Nov 15:53 lcn-dir JobId 375: Recycled volume "tape3"
> > 15-Nov 15:53 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> > 4, drive 0" command.
> > 15-Nov 15:54 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 3,
> > drive 0" command.
> > 15-Nov 15:54 lcn-sd JobId 375: 3305 Autochanger "load slot 3, drive
> > 0", status is OK.
> > 15-Nov 15:54 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > 0" command.
> > 15-Nov 15:54 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > result is Slot 3.
> > 15-Nov 15:54 lcn-sd JobId 375: Recycled volume "tape3" on device
> > "Ultrium" (/dev/tape), all previous data lost.
> > 15-Nov 15:54 lcn-sd JobId 375: New volume "tape3" mounted on device
> > "Ultrium" (/dev/tape) at 15-Nov-2007 15:54.
> > 15-Nov 17:04 lcn-dir JobId 375: Fatal error: sql_create.c:732
> > sql_create.c:732 insert INSERT INTO batch VALUES
> > (20976597,375,'/mnt/right/ppg/dropbox/for_jessica.dir/lesion_vol.dir/2117/','2117_lesionnot_fruit_004.flt.gz','gg
> > Bgn/f IGw B Ru U A FO BAA I B

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Michael Lewinger
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
(2567 – 1 bytes).

If you need a MyISAM table that is larger than the default limit and
your operating system supports large files, the CREATE TABLE statement
supports AVG_ROW_LENGTH and MAX_ROWS options. See Section 12.1.5,
"CREATE TABLE Syntax". The server uses these options to determine how
large a table to allow.

Michael

On Nov 16, 2007 8:38 AM, Michael Lewinger <[EMAIL PROTECTED]> wrote:
> 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 -0600, Nick Jones wrote:
> > > 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
> > > backups of the same identical job except on a different / identical
> > > tapeset that is now offsite.
> > >
> > > I am trying to create a new backup on the secondary set of tapes and I
> > > keep running into this error after a day and a half.  Table 'batch' is
> > > full.  I'm using a large my.cnf config
> > >
> > > Another error is:   Attribute create error. sql_find.c:333 Request for
> > > Volume item 1 greater than max 0 or less than 1 I may have read
> > > somewhere that this is caused by a disk space issue so I suspect I'm
> > > running out of space.
> > >
> > > The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
> > > space.  I have 16GB free on the root partition where mysql lives,
> > > however the bacula sql tables and working directory are symbolically
> > > linked to a RAID with 80GB of free space.  I had hoped this would be
> > > enough.  Is it not?
> > >
> > > Thanks for any hints on identifying the problem.
> > >
> > > Nick
> > >
> > >
> > >
> > > -- Forwarded message --
> > > From: Bacula <[EMAIL PROTECTED]>
> > > Date: Nov 15, 2007 5:05 PM
> > > Subject: Bacula: Backup Fatal Error of lcn-fd Full
> > > To: [EMAIL PROTECTED]
> > >
> > >
> > > 14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
> > > 14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
> > > in catalog. Doing FULL backup.
> > > 14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
> > > Job=Job1.2007-11-14_09.29.05
> > > 14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
> > > 14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
> > > 14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > > 0" command.
> > > 14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > > result is Slot 1.
> > > 14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
> > > "Ultrium" (/dev/tape), all previous data lost.
> > > 14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
> > > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > > 14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
> > > 14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
> > > Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
> > > 14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
> > > 14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> > > 1, drive 0" command.
> > > 14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
> > > drive 0" command.
> > > 14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
> > > 0", status is OK.
> > > 14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> > > 0" command.
> > > 14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> > > result is Slot 4.
> > > 14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
> > > "Ultrium" (/dev/tape), all previous data lost.
> > > 14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
> > > "Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
> > > 15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808:12641 on
> > > device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> > > 15-Nov 15:53 lcn-sd JobId 375: Re-read of last block succeeded.
> > > 15-Nov 15:53 lcn-sd JobId 375: End of medium on Volume "tape4"
> > > Bytes=808,763,784,192 Blocks=12,536,640 at 15-Nov-2007 15:53.
> > > 15-Nov 15:53 lcn-dir JobId 375: Recycled volume "tape3"
> > > 15-Nov 15:53 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> > > 4, drive 0" command.
> > > 15

[Bacula-users] backup issue with batch table

2007-11-15 Thread Nick Jones
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
backups of the same identical job except on a different / identical
tapeset that is now offsite.

I am trying to create a new backup on the secondary set of tapes and I
keep running into this error after a day and a half.  Table 'batch' is
full.  I'm using a large my.cnf config

Another error is:   Attribute create error. sql_find.c:333 Request for
Volume item 1 greater than max 0 or less than 1 I may have read
somewhere that this is caused by a disk space issue so I suspect I'm
running out of space.

The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
space.  I have 16GB free on the root partition where mysql lives,
however the bacula sql tables and working directory are symbolically
linked to a RAID with 80GB of free space.  I had hoped this would be
enough.  Is it not?

Thanks for any hints on identifying the problem.

Nick



-- Forwarded message --
From: Bacula <[EMAIL PROTECTED]>
Date: Nov 15, 2007 5:05 PM
Subject: Bacula: Backup Fatal Error of lcn-fd Full
To: [EMAIL PROTECTED]


14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
in catalog. Doing FULL backup.
14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
Job=Job1.2007-11-14_09.29.05
14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
0" command.
14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
result is Slot 1.
14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
"Ultrium" (/dev/tape), all previous data lost.
14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
1, drive 0" command.
14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
drive 0" command.
14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
0", status is OK.
14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
0" command.
14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
result is Slot 4.
14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
"Ultrium" (/dev/tape), all previous data lost.
14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
"Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808:12641 on
device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
15-Nov 15:53 lcn-sd JobId 375: Re-read of last block succeeded.
15-Nov 15:53 lcn-sd JobId 375: End of medium on Volume "tape4"
Bytes=808,763,784,192 Blocks=12,536,640 at 15-Nov-2007 15:53.
15-Nov 15:53 lcn-dir JobId 375: Recycled volume "tape3"
15-Nov 15:53 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
4, drive 0" command.
15-Nov 15:54 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 3,
drive 0" command.
15-Nov 15:54 lcn-sd JobId 375: 3305 Autochanger "load slot 3, drive
0", status is OK.
15-Nov 15:54 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
0" command.
15-Nov 15:54 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
result is Slot 3.
15-Nov 15:54 lcn-sd JobId 375: Recycled volume "tape3" on device
"Ultrium" (/dev/tape), all previous data lost.
15-Nov 15:54 lcn-sd JobId 375: New volume "tape3" mounted on device
"Ultrium" (/dev/tape) at 15-Nov-2007 15:54.
15-Nov 17:04 lcn-dir JobId 375: Fatal error: sql_create.c:732
sql_create.c:732 insert INSERT INTO batch VALUES
(20976597,375,'/mnt/right/ppg/dropbox/for_jessica.dir/lesion_vol.dir/2117/','2117_lesionnot_fruit_004.flt.gz','gg
Bgn/f IGw B Ru U A FO BAA I BHOj5q BE7Ot4 BG2Gxr A A
C','xWoEMzfHWuvIxoZu2vxP0A') failed:
The table 'batch' is full
15-Nov 17:04 lcn-dir JobId 375: sql_create.c:732 INSERT INTO batch
VALUES 
(20976597,375,'/mnt/right/ppg/dropbox/for_jessica.dir/lesion_vol.dir/2117/','2117_lesionnot_fruit_004.flt.gz','gg
Bgn/f IGw B Ru U A FO BAA I BHOj5q BE7Ot4 BG2Gxr A A
C','xWoEMzfHWuvIxoZu2vxP0A')
15-Nov 17:04 lcn-dir JobId 375: Fatal error: catreq.c:478 Attribute
create error. sql_find.c:333 Request for Volume item 1 greater than
max 0 or less than 1
15-Nov 17:04 lcn-sd JobId 375: Job Job1.2007-11-14_09.29.05 marked to
be canceled.
15-Nov 17:04 lcn-sd JobId 375: Job write elapsed time = 31:31:59,
Transfer rate = 14.30 M bytes/se

Re: [Bacula-users] backup issue with batch table

2007-11-15 Thread Jason Martin
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?
> 
> 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
> backups of the same identical job except on a different / identical
> tapeset that is now offsite.
> 
> I am trying to create a new backup on the secondary set of tapes and I
> keep running into this error after a day and a half.  Table 'batch' is
> full.  I'm using a large my.cnf config
> 
> Another error is:   Attribute create error. sql_find.c:333 Request for
> Volume item 1 greater than max 0 or less than 1 I may have read
> somewhere that this is caused by a disk space issue so I suspect I'm
> running out of space.
> 
> The fileset is roughly 27,000,000 (million) files consuming 2.5 TB of
> space.  I have 16GB free on the root partition where mysql lives,
> however the bacula sql tables and working directory are symbolically
> linked to a RAID with 80GB of free space.  I had hoped this would be
> enough.  Is it not?
> 
> Thanks for any hints on identifying the problem.
> 
> Nick
> 
> 
> 
> -- Forwarded message --
> From: Bacula <[EMAIL PROTECTED]>
> Date: Nov 15, 2007 5:05 PM
> Subject: Bacula: Backup Fatal Error of lcn-fd Full
> To: [EMAIL PROTECTED]
> 
> 
> 14-Nov 09:29 lcn-dir JobId 375: No prior Full backup Job record found.
> 14-Nov 09:29 lcn-dir JobId 375: No prior or suitable Full backup found
> in catalog. Doing FULL backup.
> 14-Nov 09:29 lcn-dir JobId 375: Start Backup JobId 375,
> Job=Job1.2007-11-14_09.29.05
> 14-Nov 09:29 lcn-dir JobId 375: Recycled current volume "tape1"
> 14-Nov 09:29 lcn-dir JobId 375: Using Device "Ultrium"
> 14-Nov 09:29 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> 0" command.
> 14-Nov 09:29 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> result is Slot 1.
> 14-Nov 09:29 lcn-sd JobId 375: Recycled volume "tape1" on device
> "Ultrium" (/dev/tape), all previous data lost.
> 14-Nov 23:46 lcn-sd JobId 375: End of Volume "tape1" at 742:11802 on
> device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> 14-Nov 23:46 lcn-sd JobId 375: Re-read of last block succeeded.
> 14-Nov 23:46 lcn-sd JobId 375: End of medium on Volume "tape1"
> Bytes=742,713,882,624 Blocks=11,512,801 at 14-Nov-2007 23:46.
> 14-Nov 23:46 lcn-dir JobId 375: Recycled volume "tape4"
> 14-Nov 23:46 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> 1, drive 0" command.
> 14-Nov 23:47 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 4,
> drive 0" command.
> 14-Nov 23:47 lcn-sd JobId 375: 3305 Autochanger "load slot 4, drive
> 0", status is OK.
> 14-Nov 23:47 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> 0" command.
> 14-Nov 23:47 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> result is Slot 4.
> 14-Nov 23:47 lcn-sd JobId 375: Recycled volume "tape4" on device
> "Ultrium" (/dev/tape), all previous data lost.
> 14-Nov 23:47 lcn-sd JobId 375: New volume "tape4" mounted on device
> "Ultrium" (/dev/tape) at 14-Nov-2007 23:47.
> 15-Nov 15:53 lcn-sd JobId 375: End of Volume "tape4" at 808:12641 on
> device "Ultrium" (/dev/tape). Write of 64512 bytes got -1.
> 15-Nov 15:53 lcn-sd JobId 375: Re-read of last block succeeded.
> 15-Nov 15:53 lcn-sd JobId 375: End of medium on Volume "tape4"
> Bytes=808,763,784,192 Blocks=12,536,640 at 15-Nov-2007 15:53.
> 15-Nov 15:53 lcn-dir JobId 375: Recycled volume "tape3"
> 15-Nov 15:53 lcn-sd JobId 375: 3307 Issuing autochanger "unload slot
> 4, drive 0" command.
> 15-Nov 15:54 lcn-sd JobId 375: 3304 Issuing autochanger "load slot 3,
> drive 0" command.
> 15-Nov 15:54 lcn-sd JobId 375: 3305 Autochanger "load slot 3, drive
> 0", status is OK.
> 15-Nov 15:54 lcn-sd JobId 375: 3301 Issuing autochanger "loaded? drive
> 0" command.
> 15-Nov 15:54 lcn-sd JobId 375: 3302 Autochanger "loaded? drive 0",
> result is Slot 3.
> 15-Nov 15:54 lcn-sd JobId 375: Recycled volume "tape3" on device
> "Ultrium" (/dev/tape), all previous data lost.
> 15-Nov 15:54 lcn-sd JobId 375: New volume "tape3" mounted on device
> "Ultrium" (/dev/tape) at 15-Nov-2007 15:54.
> 15-Nov 17:04 lcn-dir JobId 375: Fatal error: sql_create.c:732
> sql_create.c:732 insert INSERT INTO batch VALUES
> (20976597,375,'/mnt/right/ppg/dropbox/for_jessica.dir/lesion_vol.dir/2117/','2117_lesionnot_fruit_004.flt.gz','gg
> Bgn/f IGw B Ru U A FO BAA I BHOj5q BE7Ot4 BG2Gxr A A
> C','xWoEMzfHWuvIxoZu2vxP0A') failed:
> The table 'batch' is full
> 15-Nov 17:04 lcn-dir JobId 375: sql_create.c:732 INSERT INTO batch
> VALUES 
> (20976597,375,'/mnt/right/ppg/dropbox/for_jessica.dir/lesion_vol.dir/2117/','2117_lesionnot_fruit_004.flt.gz','gg
> Bgn/f IGw B Ru