Lines Matching full:mirror
14 live block device jobs -- stream, commit, mirror, and backup. These can
118 (3) ``drive-mirror`` (and ``blockdev-mirror``): Synchronize a running
503 Live disk synchronization --- ``drive-mirror`` and ``blockdev-mirror``
513 The ``drive-mirror`` (and its newer equivalent ``blockdev-mirror``)
519 When you cancel an in-progress 'mirror' job *before* the source and
522 'mirror' job *after* it has indicated (via the event
527 Besides the 'mirror' job, the "active ``block-commit``" is the only
532 So there are two possible actions to take, after a 'mirror' job has
578 QMP invocation for ``drive-mirror``
582 way to [D], to a new target (``drive-mirror`` will create the destination
585 (QEMU) drive-mirror device=node-D target=e.qcow2 sync=full job-id=job0
587 "execute": "drive-mirror",
600 'mirror' job is "ready" to be completed (and QEMU will also emit an
612 "type": "mirror",
649 Comparing 'commit' and 'mirror': In both then cases, the overlay images
652 the case of 'mirror', a *new* target image is populated with the data
656 QMP invocation for live storage migration with ``drive-mirror`` + NBD
660 common use-cases that takes advantage of the ``drive-mirror`` primitive
748 (3) [On *source* QEMU] Then, invoke ``drive-mirror`` (NB: since we're
749 running ``drive-mirror`` with ``mode=existing`` (meaning:
754 …(QEMU) drive-mirror device=node-D target=nbd:localhost:49153:exportname=node-TargetDisk sync=top m…
756 "execute": "drive-mirror",
766 (4) [On *source* QEMU] Once ``drive-mirror`` copies the entire data, and the
801 Notes on ``blockdev-mirror``
804 The ``blockdev-mirror`` command is equivalent in core functionality to
805 ``drive-mirror``, except that it operates at node-level in a BDS graph.
807 Also: for ``blockdev-mirror``, the 'target' image needs to be explicitly
812 entire disk image chain, to a target, using ``blockdev-mirror`` would be:
822 (3) Perform ``blockdev-mirror`` (use ``"sync": "full"`` to copy the
826 (4) Optionally, query for active block jobs, there should be a 'mirror'
829 (5) Gracefully complete the 'mirror' block device job, and notice the
840 QMP invocation for ``blockdev-mirror``
875 Perform ``blockdev-mirror``, and notice the event ``BLOCK_JOB_READY``::
877 (QEMU) blockdev-mirror device=node-B target=node-E sync=full job-id=job0
879 "execute": "blockdev-mirror",
888 Query for active block jobs, there should be a 'mirror' job ready::
899 "type": "mirror",