On 2/23/22 16:38, Chris Wilkinson wrote: > I modified a job to use a larger maximum volume size instead of the previous > 500M. When I run the job I find that new volumes > and recycled ones top out at 500M. I had expected them to go to 50G but this > isn't happening. Am I wrong in this expectation? > > I set the new value in both the Pool (Director) MaximumVolumeBytes=50G and > storage daemon MaximumVolumeSize=50G, updated the > pool and all volumes in the pool and restarted the daemons. >
Hello Chris, First, I would drop the SD MaximumVolumeSize=50G setting(s) and restart the SD. Then, in bconsole, run: * time (note the time) * reload * s dir - Check that `conf reloaded` time in the header is about the same as the time just printed. If it is not, then you will need to restart the Director. Then: * update pool=xxxx (for each pool you have modified) * update volume fromallpools - To make volumes already existing in modified pools inherit the new Pool settings This should solve the problem for you. Best regards, Bill -- Bill Arlofski w...@protonmail.com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
