I believe the answer is no, but as a happy bacula user for 10 years I am
somewhat surprised at the lack of flexibility.
The scenarios is this: A fileserver (1 client) with dozens of large
(size-wise) filesystems (12 jobs), but a couple of those filesystems are
large (filecount-wise). We would really like to set different file
retention periods on those high-filecount jobs (50+million), because
they are forcing the Catalog to go beyond our size constraints.
However, we also don't want to lose the file retention longevity of that
client's other jobs (5 years). The only hack I can think of is to
define 2 clients for 1 actual host, but I'd rather not go down that
route, because tracking jobs and associating them, especially over
multiple years, will get that much more tricky.
Ideas?
thanks,
Stephen
--
Stephen Thompson Berkeley Seismo Lab
step...@seismo.berkeley.edu 215 McCone Hall
Office: 510.664.9177 University of California
Berkeley, CA 94720-4760
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
