Lines Matching full:point

19 to another target image; and point-in-time (and incremental) backups of
122     Point-in-time (live) copy of a block device to a destination.
220 - Point 1: Guest state when [B] was created is contained in file [A]
221 - Point 2: Guest state when [C] was created is contained in [A] + [B]
222 - Point 3: Guest state when [D] was created is contained in
230   guest data for that point in time is *not* contained in that file
263     backing file pointer of image [D] will be adjusted to point to image
275     adjusted to point to [A].  I.e. after performing "intermediate
347     chain is the following, where image [C] is adjusted to point at [A]
353     resulting chain, where image [D] is adjusted to point to image [A]
397 to point to image [A], and the original 4-image chain will end up being
407     represents that old point-in-time, and may be valid in that context.
409     represents any point-in-time, and is invalid in any context.
537     ``BLOCK_JOB_COMPLETED``) will create a point-in-time (which is at
545     QEMU) to point to the target image, [E], causing all the new writes
546     from this point on to happen there.
558 (3) ``none`` -- Synchronize only the new writes from this point on.
625 at this point:
627 (a) Create a point-in-time snapshot by ending the synchronization.  The
628     point-in-time is at the time of *ending* the sync.  (The result of
811 E.g. the sequence of actions to create a point-in-time backup of an
938 you to create a point-in-time snapshot.
940 In this case, the point-in-time is when you *start* the
992 E.g. the sequence of actions to create a point-in-time backup
1108 point-in-time backup of the disk image chain -- i.e. contents from