On 05/07/2017 10:52 PM, Chris Laprise wrote:
>
> I believe the largest qvm-backup bottlenecks to be related to disk
> I/O. For one, qb writes all data to a temporary file before sending it
> to the destination. Second, it seems to inefficiently read all parts
> of a sparse image file (although it does pack the file efficiently on
> the destination) so a 40GB image with only 8GB used will take a long
> time to process in relation to the space used -- these are the parts
> where the CPU is busy.
>
> Encryption should add very little to the backup overhead.
>
Agreed. That said, borgbackup onto a VM an then through SSH is about
four hours for an incremental backup, qvm-backup to a local disk (which
in principle should be much faster) is about eight hours. While I make
no guarantees about the integrity of a tampered borgbackup, the
performance math is clear.
I will publish the automation to do borgbackup on Qubes OS soon.
--
Rudd-O
http://rudd-o.com/
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/abf5192b-d6b3-7ae7-eada-06fa5ff66b59%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.
