'Martin Schmid' via bareos-users
2018-08-24 17:31:17 UTC
Hi everybody
I guess that this question has been asked several times but I cannot find the reason for my problem:
I'm running bareos 17.2 on linux with several storage daemons on the network. All of them write reasonably fast with about 10MB/s to disks.
Most of the disks are configured as RAID1, some RAID0 and one is a single disks.
Only the single disk has a slow backup speed of never more than 1MB/s, sometimes even much lower.
If I replace the disk by an SSD, the backup speed rises to some 17MB/s. So it must be the disk.
But a cp of a large file runs with 75MB/s, sometimes more. So, it should not be the disk.
I've then enabled spooling with the spool directory being on a SSD.
The spool file writes with about 25MB/s but the despooling doesn't rise above 1MB/s.
Since this shouldn't be anything other than a data copy, why doesn't it reach the write speed of a file copy?
All compression work is done by the file daemon and should not affect despooling.
And database speed is not the reason, eider. There's no CPU load and the same data sent to another device runs much faster.
So, what's the explanation for this? And is there something effective to tune at sd level? Block size or so..
Regards,
Martin
I guess that this question has been asked several times but I cannot find the reason for my problem:
I'm running bareos 17.2 on linux with several storage daemons on the network. All of them write reasonably fast with about 10MB/s to disks.
Most of the disks are configured as RAID1, some RAID0 and one is a single disks.
Only the single disk has a slow backup speed of never more than 1MB/s, sometimes even much lower.
If I replace the disk by an SSD, the backup speed rises to some 17MB/s. So it must be the disk.
But a cp of a large file runs with 75MB/s, sometimes more. So, it should not be the disk.
I've then enabled spooling with the spool directory being on a SSD.
The spool file writes with about 25MB/s but the despooling doesn't rise above 1MB/s.
Since this shouldn't be anything other than a data copy, why doesn't it reach the write speed of a file copy?
All compression work is done by the file daemon and should not affect despooling.
And database speed is not the reason, eider. There's no CPU load and the same data sent to another device runs much faster.
So, what's the explanation for this? And is there something effective to tune at sd level? Block size or so..
Regards,
Martin
--
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+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.