>
> Thanks for the help provided so far, it's very much appreciated. I do have
> a few follow-up questions:
>
>
> In a case where the client's storage pool
Pools don't belong to a client unless you set up the directors schedules
that way and don't run any manually to the pool.
> would of
an
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: phatrik [mailto:bacula-forum < at > backupcentral.com]
> > Gesendet: Mittwoch, 24. Juni 2009 03:46
> > An: bacula-users < at > lists.sourceforge.net
> > Betreff: [Bacula-users] Job v
> -Ursprüngliche Nachricht-
> Von: phatrik [mailto:bacula-fo...@backupcentral.com]
> Gesendet: Mittwoch, 24. Juni 2009 03:46
> An: bacula-users@lists.sourceforge.net
> Betreff: [Bacula-users] Job vs volume retention periods
>
>
> Hi,
>
> I'm confuse
liche Nachricht-
Von: phatrik [mailto:bacula-fo...@backupcentral.com]
Gesendet: Mittwoch, 24. Juni 2009 03:46
An: bacula-users@lists.sourceforge.net
Betreff: [Bacula-users] Job vs volume retention periods
Hi,
I'm confused in regards to job retention vs volume retention. From the lit
Hi,
I'm confused in regards to job retention vs volume retention. From the little
bit I understand, if the volume retention period is passed and bacula is unable
to find any other appendable volumes in the client's stoarge pool, it will
delete all file and job records and then re-use that vol
