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 allpools storage=S-FilesForTape"
       Console = "truncate allpools storage=File"
   }

The prune and truncate is doing what it has always done, except that 
every volume for a particular storage that is marked as purged is 
written to every time the truncate command is run.  For previous 
releases (7.0.x and earlier - I haven't run 7.2) the behaviour was that 
only purged volumes that had not been truncated were written to (i.e. 
the truncate was done).

Possibly related, I see that volumes that are marked as purged have a 
non zero job count.

Are these expected behaviours?

Regards

Mike

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users