Lines Matching refs:sync

38 ``blockdev-snapshot-sync``, or offline via ``qemu-img``)::
148 ``blockdev-snapshot-sync``, or ``blockdev-add``) as part of the disk
185 ``blockdev-snapshot-sync`` commands as following (which shows the
189 …(QEMU) blockdev-snapshot-sync node-name=node-A snapshot-file=b.qcow2 snapshot-node-name=node-B for…
191 "execute": "blockdev-snapshot-sync",
207 …(QEMU) blockdev-snapshot-sync node-name=node-B snapshot-file=c.qcow2 snapshot-node-name=node-C for…
208 …(QEMU) blockdev-snapshot-sync node-name=node-C snapshot-file=d.qcow2 snapshot-node-name=node-D for…
539 image chain (or only the top-most image, depending on the ``sync``
566 from start to end. With ``sync=none``, it's only the
585 (QEMU) drive-mirror device=node-D target=e.qcow2 sync=full job-id=job0
592 "sync": "full"
596 The ``"sync": "full"``, from the above, means: copy the *entire* chain
628 point-in-time is at the time of *ending* the sync. (The result of
751 target host), with the synchronization mode as 'top' (``"sync:
754 …irror device=node-D target=nbd:localhost:49153:exportname=node-TargetDisk sync=top mode=existing j…
762 "sync": "top"
822 (3) Perform ``blockdev-mirror`` (use ``"sync": "full"`` to copy the
852 …(QEMU) blockdev-snapshot-sync node-name=node-A snapshot-file=b.qcow2 snapshot-node-name=node-B for…
853 …(QEMU) blockdev-snapshot-sync node-name=node-B snapshot-file=c.qcow2 snapshot-node-name=node-C for…
854 …(QEMU) blockdev-snapshot-sync node-name=node-C snapshot-file=d.qcow2 snapshot-node-name=node-D for…
877 (QEMU) blockdev-mirror device=node-B target=node-E sync=full job-id=job0
884 "sync": "full"
958 (QEMU) drive-backup device=node-D sync=full target=e.qcow2 job-id=job0
964 "sync": "full",
1004 (3) Perform ``blockdev-backup`` (use ``"sync": "full"`` to copy the
1032 …(QEMU) blockdev-snapshot-sync node-name=node-A snapshot-file=b.qcow2 snapshot-node-name=node-B for…
1034 "execute": "blockdev-snapshot-sync",
1067 (QEMU) blockdev-backup device=node-B target=node-E sync=full job-id=job0
1074 "sync": "full"