I did. I implemented the runscript mentioned there that runs daily.
Job {
Name = CatalogBackup ...
RunScript {
RunsWhen=After
RunsOnClient=No
Console = "purge volume action=truncate allpools storage=File"
}
}
This doesn't seem to be having the desired effect. Volumes are not being
truncated though I can truncate them manually with bconsole truncate if
they are first purged.
The thing that puzzles me about this is the storage= statement since I have
multiple storages defined.
It seems that truncate will only work on purged volumes and volumes will
not be purged until their retention time is up.
Regards
Chris Wilkinson
On Thu, 16 Aug 2018, 10:15 p.m. Jérôme Blion, <jerome.bl...@free.fr> wrote:
> Le 16/08/2018 à 13:56, Radosław Korzeniewski a écrit :
>
> Hello,
>
> 2018-08-15 17:45 GMT+02:00 Chris Wilkinson <winstonia...@gmail.com>:
>
>> I'm approaching 100% capacity on my backup storage so will soon start
>> running into out of space warnings. Is there a way that the disc space used
>> by volumes with no associated jobs can be reclaimed and the storage made
>> available for reuse?
>>
>>
> You can use a truncate command for that.
>
>
> Hi,
>
> Did you have a look on that:
> https://blog.bacula.org/whitepapers/CommunityDiskBackup.pdf
>
> HTH
> Jérôme Blion.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
