I can’t help with the hard-links, basefiles (never used that feature) or keeping monthly's while also doing an AI scheme.
The issue of unpurged volumes that have no jobs is why I have the script I shared. I highly recomend you do not delete volumes but use prune volume=<volume> yes
Which will force Bareos to review the state of the volume and then ether delete (have to delete both the catalog and the file on the filesystem) or truncate volstatus=Purged to free the space and make the volume ready for reuse when a new volume is needed.
> <Diagram_Backup_Strategy_old.png>
>
>
sim....@gmail.com schrieb am Freitag, 26. Juni 2020 um 10:04:49 UTC+2:
> Hello,
>
> First of all, thanks for the commands, those helped me much and I think I should use the bconsole more often instead of the GUI.
> I think I know what the problem is. I had a long-term job at the beginning and somehow this is where my storage got eaten up.
> There are consolidated jobs, which are not touched since 15 days and list "jobs volume=AI-Consolidated-0001" returns nothing.
> I will clean them up manually.
>
> Our goal was to do always incremental backups every 7 days, but with monthly backups for three months.
> Until now, we had a script which writes hardlinks everywhere it can, so there every backup was a full backup and even the 3 month old was in the incremental chain.
> This will save huge ammounts of space.
> Is this also possible with bareos?
>
> For illustration purpose:
>
>
> To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/d8f270c3-73ec-4d91-a948-99137368b05an%40googlegroups.com.
> <Diagram_Backup_Strategy_old.png>