Hi,

11.05.2008 16:07, Phil Schwartz wrote:
> One of my full backups (which occurs weekly) has been stalling each time 
> it's run.

How long has it been stalled? And does the catalog work in the background?

What you describe could be related to the new feature of batch 
inserts, I think.

If that's the case, it simply takes some time for Bacula to insert all 
the collected attributes into the real catalog after they were stored 
in a temporary table.

You can check this by looking at what the catalog database does during 
this time - for MySQL, 'mysqladmin processlist' is a good start.

If, when using batch inserts, the temporary table becomes unusable you 
should get some error messages in the end. The temporary table can 
break if the database servers temp space is too small, and it can 
vanish if the database connection is closed after being idle for too 
long. The latter can be prevented by setting a longer timeout calue in 
the database configuration. (Note that this is all relevant for MySQL, 
PostgreSQL works a bit different.)

The next step for you should be to simply wait longer and check what 
the database does while the job is in state "Dir inserting Attributes".

Arno

> Status dir
> 
> 10468 Full    clutch-development.2008-05-11_01.05.18 Dir inserting 
> Attributes
> 
> 
> The relevant dir config settings are:
> JobDefs {
>    Name = "clutch-development"
>    Messages = Standard
>    FileSet = "Clutch Development"
>    Storage = File
>    Pool = clutch-dev
>    Client = clutch-fd
> }
> 
> Job {
>    Name = "clutch-development"
>    Type = Backup
>    JobDefs = "clutch-development"
>    Schedule = "WeeklyCycle"
>    Write Bootstrap = "/var/bacula/working/clutch.bsr"
> }
> 
> Pool {
>    Name = "clutch-dev"
>    Pool Type = Backup
>    Use Volume Once = yes
>    LabelFormat = "clutch-dev-"
>    AutoPrune = yes
>    VolumeRetention = 30d
>    Maximum Volumes = 40
>    Recycle = yes
> }
> 
> Schedule {
>    Name = "WeeklyCycle"
>    Run = Full sun at 1:05
>    Run = Differential mon-sat at 1:05
> }
> 
> FileSet {
>    Name = "Clutch Development"
>    Include  {
>      Options { compression=GZIP }
>      File = /home/clutch/devel
>    }
>    Exclude {
>    File = *.tgz *.gz *.pyc build/* dist/*
>    }
> }
> 
> 
> The nightly diffs work fine.  This configuration worked fine with 1.34. 
>   Since upgrading to the latest Bacula version the full job has not 
> completed once.  I'm not sure where to look or how to fix this.  The 
> previous attempts I've just killed the job and restart the director.
> 
> Thanks for any help,
> 
> Phil
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users