On Thu, 2005-11-10 at 00:05 +0200, Kern Sibbald wrote:
> No. You asked it (via the status command) to tell you what the next volume
> will be, so it is doing its best to figure it out by applying the algorithm
> it uses when the SD requests a volume.
What then is the action of 'pruning' a volum
On Wednesday 09 November 2005 22:49, Jesse Keating wrote:
> On Wed, 2005-11-09 at 21:44 +, Martin Simmons wrote:
> > Doing 'status dir' can trigger pruning because it tries to find the
> > volumes that will be used by the jobs in the next 24 hours. It looks
> > like certain combinations of poo
On Wed, 2005-11-09 at 21:44 +, Martin Simmons wrote:
> Doing 'status dir' can trigger pruning because it tries to find the volumes
> that will be used by the jobs in the next 24 hours. It looks like certain
> combinations of pool options will cause the "Pruning oldest volume" message
> each ti
> On Wed, 09 Nov 2005 13:19:43 -0800, Jesse Keating <[EMAIL PROTECTED]>
> said:
Jesse> On Tue, 2005-11-08 at 14:05 -0800, Jesse Keating wrote:
>>
>> Some times it is just once, sometimes I get multiples in the same email.
>> Every time today it has been the same job. This volume
On Tue, 2005-11-08 at 14:05 -0800, Jesse Keating wrote:
>
> Some times it is just once, sometimes I get multiples in the same email.
> Every time today it has been the same job. This volume was created
> TODAY. Whats going on?
>
I have found what action triggers this message. Any time I do a
Seems that every time I have to stop and start the daemon (reboots or
whatnot) I get messages about pruning jobs from volumes:
08-Nov 14:01 dragul: Pruning oldest volume "Bacula-Volume-0001"
08-Nov 14:01 dragul: Pruning oldest volume "Bacula-Volume-0001"
Some times it is just once, sometimes I ge
