Hi all Just moved to Bareos from an old and suffering Amanda installation, and things work, but very slowly indeed. Small files are slow, but that was somewhat expected. But when backing up large files, we get perhaps 25MB/s maximum, while copying over NFS gives me ~140MB/s for non-cached content (200MB/s+ for cached stuff). Storage backend for the VMs backed up are two Dell Equallogic PS6500 with 48x3TB disks each, connected on iSCSI with 4x1Gbps links each with multipath. Networking elsewhere is 10Gpbs. Generally, storage works well for everything, but the Bareos client is dead slow. I beleive I have tracked down the problem:
When Bareos backs up data, it reads in increments of 'Maximum Network Buffer Size', meaning 64kB or less. This isn't very much, and is AFAICS the reason why the 'iostat -mx 5' on the client tells me 100% utilisation on the disk being read. From strace and the code, I see a single thread looping through read() and write(), meaning it'll read a small bit of code, then send it over the network, probably wait for the ACK and then read a new chunk of 64kB etc. If the file on the client is in the OS cache, it seems to work rather fine (perhaps 100Mbps on a good day). But then, I don't have 50TiB to cache my fileservers :P Any idea how this could be fixed? roy -- 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.
