> Basically if I specify it on the command line, it would work. So it's not > honoring the behavior specified for volumes in that pool.
The code specifically requires that truncate be both enabled on the volume AND specified on the command line. So it isn't clear what the design intent was. It isn't hard to work with it either way once you know what the rules are. > Exactly. Should this be filed as a new bug? A functionality that has a > documented option that doesn't work? I would think that Always Incremental > doesn't work without this option. I guess this is up to you. I don't use the truncate option and I've been running AI backups for a long while, so it isn't true that it won't work. The severity of the issue is clearly higher for you than for me. It isn't clear from the code what the design intent was, i.e. it isn't code that throws an error but rather code that doesn't exist. BTW ... another random thought that occurs to me ... The script that I provided as a workaround for consolidate jobs not pruning the volumes executes the PRUNE command via console. Since it executes on a list of volumes that do not have any associated jobs (the query), there's no reason you can't run the PURGE command instead. You already know that the volume has no associated backup data so the safety of using the prune command isn't needed. If you write it that way you can just include the truncate option and your problem is completely solved. You just need to convince yourself that you can never accidentally purge a volume with active backup data on it. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
