LWN: Comments on "Changed-block tracking and differential backups in QEMU" https://lwn.net/Articles/837053/ This is a special feed containing comments posted to the individual LWN article titled "Changed-block tracking and differential backups in QEMU". en-us Thu, 04 Sep 2025 05:49:36 +0000 Thu, 04 Sep 2025 05:49:36 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Changed-block tracking and differential backups in QEMU https://lwn.net/Articles/867208/ https://lwn.net/Articles/867208/ abii <div class="FormattedComment"> hi,<br> <p> yes, this is the more advanced version. I also have played with the push based model, here is another simple project:<br> <p> <a rel="nofollow" href="https://github.com/abbbi/qmpbackup">https://github.com/abbbi/qmpbackup</a><br> </div> Tue, 24 Aug 2021 10:22:10 +0000 Changed-block tracking and differential backups in QEMU https://lwn.net/Articles/842641/ https://lwn.net/Articles/842641/ kashyap <div class="FormattedComment"> Cool; reading the code, I see that you&#x27;re using the pull-based mechanism to take the backup via the NBD export. And also handling the backup restoration aspects yourself—which is &quot;required&quot; by the pull-based approach, anyway. I also notice you&#x27;re using the libvirt APIs. <br> <p> Thanks for sharing!<br> <p> <p> </div> Fri, 15 Jan 2021 14:30:23 +0000 Changed-block tracking and differential backups in QEMU https://lwn.net/Articles/841484/ https://lwn.net/Articles/841484/ abii <div class="FormattedComment"> I have created a small project on github that makes use of the new dirty bitmap features and<br> enables you to create live full/incremental backups for virtual machines running on libvirt/qemu <br> setups supporting the new features:<br> <p> <a rel="nofollow" href="https://github.com/abbbi/virtnbdbackup">https://github.com/abbbi/virtnbdbackup</a><br> </div> Thu, 31 Dec 2020 09:23:11 +0000 Changed-block tracking and differential backups in QEMU https://lwn.net/Articles/837922/ https://lwn.net/Articles/837922/ kashyap <div class="FormattedComment"> Very interesting; thanks for sharing. If you get time, might want to write a QEMU blog post[1] on your implementation approach—other users writing their own QEMU-based backup tooling might learn from your experience. :-)<br> <p> [1] <a href="https://www.qemu.org/blog/">https://www.qemu.org/blog/</a><br> </div> Fri, 20 Nov 2020 15:23:09 +0000 Changed-block tracking and differential backups in QEMU https://lwn.net/Articles/837769/ https://lwn.net/Articles/837769/ tlamp <div class="FormattedComment"> We used them to do fast and cheap backups on running machines for our new rust based open-source backup server[0], using a rust library with C bindings[1] to combine that with QEMU.<br> <p> The code enabling dirty bitmap tracking was surprisingly small, a subset of it can be found at [2] (we really need to clean up the oot patches a bit).<br> <p> We also use bitmaps in combination with ZFS sync to get a cheap and fast live migration even if bigger local storage is in use, as only the delta between the last synced snapshot needs to be moved, which can be tracked with those dirty bitmaps nicely.<br> <p> [0]: <a href="https://pbs.proxmox.com/">https://pbs.proxmox.com/</a><br> [1]: <a href="https://git.proxmox.com/?p=proxmox-backup-qemu.git;a=tree">https://git.proxmox.com/?p=proxmox-backup-qemu.git;a=tree</a><br> [2]: <a href="https://git.proxmox.com/?p=pve-qemu.git;a=blob;f=debian/patches/pve/0037-PVE-Backup-Add-dirty-bitmap-tracking-for-incremental.patch;h=c9740603da8c863dd401937088a082decd9830b3;hb=HEAD">https://git.proxmox.com/?p=pve-qemu.git;a=blob;f=debian/p...</a><br> </div> Thu, 19 Nov 2020 15:04:53 +0000