Re: [Bacula-users] Fatal Error doing Full Backup

Thank you Kevin,

Use priority is a good idea so I won't have to change the catalog schedule
every time the size grows in the server backup. I will apply priority 10 to
regular backups and priority 11 to backupcatalog.
I also have Max Concurrent Jobs = 1 in my Director configuration

Thanks again
ISABEL



-----Mensaje original-----
De: Kevin Keane [mailto:subscription AT kkeane DOT com]
Enviado el: viernes, 14 de noviembre de 2008 13:08
CC: bacula-users AT lists.sourceforge DOT net
Asunto: Re: [Bacula-users] Fatal Error doing Full Backup


Maybe you can use priorities to accomplish the same goal?

I have all my backup jobs scheduled for the exact same time. All my
regular backup jobs run with priority 10, the BackupCatalog runs with
priority 11. That way, it will wait until all the higher-priority jobs
have finished, and start right away afterwards.

Here is what I have in my JobDefs:

JobDefs {
     Name = "DefaultJobs"
     Type = Backup
     Level = Incremental
     Client = randamai-fd
     FileSet = "Full Set"
     Schedule = "WeeklyCycle"
     Messages = Standard
     Priority = 10
     Write Bootstrap = "/var/lib/bacula/working/%n.bsr"
     Pool = Default
     Full Backup Pool = Full-Pool
     Run Before Job = "/usr/local/sbin/nagiosscheduledowntime %c"
     Differential Backup Pool = Diff-Pool
     Incremental Backup Pool = Inc-Pool
}

And the Job BackupCatalog:

Job {
  Name = "BackupCatalog"
  JobDefs = "DefaultJob"
  Level = Full
  Client = randamai-fd
  FileSet="Catalog"
  Schedule = "WeeklyCycleAfterBackup"
  # This creates an ASCII copy of the catalog
  RunBeforeJob = "/usr/lib/bacula/make_catalog_backup bacula bacula"
  # This deletes the copy of the catalog
  RunAfterJob  = "/usr/lib/bacula/delete_catalog_backup"
  Write Bootstrap = "/var/lib/bacula/working/BackupCatalog.bsr"
  Priority = 11                   # run after main backup
}

I also have Max Concurrent Jobs = 1 in my Director configuration; not
sure if that is necessary to make this work properly.

Kevin Keane
The NetTech
http://www.4nettech.com

Isabel Bermejo wrote:
> Hi
> I think I've found the problem. This server only runs a Full backup on
> Mondays. While size grows, the time to perform the backup grows too. If I
> run a full backup server in the morning, the backup runs without errors.
> With this, I've realized that BackupCatalog runs 2 minutes before Backup
> server has finished so the error is "database is locked".
>
> I'm gonna change the time for backupcatalog and test if I'm right.
>
> Thanks
> ISABEL
>
> -----Mensaje original-----
> De: Arno Lehmann [mailto:al AT its-lehmann DOT de]
> Enviado el: jueves, 13 de noviembre de 2008 0:08
> Para: bacula-users AT lists.sourceforge DOT net
> Asunto: Re: [Bacula-users] Fatal Error doing Full Backup
>
>
> Hello,
>
> 11.11.2008 10:00, Isabel Bermejo wrote:
>
>> Hi,
>> I'm using Bacula to backup servers into files (not tapes). One of the
>> servers has to backup 30GB of information. It has been working fine for 2
>> years but 3 weeks ago I received a Fatal Error message.
>>
>> Here I post a little bit of the message (it's too large):
>> 10-Nov 22:40 iesa8-dir: BackupIESA4.2008-11-10_21.30.00 Fatal error:
>> sql_create.c:564 sql_create.c:564 insert INSERT INTO File
>> (FileIndex,JobId,PathId,FilenameId,LStat,MD5) VALUES
>> (42322,10216,14961,17509,'MK EgAR IH0 B IM IM A SXHu BAA CTY BJEhK1
BCNzD+
>> BFE418 A A E','0') failed:
>> database is locked
>>
>
> I think the error message is quite clear - the database is locked.
>
> ...
>
>> This message appears only when doing Full Backup. Does anyone know what
is
>> the problem?
>>
>
> That'S more interesting... Bacula itself should be well able to
> serialize database accesses. Also, if this only happens for this one
> job, that indicates a more serious problem.
>
> Have you checked that the database is usable and what else happens
> there while the job in question runs? You don't tell us which database
> you use - with MySQL, 'mysqladmin processlist' will give you something
> useful, perhaps.
>
>
>> I've read it could be the amount of data I'm backing up but
>> this has been working fine till 3 weeks ago. I'm using Bacula 1.38 and I
>> haven't modified nothing at all because it was working fine.
>>
>
> 1.38 is definitely no longer fully supported. I suggest you upgrade to
> the current released version and see if that behaves differently. If
> the error persists, you should report that, or submit a bug report
> directly at bugs.bacula.org.
>
> Arno
>


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users