On 3/19/2011 11:29 AM, Dan Langille wrote:
> On 3/4/2011 7:32 AM, Dan Langille wrote:
>> This situation occurs often. Usually every morning. If I cancel the top
>> job (in this ca 54502), the other jobs will proceed.
>>
>>
>>
>> Running Jobs:
>> Console connected at 04-Mar-11 12:23
>> JobId Le
On 3/4/2011 7:32 AM, Dan Langille wrote:
> This situation occurs often. Usually every morning. If I cancel the top
> job (in this ca 54502), the other jobs will proceed.
>
>
>
> Running Jobs:
> Console connected at 04-Mar-11 12:23
>JobId Level Name Status
>
On Monday 07 March 2011 14:33:50 Dan Langille wrote:
> On 3/7/2011 6:49 AM, Silver Salonen wrote:
> > On Monday 07 March 2011 13:37:42 Dan Langille wrote:
> >> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> >>> On 3/4/11 4:32 AM, Dan Langille wrote:
> This situation occurs often. Usually every mor
On 3/7/2011 6:49 AM, Silver Salonen wrote:
> On Monday 07 March 2011 13:37:42 Dan Langille wrote:
>> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
>>> On 3/4/11 4:32 AM, Dan Langille wrote:
This situation occurs often. Usually every morning. If I cancel the top
job (in this ca 54502), the oth
On Monday 07 March 2011 13:37:42 Dan Langille wrote:
> On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> > On 3/4/11 4:32 AM, Dan Langille wrote:
> >> This situation occurs often. Usually every morning. If I cancel the top
> >> job (in this ca 54502), the other jobs will proceed.
> >>
> >>
> >>
> >> Runn
On 3/4/2011 10:31 PM, Mehma Sarja wrote:
> On 3/4/11 4:32 AM, Dan Langille wrote:
>> This situation occurs often. Usually every morning. If I cancel the top
>> job (in this ca 54502), the other jobs will proceed.
>>
>>
>>
>> Running Jobs:
>> Console connected at 04-Mar-11 12:23
>> JobId Level
On 3/4/11 4:32 AM, Dan Langille wrote:
> This situation occurs often. Usually every morning. If I cancel the top
> job (in this ca 54502), the other jobs will proceed.
>
>
>
> Running Jobs:
> Console connected at 04-Mar-11 12:23
>JobId Level Name Status
> ==
This situation occurs often. Usually every morning. If I cancel the top
job (in this ca 54502), the other jobs will proceed.
Running Jobs:
Console connected at 04-Mar-11 12:23
JobId Level Name Status
On Mon, December 13, 2010 9:18 pm, Dan Langille wrote:
> From time to time, I get a job stuck. But I'm not sure why. Several
> other jobs have already gone through this storage device since this item
> was queued. Confused...
>
> Running Jobs:
> Console connected at 14-Dec-10 02:03
> JobId L
From time to time, I get a job stuck. But I'm not sure why. Several
other jobs have already gone through this storage device since this item
was queued. Confused...
Running Jobs:
Console connected at 14-Dec-10 02:03
JobId Level Name Status
==
There was some discussion a while back of an error state in which no new
jobs could be started in Bacula, with all jobs showing "Waiting on max
storage jobs" even though the configuration was completely correct and
no concurrency limits had been exceeded. I ran into this problem myself
yesterday,
On Tue, Jan 13, 2009 at 6:54 PM, Mikel Jimenez Fernandez
wrote:
> Hello
>
> Why I see in my bconsole so much "waiting on max Storage jobs" ?
>
>
> Here my status dir :
>
> 6534 Differe redeyemadrid.irontec.vpn.2009-01-11_19.00.42 is running
> 6625 Increme pbximh.irontec.vpn.2009-01-13_20.30.18
Hello
Why I see in my bconsole so much "waiting on max Storage jobs" ?
Here my status dir :
6534 Differe redeyemadrid.irontec.vpn.2009-01-11_19.00.42 is running
6625 Increme pbximh.irontec.vpn.2009-01-13_20.30.18 is running
6628 Increme pbxalhondiga.irontec.vpn.2009-01-13_21.00.22 is wai
On Tue, Oct 14, 2008 at 12:10 AM, Sebastian Lehmann <[EMAIL PROTECTED]
> wrote:
> Hello,
>
> Look at the storage-section in the bacula-dir.conf. There you have also
> to define "Maximum Concurrent Jobs", e.g:
>
> Storage {
> Name = SL500-1
> Address = dss-bacula
> SD Port = 9103
> Password = "
On Tue, 14 Oct 2008, Sebastian Lehmann wrote:
> > In general it's better to increase concurrent jobs and make sure
> > there's adequate spool space than switch this option on.
>
> oh, sorry, i didn't know that fact. Why is this not the recommended
> setting?
Because it means a single pool can mon
On Tue, 14 Oct 2008, Sebastian Lehmann wrote:
> Bacula will only use one drive per pool, so if you want to write to more
> then one drive you have to define several pools and direct the jobs to
> this pools.
Not quite correct.
That is the default setting, but Bacula can use several drives on one
Hi Alan,
Am Di 14.10.2008 12:06 schrieb Alan Brown <[EMAIL PROTECTED]>:
> On Tue, 14 Oct 2008, Sebastian Lehmann wrote:
>
> > Bacula will only use one drive per pool, so if you want to write to
> > more
> > then one drive you have to define several pools and direct the jobs
> > to
> > this pools
Hello,
Am Di 14.10.2008 01:31 schrieb Dave Poirier <[EMAIL PROTECTED]>:
> Brand spankin new to Bacula... I like what I see so far.
> I googled and looked through the archives and couldn't find anything
> helpful. Anyway, I have a autochanger with 4 AIT-3 drives but it seems
> if I
> start multipl
Dave Poirier wrote:
> Brand spankin new to Bacula... I like what I see so far.
> I googled and looked through the archives and couldn't find anything
> helpful. Anyway, I have a autochanger with 4 AIT-3 drives but it seems
> if I start multiple jobs it will only run one job on the first drive and
Brand spankin new to Bacula... I like what I see so far.
I googled and looked through the archives and couldn't find anything
helpful. Anyway, I have a autochanger with 4 AIT-3 drives but it seems if I
start multiple jobs it will only run one job on the first drive and any job
after will sit with a
20 matches
Mail list logo
