--- Rich <[EMAIL PROTECTED]> wrote:
> On 2007.10.05. 17:30, Foo Bar wrote:
> ...
> >
> > 'Remove Volume After' is of no use since I want to keep the volume,
> just
> > control its contents.
>
> actually, if you would limit each volume to a single job, it would
> nicely achieve the goal, i thin
On 2007.10.05. 17:30, Foo Bar wrote:
...
>>> What I would like to do is to keep for example 2 full backups, and as
>>> soon as the third is made the oldest one should be deleted from disk
>>> (not just the job/volume entries in the catalog).
>> it seems that you might be interested in feature reque
--- Rich <[EMAIL PROTECTED]> wrote:
> i don't know how feasible would this be with current bacula formats -
> such a storage system would be a huge benefit for hdd based systems, but
> might require serious changes.
Indeed, I'm backing up to disk for the time being, not tape.
> > What I would
On 2007.10.05. 13:20, Foo Bar wrote:
> If I want to use a single volume per client, how do I delete old backups
> from it in a FIFO manner without using dates or size? Can Bacula seek back
> and resize a volume at all or does it need to recycle it?
i don't know how feasible would this be with curr
If I want to use a single volume per client, how do I delete old backups
from it in a FIFO manner without using dates or size? Can Bacula seek back
and resize a volume at all or does it need to recycle it?
What I would like to do is to keep for example 2 full backups, and as soon
as the third is m
