Jose Perez wrote:
> Now I'd like to be able to store (and so be able to restore from)
> backups of last 90 days; Older backups must be simply erased, so to
> achieve this ... would I need something like these?
>
> Client {
> ...
> ...
> File Retention = 90 days
> Job Retention = 90 days
> }
Hi:
> If you did not set any condition to limit the disk volume size or
> usage the volume will grow till it exhausts your storage then the
> volume retention period of 15 days kicks in.
>
That's exactly what is going to happen soon If I don't solve this now.
> See the first part of the followin
>
> Bacula's retention times for volumes are based on the date the volume was
> last written. So, every time Bacula writes a backup job to a volume, your
> 15-day retention clock starts over from zero. As long as your volume's
> status is Append, bacula will keep writing to it.
>
That's the kind
Jose Perez wrote:
Hi people:
I'm a little confused about how bacula deals with Pools and Volumes.
I'm using Automatic labeling with a Pool that uses a unique Volume (as
file disk) that is continuosly increasing its size. I have a unique
volume named Vol-0001 with a size of 900 GB and status
On Thu, Oct 15, 2009 at 8:02 PM, Jose Perez wrote:
> Hi people:
>
> I'm a little confused about how bacula deals with Pools and Volumes.
> I'm using Automatic labeling with a Pool that uses a unique Volume (as
> file disk) that is continuosly increasing its size. I have a unique
> volume named Vol
Hi people:
I'm a little confused about how bacula deals with Pools and Volumes.
I'm using Automatic labeling with a Pool that uses a unique Volume (as
file disk) that is continuosly increasing its size. I have a unique
volume named Vol-0001 with a size of 900 GB and status Append.
If I pretend to
