Hi, I was successfully running Bareos 17.2 for two months after trying 18.2 (it was unstable when i have tested it). I do have some older pieces of hardware. Before installation of 18.2 my backup jobs was able to saturate 1Gbe ling without any problem. Now since i run 18.2 i have TLS-PSK enabled by default with following cipher: PSK-AES256-CBC-SHA. It seems that bareos-fd is a problem now because i cannot get more than 25MB/s. I have looked at cpu utilization and it is clear to me that bareos-fd is consuming single cpu core while there are still 3 idle cores available. Load profile is 90% user and 10% sys (single core). For me it seems that there is a lack of parallelism that leads into a bottleneck (in my case) when encryption is enabled (in 18.2 this is default).
I wanted to disable fd-sd compression selectively for this one particular slow fd. My questions are : 1. Is it possible to improve parallelism of bareos-fd ? 2. Could anyone please give me a short guidance how to disable encryption for one particular client ? I have another fd's which are running fine and it is likely that i could run on a full speed again after having fd-sd connection encription selectively disabled. 3. Is it possible to choose weaker encryption schema for this one fd ? PS. I have tested following options on fd and sd: TLS Enable TLS Psk Enable TLS Psk Require TLS Require It is a long story (can share lenghty experience) but the only thing i managed to get with mix of this parameters was unresponsive fd or fd that failed to start. Kind Regards, Bart -- 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 post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
