I should have included this partial job log. There are many more the same apart from the Volume name. ... 23-Feb 22:34 homeserver-dir JobId 5539: Recycled volume "archive-full11257" 23-Feb 22:34 homeserver-sd JobId 5539: Recycled volume "archive-full11257" on File device "esata16tb" (/mnt/esata16tb/bacula), all previous data lost. 23-Feb 22:34 homeserver-sd JobId 5539: New volume "archive-full11257" mounted on device "esata16tb" (/mnt/esata16tb/bacula) at 23-Feb-2022 22:34. 23-Feb 22:34 homeserver-sd JobId 5539: End of medium on Volume "archive-full11257" Bytes=499,968,236 Blocks=7,750 at 23-Feb-2022 22:34. ...
On Wed, 23 Feb 2022, 11:38 pm Chris Wilkinson, <winstonia...@gmail.com> 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. > > > Regards > Chris Wilkinson > > >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
