Re: [qubes-users] bottlenecks during qvm-backup
On 4/23/19 4:58 PM, lik...@gmx.de wrote: Hi, is there a possibility to find the bottlenecks during a qvm-backup? A backup of ~100GB with compression takes several hours. During the time the (4) cpu cores (xentop) are not used well and the harddisk (iotop) is also idling a lot. I'm creating a backup to a usb attached ext3 formated harddrive. How to find out which components are responsible for the slow process? Best, Pete Hi, You may want to try my new incremental backup tool that works with Qubes: https://github.com/tasket/sparsebak Using LVM snapshot metadata, it finds the volume changes instantly without having to read+hash the whole volume first. Its able to update large 100GB+ volumes in under 10 sec. (i.e. its proportional to the amount of changed data since the last backup) and testers say its pretty stable even in pre-beta. The 'new5' branch also has a new de-duplication feature that we're testing to save even more bandwidth and disk space. The only thing its lacking at this point is built-in encryption, so you'll have to supply that yourself with an encrypted filesystem if you desire it. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/068be0a5-fc6a-feac-1bd4-120e6c3c4488%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] bottlenecks during qvm-backup
On Tue, 23 Apr 2019 21:58:17 +0100 lik...@gmx.de wrote: > Hi, > > is there a possibility to find the bottlenecks during a qvm-backup? A > backup of ~100GB with compression takes several hours. During the > time the (4) cpu cores (xentop) are not used well and the harddisk > (iotop) is also idling a lot. I'm creating a backup to a usb attached > ext3 formated harddrive. > > How to find out which components are responsible for the slow process? > > Best, Pete > Just try copying 100Gb to the usb connected drive to see how long that takes. USB drive speed can be quite slow. Mike. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190423225301.42f29b62.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] bottlenecks during qvm-backup
Hi, is there a possibility to find the bottlenecks during a qvm-backup? A backup of ~100GB with compression takes several hours. During the time the (4) cpu cores (xentop) are not used well and the harddisk (iotop) is also idling a lot. I'm creating a backup to a usb attached ext3 formated harddrive. How to find out which components are responsible for the slow process? Best, Pete -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e301711a-da65-1f09-54cf-8ddd92278d05%40gmx.de. For more options, visit https://groups.google.com/d/optout.
