Hello List,
does anyone knows which db operations block the "status dir" command?
I am using bacula 2.4.3 -1 whith MySQL-server-community-5.1.28-0 su RHEL 5
x86_64.
I knew tha now "status dir" does not trigger any more a general pruning of
volumes, as it did before, but it happens anyway that the
Hello,
I am using "status dir" and others
to build a daily bacula status mail,
"status dir" lists scheduled jobs based on days (default=1)
but lists only last 10 terminated jobs.
It would be nice if days option is also used for
last terminated jobs.
afaik there is no console command to list
ter
In the message dated: Tue, 28 Aug 2007 09:49:35 +0200,
The pithy ruminations from Arno Lehmann on
were:
=> Hi,
=>
=> 28.08.2007 02:35,, Charles Sprickman wrote::
=> > Hi all,
=> >
=> > I'm starting to work on a script to alert me to what tapes will be needed
=> > for upcoming runs. Accordin
> > It is of course finding the right volumes when it's time for the job
to
> > run, but I'm a bit confused as to why it can't supply the info ahead
of
> > time. What configuration parameters might I have screwed up to
break
> > this?
>
> I don't thinky you screwed up anything... the problem is t
> Having the pool which will be used displayed would, in
> many cases, be more informative.
>
I was just thinking that...
John
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems
On 8/27/07, Charles Sprickman <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm starting to work on a script to alert me to what tapes will be needed
> for upcoming runs. According to the manual (I think), this info should be
> shown in the "status dir" output.
>
> Mine looks like this, and has for as
Hi,
28.08.2007 02:35,, Charles Sprickman wrote::
> Hi all,
>
> I'm starting to work on a script to alert me to what tapes will be needed
> for upcoming runs. According to the manual (I think), this info should be
> shown in the "status dir" output.
>
> Mine looks like this, and has for as lon
Hi all,
I'm starting to work on a script to alert me to what tapes will be needed
for upcoming runs. According to the manual (I think), this info should be
shown in the "status dir" output.
Mine looks like this, and has for as long as I can remember:
*status dir
Automatically selected Catalog
On Wednesday 14 February 2007 13:22, Gavin Conway wrote:
> Kern Sibbald wrote:
> > The problem is that your Catalog database is not well tuned (missing
> > indexes), or you have a very large database. The performance problem
> > comes from Bacula attempting to find the next volume that will be use
Kern Sibbald wrote:
> The problem is that your Catalog database is not well tuned (missing
> indexes),
> or you have a very large database. The performance problem comes from Bacula
> attempting to find the next volume that will be used for each scheduled job,
> and to do so, it must generally
On Wednesday 14 February 2007 13:22, Gavin Conway wrote:
> Kern Sibbald wrote:
> > The problem is that your Catalog database is not well tuned (missing
> > indexes), or you have a very large database. The performance problem
> > comes from Bacula attempting to find the next volume that will be use
On Sunday 11 February 2007 10:28, Mikael Kermorgant wrote:
> Hello,
>
> I'm currently using bacula 1.38.11 and sometimes, when I run "status
> dir" on the console, it generates a high load on the server ( >3, more
> than 15minutes) and blocks the console from user input. Basically, it
> spends all
I wonder would some kind of high debug level or trace would maybe tell you what
it's doing. Take a look in the manual and see what you think.
-Original Message-
From: Mikael Kermorgant <[EMAIL PROTECTED]>
Subj: [Bacula-users] 'status dir' puts high load on ser
Hello,
I'm currently using bacula 1.38.11 and sometimes, when I run "status
dir" on the console, it generates a high load on the server ( >3, more
than 15minutes) and blocks the console from user input. Basically, it
spends all this time to dress the list of scheduled jobs.
My server is maybe a b
mmh it looks the same for me ... I don't have any more these messages
today, strange !
steen meyer wrote:
> Hello,
>
> I also always have this, and I find it funny that is always gives this
> message
> only about the first volume created, what about all the other volumes - as
> the rotation ha
Hello,
I also always have this, and I find it funny that is always gives this message
only about the first volume created, what about all the other volumes - as
the rotation have carried one for some rounds, what's then the relevance of
always pruning the oldes volume?
Onsdag 28 juni 2006 15:4
Hi,
On 6/30/2006 8:54 AM, Julien Cigar wrote:
> Arno Lehmann wrote:
>
>>Hello,
>>
>>On 6/28/2006 3:47 PM, Julien Cigar wrote:
>>
>>
>>>Hi !
>>>
>>>I'm using 1.38.9 (Debian) with PostgreSQL (8.1.4)
>>>
>>>Am I the only one to have this kind of message : 28-Jun 12:39
>>>phoenix-dir: Pruning olde
Arno Lehmann wrote:
> Hello,
>
> On 6/28/2006 3:47 PM, Julien Cigar wrote:
>
>> Hi !
>>
>> I'm using 1.38.9 (Debian) with PostgreSQL (8.1.4)
>>
>> Am I the only one to have this kind of message : 28-Jun 12:39
>> phoenix-dir: Pruning oldest volume "Canis-Incr-Disk-0001" when I do a
>> *status d
Hello,
On 6/28/2006 3:47 PM, Julien Cigar wrote:
> Hi !
>
> I'm using 1.38.9 (Debian) with PostgreSQL (8.1.4)
>
> Am I the only one to have this kind of message : 28-Jun 12:39
> phoenix-dir: Pruning oldest volume "Canis-Incr-Disk-0001" when I do a
> *status dir ? (nothing is pruned of course)
On 28.06.2006, at 15:55, Julien Cigar wrote:
> Yep it's turned on, but I have this messages every time I do a
> *status dir, and nothing is pruned
Have you checked your retention periods? Maybe this volume is just
not "old enough".
Using Tomcat but need to do more? Need to support web servi
Yep it's turned on, but I have this messages every time I do a *status
dir, and nothing is pruned
Sebastian Stark wrote:
>
> If you have automatic pruning turned on this is expected behaviour I
> would say.
>
>
> Sebastian
>
> On 28.06.2006, at 15:47, Julien Cigar wrote:
>
>> Hi !
>>
>> I'm usin
If you have automatic pruning turned on this is expected behaviour I
would say.
Sebastian
On 28.06.2006, at 15:47, Julien Cigar wrote:
> Hi !
>
> I'm using 1.38.9 (Debian) with PostgreSQL (8.1.4)
>
> Am I the only one to have this kind of message : 28-Jun 12:39
> phoenix-dir: Pruning oldest
Hi !
I'm using 1.38.9 (Debian) with PostgreSQL (8.1.4)
Am I the only one to have this kind of message : 28-Jun 12:39
phoenix-dir: Pruning oldest volume "Canis-Incr-Disk-0001" when I do a
*status dir ? (nothing is pruned of course)
(Complete output is available on
http://rafb.net/paste/results
23 matches
Mail list logo
