On 12 Dec 2005 at 22:04, Harondel J. Sibble wrote:
A key point mentioned above, that can be a source of frustration, is that
Bacula will only recycle purged Volumes if there is no other appendable
Volume available, otherwise, it will always write to an appendable Volume
On 2 Dec 2005 at 20:09, Martin Simmons wrote:
I suggest you post the output of llist volumes.
Did all that, no response :-(
Anyhow, I still have to manually purge each tape, how do I get around this.
--
Harondel J. Sibble
Sibble Computer Consulting
Creating solutions for the small
On 1 Dec 2005 at 10:37, Kern Sibbald wrote:
Yes, a shorter Volume retention period will force pruning of job and file
data, but as the manual and a recent email point out, after changing the .conf
volume retention period, you must update the catalog data for volumes that
already exist.
On 2 Dec 2005 at 9:12, Harondel J. Sibble wrote:
On 1 Dec 2005 at 9:29, Sebastian Stark wrote:
You have to use the update command to first update the pool parameters
from the config file and the use update again to update the volume
parameters from the pool:
update - pool from
On 1 Dec 2005 at 9:29, Sebastian Stark wrote:
You have to use the update command to first update the pool parameters
from the config file and the use update again to update the volume
parameters from the pool:
update - pool from resource
update - volume parameters - select pool -
On Friday 02 December 2005 18:12, Harondel J. Sibble wrote:
On 1 Dec 2005 at 9:29, Sebastian Stark wrote:
You have to use the update command to first update the pool parameters
from the config file and the use update again to update the volume
parameters from the pool:
update - pool
On 2 Dec 2005 at 19:00, Sebastian Stark wrote:
You can see the result in list media
Nope, no difference. I had the run before update on the screen and compared
it to the run afterwards, no difference.
--
Harondel J. Sibble
Sibble Computer Consulting
Creating solutions for the small
On Thu, 01 Dec 2005 07:57:42 -0800, Harondel J. Sibble [EMAIL
PROTECTED] said:
Harondel On 1 Dec 2005 at 10:37, Kern Sibbald wrote:
Yes, a shorter Volume retention period will force pruning of job and file
data, but as the manual and a recent email point out, after changing the
.conf
On 2 Dec 2005 at 20:09, Martin Simmons wrote:
When was the volume last written? All the retention times are counted
from the last write time. If you wrote it on day 5, then on day 7 the
day 5 backup from was only 2 days old and still within the retention
period, hence the tape should not
--Da: Harondel J. Sibble [EMAIL PROTECTED]A: Sebastian Stark [EMAIL PROTECTED] Cc: bacula-users@lists.sourceforge.net Data: 1 dicembre 2005 7.02.59 CETOggetto: Re: [Bacula-users] problems with autopruning and volume reuse
On 30 Nov 2005 at 19:20
On Thu, Dec 01, 2005 at 09:04:40AM +0100, Gabriele Bulfon wrote:
Maybe I am wrong, but as I'm having the same problem for months, I deduce
there is something wrong on the Bacula pdf document: it states that bacula
will consider the shortest retention period during prune.
So, I guessed from
On Thursday 01 December 2005 09:39, Sebastian Stark wrote:
On Thu, Dec 01, 2005 at 09:04:40AM +0100, Gabriele Bulfon wrote:
Maybe I am wrong, but as I'm having the same problem for months, I deduce
there is something wrong on the Bacula pdf document: it states that
bacula will consider the
The other question I had regarding this issue is how to reconcile job
retention vs. volume retention. With an appendable volume, if jobs are
held for 30 days, they will expire at all different times. I'm not sure
how this can relate to media retention, which obviously can only be
around until
On 1 Dec 2005 at 10:37, Kern Sibbald wrote:
Yes, a shorter Volume retention period will force pruning of job and file
data, but as the manual and a recent email point out, after changing the .conf
volume retention period, you must update the catalog data for volumes that
already exist.
On Wed, Nov 30, 2005 at 10:01:15AM -0800, Harondel J. Sibble wrote:
I am pretty sure I am missing something fairly fundamental in the way volumes
are recycled, I've read through the docs, checking the list postings, but
have been unable to get a handle on this.
Basically, if I start with a
I am having the same problem. And I'm getting mad with the flags.I recently started to think I have old jobs that stored the old job retention period.How can I get rid of all that old jobs that are no more valid, without having to delete each by hand?Should I start again from a scratch database
On Wed, 30 Nov 2005 19:34:24 +0100 (CET), Gabriele Bulfon [EMAIL
PROTECTED] said:
Gabriele How can I get rid of all that old jobs that are no more valid,
Gabriele without having to delete each by hand?
I would so this by editing the output of list jobs to include the old jobs and
writing
On 30 Nov 2005 at 19:20, Sebastian Stark wrote:
From your bacula-dir.conf it looks like your job retention is 30 days.
As I understand bacula it won't (automatically) prune volumes unless it
has purged all jobs referring to this volume.
Ahh, so I should set the job retention period to
On 30 Nov 2005 at 19:20, Sebastian Stark wrote:
From your bacula-dir.conf it looks like your job retention is 30 days.
As I understand bacula it won't (automatically) prune volumes unless it
has purged all jobs referring to this volume.
So once I make that change in my conf file, do I have
19 matches
Mail list logo
