[Bacula-users] Job is waiting on Storage

[Bill A. <waa...@re...>]

On 08/31/10 08:44, Marco Lertora wrote:
>   Hi!
> 
> I've the same problem! anyone found a solution?
> 
> I have 3 concurrent jobs, which backup from different fd to the same 
> device on sd.
> All jobs use the same pool and the pool use "Maximum Volume Bytes" as 
> volume splitting policy, as suggested in docs.
> All job has the same priority.
> 
> Everything starts good, but after some volumes changes (becouse they 
> reach the max volume size) the storage lost the pool information of the 
> mounted volume
> So, the jobs started after that, wait on sd for a mounted volume with 
> the same pool as the one wanted by the job.
> 
> Regards
> Marco Lertora


Sorry for a "me too" post... But:


I have been noticing the same thing here.  I just have not been able to
monitor it and accurately document it.

Basically it appears to be exactly what you have stated above. I am also using
only disk storage with my "file tapes" configured to be a maximum of 10GB each.

I have seen a "status dir"  show me  "job xxx waiting on storage" and have
noted that the job(s) waiting are of the same priority as the job(s) currently
running and are configured to use the same device and pool.

I have also noticed exactly what Lukas Kolbe described here where the job
wants one pool, but thinks it has a "null named pool":

> 3608 JobId=308 wants Pool="dp" but have Pool=""

and here where the device is mounted, the volume name is known but the pool is
unknown:

>Device "dp1" (/var/bacula/diskpool/fs1) is mounted with:
>      Volume:      Vol0349
>      Pool:        *unknown*
>      Media type:  File
>      Total Bytes=11,726,668,867 Blocks=181,775 Bytes/block=64,512
>      Positioned at File=2 Block=3,136,734,274



So by all indications the job(s) that are "waiting on storage" should be
running but are instead needlessly waiting.


Initially, my thought was that I had the Pool in the jobs defined like:

Pool = Default

and the Default pool had no tapes in it - Bacula requires a Pool to be defined
in a Job definition - Which is why I used "Default", but I was overriding the
Pool in the Schedule like so:

Schedule {
  Name = WeeklyToOffsiteDisk
        Run = Full              pool=Offsite-eSATA      sun     at 20:30
        Run = Incremental       pool=Offsite-eSATA-Inc  mon-fri at 20:30
        Run = Differential      pool=Offsite-eSATA-Diff sat     at 20:30
}


I have recently reconfigured my system to use one pool "Offsite-eSATA" and
have set:

Pool = Offsite-eSATA

directly in all of the the Job definitions instead of using the Schedule
override, but I am still seeing what you both have described.


--
Bill Arlofski
Reverse Polarity, LLC