Hi All,
I'm currently setting up a disk-based storage pool in Bacula and am 
wondering what I should set "Maximum Volume Bytes" to. I was thinking of 
setting it to "100G", but am just wondering if this is sane.

FYI, the total data of our clients is 15 TB, but we are told that this 
data should at least double each year.

I noticed that there seems to be a limit on the number of disk-based 
volumes in a pool due to the suffix having 4 digits, i.e. 0001. This 
adds up to about 10,000 possible volumes per pool. So 10,000 volumes x 
100 GB is 1 PB. That seems like overkill. Perhaps setting "Maximum 
Volume Bytes = 10G" would be more reasonable since this would add up to 
100 TB.

I'm also storing these file volumes on ZFS (v28 w/ dedup=on), and am 
wondering if smaller volumes will dedup better than larger ones. I'm 
curious to see what others are doing to take advantage of dedup-enabled 
ZFS storage w/ Bacula.

Thanks,
Mike

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users