Ok thanks. As far as I can tell this isn't causing any issues. It is
just different from what I recall for previous releases.
I have a couple of 7.0.5 systems still and will try and capture exactly
what they are doing in this space.
On 2016-03-02 11:18, Kern Sibbald wrote:
> I am not sure what
I am not sure what the problem is. If you ask Bacula to truncate a
volume and all the prerequisites are satisfied, it is going to truncate
it whether or not it was already truncated.
On 03/02/2016 03:38 AM, Brady, Mike wrote:
> Hi Kern,
>
> Sorry I have been a bit slow responding. Day job has b
Hi Kern,
Sorry I have been a bit slow responding. Day job has been getting the
way.
The simplest way for me to reproduce this is to just run by admin job
with the prune and truncate commands in it twice in a row from bconsole.
Running the job the first time I get
02-Mar 06:11 bacula04-dir Job
Hello,
What you describe would not be normal behavior, but to the best of my
knowledge the truncate code has not recently changed, so if it is
happening for you, please "show" us with before and after output.
Best regards,
Kern
On 02/29/2016 07:28 AM, Brady, Mike wrote:
> I am seeing a change
I am seeing a change in behaviour with Bacula 7.4 to what I had seen on
previous releases when truncating volumes.
I have a job that contains the following:
RunScript {
RunsWhen=Before
RunsOnClient=No
Console = "prune expired volume yes"
Console = "truncate allpool
