The dirty bitmap is already working well enough in QEMU 2.6. It can be used via LibVirt qemu-monitor-command. The only issue is that dirty bitmaps do not sustain VM restarts, snapshot creating/deleting, and VM live migration. However, this is not a big issue if you perform backups often than these operations. Since backups are in the qcow2 format, they can be placed on the Export storage, and restored directly from oVirt.
It would be relative simple to implement third-party backup solution, if disk locking mechanics was accessible via oVirt API. Implement this directly in oVirt would be even simpler as a Live Export feature, since dirty bitmaps work exactly like snapshots, and oVirt already has most of required logic. From: <[email protected]> on behalf of Yaniv Kaul <[email protected]> Date: Monday, 11 September 2017 at 17:14 To: Demeter Tibor <[email protected]> Cc: users <[email protected]> Subject: Re: [ovirt-users] CBT question On Mon, Sep 11, 2017 at 4:17 PM, Demeter Tibor <[email protected]<mailto:[email protected]>> wrote: Dear Listmembers, Somebody know when will be available the CBT (changed block tracking) feature in ovirt/rhev? It has to be implemented first in QEMU - where it is still being worked on. We plan to take advantage of it after it is ready in QEMU (and libvirt of course). We looking for an usable backup solution for our ovirt guests, but I've see, there are some API limitation yet. But nevertheless there are various backup solutions that can be used today, even if not as efficient as CBT. Y. Thanks in advance, R Tibor _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
