Hey Steve,
I had something similar happen to me here, bacula will respect your retention
policies, and your volume limit. So if you have 200 files and you have
configured a limit of 205, when the next job starts, it will recycle anything
it can, use any volume that is purged, then start creati
once you hit the maximum volume number in the pool, bacula will purge
/ recycle the oldest volume it can find in the pool, depending on your
pool configuration. Are you limiting the volume size or number of jobs
in any way?
All the best, Uwe
Yes I am limiting the volume size to 5Gb and only
I did the volume cleanup and had just around the number of volumes needed (or I
thought). Then it started to work the way I expected in that it recycled
volumes that jobs had expired (7 days). But then one day someone put a 32Gb of
data on so it couldn't recycle enough volumes so it auto creat
John,
Thanks for the reply. I went throught and manually purge a lot of the jobs.
What it seemed was happening was that it was auto creating a volume before it
would recycle. I am going to try to figure out just how many volumes are
needed and then delete the rest.
Thanks again for the repl
I am confused about how to get backup jobs to be automatically removed and for
disk files to be recycled and reused for backs. I created a schedule that runs
diff tues-friday morning and two different retention base backups on Saturday
morning. I set the retention of the differentials ot 7 day
