Firstly, it's perfectly normal that hardware compression rate drops when
dealing with encrypted data. Compression ratio depends heavily on
entropy of input data and good encryption assures uniform distribution
of encrypted data so there's no point in compressing data _after_
encryption.
Secondly, in Bareos encryption is the property of a filedaemon so it's
applied to all the data from a configured client. Compression however is
defined on the FileSet resource level so you can mix compressed and
uncompressed files within one job. So it only makes sense to encrypt
data after the job is being initially pulled from the client.
You can of course look into the sources (Bareos is open-source after all
;-)) to confirm it but I think it should be reasonable enough.
Best regards,
MK
On 23.09.2019 17:14, Steffen Knauf wrote:
Hello,
we enabled encryption on the clients. Hardware compression is enabled,
too. By activating encryption the compression Rate is nearly fallen to
2-5% (from 50%). I plan to enable compression on the bareos Clients and
disable Harware compression. Can someone confirm that encryption is
done after compression on the bareos clients?
Thanks & greets
Steffen
--
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/e7bc07dc-9b42-cb23-ba62-a9d29fe8f048%40gmail.com.
