[Borgbackup] Slow backup speed

[Marc Pope]

What about running it from the client? NFS overhead is likely the problem. You could run it using a ssh command to the client from the server. 

> On Oct 30, 2018, at 1:59 PM, Zack Coffey <clickwir at gmail.com> wrote:
> 
> I think you are right, it's not a bandwidth issue. But NFS dealing with that many small functions may be the bottleneck. 
> 
> I've seen NFS be the bottleneck many times when dealing with large amounts of small files or small changes. Big file transfers, it blazes. Tons of tiny ones, grinds to a halt. Some NFS mount tweaks can help that though.
> 
>> On Tue, Oct 30, 2018 at 2:55 AM Sebastian Pölsterl <sebp at k-d-w.org> wrote:
>> Hi,
>> 
>> I'm using borg via borgmatic to backup of about 10TB of data. Since 
>> incremental backups take about 13 hours, I was wondering if there's any 
>> configuration option that can be used to speed things up, or if 13 hours 
>> is an expected duration.
>> 
>> In total, the volume contains about 25 million files, but changes are 
>> rare. Backups are created daily and are carried out over a gigabit 
>> network connection with the client's disk mounted via NFS on the server 
>> running borg. Backups are created with --files-cache ctime,size and lz4 
>> compression. Based on monitoring bandwidth usage, I would say that 
>> network bandwidth is not the bottleneck.
>> 
>> Is there any configuration option I have been missing so far that could 
>> help to speed up daily backups?
>> 
>> Thanks for your help!
>> 
>> -- 
>> Sebastian
>> _______________________________________________
>> Borgbackup mailing list
>> Borgbackup at python.org
>> https://mail.python.org/mailman/listinfo/borgbackup
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20181030/ec44d923/attachment.html>