Hi Spiros, you can play with the Maximum Network Buffer Size. If you are on a fast local Ethernet you can increase that value to 65,536 bytes like it is written in the documentation it could increase the throughput five to ten times. You can play with compression on and of. Because a windows 7 pc with a weak cpu can slow down the FD by compressing the data. If you need compression the bareos-sd can do that with autoxflate-sd. If you have enabled TLS and the data flows through a VLAN and isn't sensitive you can try to turn it of and have a look if it changes something. Maybe it could be that with spooling the data before writing to "tape/volume/disk" will allow bareos-sd and bareos-fd to transmit data more performant.
I don't know much about your network infrastructure but if you have more than 10 Switches and over 200 devices it could be better to put your backup infrastructure in an separated serverice VLAN. Makes only sense if your Routing device is fast enough for example a L3 switch. Otherwise you can split your network in VLAN segments for decreasing broadcast domains. In that case your bareos have to have a IP in each VLAN. If it is possible try to connect your physical server with bareos-sd to your core switch and a direct connection from your windows PC if possible. Just so be sure, windows 7 jumboframes are activated ;) ? Have a nice day, Marco -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
