Because i probably sent message somewhere...Repeated post. So i configured compression on the filesets for our Always Incremental scenario. Daily backups (based on the comparision between uncompressed and compressed file content) are compressed. But Consolidate job doesn't have Fileset variable, so it looks uncompressed. And continually, longterm (VirtualFull) volumes with Fileset configured seems uncompressed too. Any idea, where is something missing? Thanks.
On Monday, April 27, 2026 at 10:14:57 AM UTC+2 Bruno Friedmann (bruno-at-bareos) wrote: > Compression is per block and if is detected, so if you do compression on > the storage, it will work transparently (well more cpu / ram etc .. but you > get it). > Also if a block is compressed, you can also send it compressed back to the > FD which do the uncompression. > Just be sure to have SD and FD supporting the same compression algo. > > Regards > On Monday, 27 April 2026 at 10:00:02 UTC+2 Martin Prochazka wrote: > >> Hi, >> >> i am validating possibility to enable compression for space saving >> (currently 24 TB data). >> >> Version 25.03 Community, Always Incremental mode. Turning it on the >> bareos (storage daemon) side. >> >> - what will happen if compression is enabled - will bareos still works >> with previous uncompressed volumes and just new volumes will be compressed? >> - opposite scenario, disabling compression if there will be issue - will >> bareos process combination plain + compressed + plain volumes? >> >> Thanks. >> > -- 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 view this discussion visit https://groups.google.com/d/msgid/bareos-users/2e9a0b6d-849d-42d8-ae73-77263e7df2e4n%40googlegroups.com.
