Hello James,
>From what you say, my retention period is only going to be as long as
the shortest Volume Retention I've specified in my pools. That is an
astonishing bug I would have though, but doesn't seem to be exactly
the case for me.
Since I have disk volume pools with volume retention of onl
Hello Dermot,
In the testing I've done I found that if I had one pool set to something
ridiculous like 1 day then when the backup was written to that pool that
retention period was applied to all copies of that particular job. As an
example if I had a 3 pools with full backups being kept in a p
Hi James,
Thanks for replying.
If I understand you correctly, then I think that is what I'm doing.
I have a very high File and Job retention on the clients resource (10
years), and a volume retention on the pools that I actually do want to
use, e.g. 13 days, 60 days, 1 year, 10 years depending on t
Hi,
I use Bacula 5.0.3 on ubuntu 9.04
I backup from a number of clients (windows and linux) to a disk raid
and then migrate to tape afterwards.
I am concerned that my retention is not working properly.
This is my client config for one client:
# Client (File Services) to backup
Client {
Name =
