On 2/24/22 04:06, Chris Wilkinson wrote:
> Many thanks Bill. I followed your steps and now it is creating volumes with
> the required size. I thought I had done those
> already using Baculum but I must have missed a step somewhere. I took out the
> max volume size from SD this time which I
> hadn
Many thanks Bill. I followed your steps and now it is creating volumes with the
required size. I thought I had done those already using Baculum but I must have
missed a step somewhere. I took out the max volume size from SD this time which
I hadn’t done before.
Best
-Chris-
> On 24 Feb 2022
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 expectati
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
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
