Lines Matching full:as

16 This document explains the conceptual mechanisms, as well as up-to-date,
32 bitmap is 64K, each '1' bit means that a 64K region as a whole may have
33 changed in some way, possibly by as little as one byte.
39 The size of a bitmap (in bytes) can be computed as such:
156       correctly, and can no longer be used. It remains in memory to serve as
276 - An incremental backup created from an empty bitmap will copy no data, as if
336   as ``+inconsistent`` if any such writes do happen. Backups made from such
370 - Merge takes one or more bitmaps as a source and merges them together into a
371   single destination, such that any segment marked as dirty in any source
378   operations will continue to cumulatively mark more segments as dirty.
415 attached to nodes serving as the root for guest devices.
452 As outlined in `Supported Image Formats`_, QEMU can persist bitmaps to qcow2
462 will be marked as ``+inconsistent`` at next load and considered unsafe to use
505 perform actions such as the following:
515 .. note:: As a consideration, if ``bitmap0`` is created prior to the full
553 As outlined in the Transactions - `Justification`_ section, perhaps we want to
712    - Using QMP commands with the VM paused as in the `Justification`_ section,
723    full backup as a backing image.
879 valid backup of the disk as it was when that backup was issued.
965 chain by hand as an ephemeral property at runtime, but that is beyond the
1219 Incremental Push Backup jobs that fail individually behave simply as
1329 #. Retry the command after fixing the underlying problem, such as
1496 it's possible to instruct them to complete or fail together as a group. QMP
1509 points-in-time, as in individual failure cases.
1599 The transaction as a whole can simply be re-issued at a later time.
1618    THIS DOCUMENTATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS