On 23.01.2022 11:37, Radosław Korzeniewski wrote:
Hello,
pt., 21 sty 2022 o 14:22 Peter Milesson via Bacula-users
<bacula-users@lists.sourceforge.net> napisał(a):
If somebody has got experience with disk based, multi volume Bacula
backup, I would be grateful about some information (tips, what to
expect, pitfalls, etc.).
The best IMVHO (but not the only mine) is to configure one job = one
volume. You will get no real benefit to limit the size of a single volume.
In the single volume = single job configuration you can set up job
retention very easily as purging a volume will purge a single job only.
It is not required to "wait" a particular volume to fill up to start
retention. Purging a volume affects a single job only. And finally you
end up with a way less number of volumes then when limiting its size
to i.e. 10G.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
Hi Radosław,
thanks for your input. I'm still in the planning phase for the new
backup server, so all information is valuable.
Excuse me some elementary questions. How do you define volumes in the
pool for your configuration? I've been using Bacula a little more than
11 years, but up till now I've used virtual tapes with fixed sizes. Once
setup, it's just ticking, and the original configuration stays.
I use a one year retention scheme, and that will not change. I have got
no reason to purge jobs within that period and after a year, I would
like to do as little work as possible, having old volumes purged
automatically, when there is no more room on the RAID array. Using
tapes, this was automatic. When all volumes were full, the volume with
the oldest write time is purged, and reused.
Best regards,
Peter
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
