docs/interop/bitmaps.rst

37 granularities mean smaller bitmap sizes, but less targeted backups.
46 QEMU uses these bitmaps when making incremental backups to know which sections
245   node, nor does it affect any backups already created from this bitmap or
466 Losing a bitmap in this way does not invalidate any existing backups that have
467 been made from this bitmap, but no further backups will be able to be issued
497 #. At a later point, issue incremental backups from ``bitmap0``.
500 incremental backups made from this point forward would be correctly aligned to
504 backups after the VM has been running for a while, for which we would want to
513 #. At a later point, issue incremental backups from ``bitmap0``.
516           drive backup, incremental backups can still be authored from this
537 Incremental backups are simply partial disk images that can be combined with
544 full and incremental backups.
702          creation of new, full backups. This relationship is not saved or
704          remember which bitmaps are associated with which backups.
870 authored, allowing a user to continue to "consume" it to create new backups on
885 backups in a chain available to link against. This is not a problem at backup
972 both of them up such that the two backups represent the same crash-consistent
1088 #. Later, create new destination images for each of the incremental backups
1089    that point to their respective full backups:
1381 to delete any incremental backups that were created successfully in this
1471 to be made, new backups for both drives will need to be made, taking into