Comprehensive data protection for all workloads
Post Reply
hobbit
Influencer
Posts: 13
Liked: 4 times
Joined: Jan 08, 2013 11:02 am
Contact:

VeeamBackup Log-Compression algorithm - possible to change from gzip?

Post by hobbit »

We recently ran into an issue considering the space usage for Veeam logs on our Linux Backup Repositories ( /var/log/VeeamBackup ).

I see that on retention logs are compressed to gzip format. We could probably save some space if a better algorithm would be used. Logrotated on the same server uses xz by default, for example.

I found kb1825 describing various settings, but no mention considering compression program options. Is there a configurable option for this?
david.domask
Veeam Software
Posts: 2838
Liked: 650 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: VeeamBackup Log-Compression algorithm - possible to change from gzip?

Post by david.domask »

Hi hobbit,

At this time there is not a means of changing this.

While it can be considered, can I ask, did adjusting the other values from KB1825 help to manage the logs a bit?
David Domask | Product Management: Principal Analyst
hobbit
Influencer
Posts: 13
Liked: 4 times
Joined: Jan 08, 2013 11:02 am
Contact:

Re: VeeamBackup Log-Compression algorithm - possible to change from gzip?

Post by hobbit »

What helped me to save the necessary space for now was enabling transparent btrfs zstd compression on that logfolder. I have lots of logs not yet in archive format, disk usage of /var/log/VeeamBackup was reduced from 20G to 9.3G by that.

But still, making the used compression tool for log archiving configurable would be nice optimization that should be includable without much effort.
david.domask
Veeam Software
Posts: 2838
Liked: 650 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: VeeamBackup Log-Compression algorithm - possible to change from gzip?

Post by david.domask »

Thank you for sharing your solution and for the request!
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Bing [Bot], Semrush [Bot] and 3 guests