I find it to be manageability. The on disk volumes sitll act like tape, so while things prune, they are effectively append only immutable. So you can only recycle them once everything on the volume ages out.
Setting size much like setting max age etc, is a way of capping unbouned appending and never recovering space. I guess you could run into maximum filesize but I have really ran into that on enterprise NAS like Isilon having 8TB max file size. Most filesystems you would use on a direct attached system have no effective limit. Brock Palen [email protected] www.mlds-networks.com Websites, Linux, Hosting, Joomla, Consulting > On Dec 12, 2024, at 2:27 PM, Jon Schewe <[email protected]> wrote: > > When using file based backups what are the reasons for setting "Maximum > Volume Bytes"? > If the filesystem supports files larger than any single backup would it make > sense to leave this unset and to set "Volume Use Duration" to something > really small and then each volume has a single job in it? > > > -- > You received this message because you are subscribed to the Google Groups > "bareos-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/bareos-users/46bdcbc8-d1d4-4615-8a4f-107cdcbc3659n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/2192AC3A-5AD2-46B5-A187-C8D988EDE575%40mlds-networks.com.
