docs/interop/live-block-operations.rst

14 live block device jobs -- stream, commit, mirror, and backup.  These can
121 (4) ``blockdev-backup`` (and the deprecated ``drive-backup``):
530     ``block-commit``", and 'backup') end automatically.
560     .. note:: In the case of ``blockdev-backup`` (or deprecated
561               ``drive-backup``), the behavior of ``none``
563               ``backup`` job consists of two parts: Anything that is
565               backup, and in the background the whole image is copied
811 E.g. the sequence of actions to create a point-in-time backup of an
934 Live disk backup --- ``blockdev-backup`` and the deprecated ``drive-backup``
937 The ``blockdev-backup`` (and the deprecated ``drive-backup``) allows
941 ``blockdev-backup`` (or deprecated ``drive-backup``) command.
944 QMP invocation for ``drive-backup``
947 Note that ``drive-backup`` command is deprecated since QEMU 6.2 and
956 image does not exist, ``drive-backup`` will create it)::
958     (QEMU) drive-backup device=node-D sync=full target=e.qcow2 job-id=job0
960         "execute": "drive-backup",
969 Once the above ``drive-backup`` has completed, a ``BLOCK_JOB_COMPLETED`` event
974 Moving from the deprecated ``drive-backup`` to newer ``blockdev-backup``
977 ``blockdev-backup`` differs from ``drive-backup`` in how you specify
978 the backup target. With ``blockdev-backup`` you can't specify filename
981 Correspondingly, ``blockdev-backup`` doesn't have ``mode`` and
986 Notes on ``blockdev-backup``
989 The ``blockdev-backup`` command operates at node-level in a Block Driver
992 E.g. the sequence of actions to create a point-in-time backup
993 of an entire disk image chain, to a target, using ``blockdev-backup``
1004 (3) Perform ``blockdev-backup`` (use ``"sync": "full"`` to copy the
1016 ``blockdev-backup``.
1018 QMP invocation for ``blockdev-backup``
1063 Then invoke ``blockdev-backup`` to copy the contents from the entire
1067     (QEMU) blockdev-backup device=node-B target=node-E sync=full job-id=job0
1069         "execute": "blockdev-backup",
1078 Once the above 'backup' operation has completed, the event,
1104     with the backup content.
1108 point-in-time backup of the disk image chain -- i.e. contents from
1109 images [A] and [B] at the time the ``blockdev-backup`` command was
1112 One way to confirm the backup disk image contains the identical content
1113 with the disk image chain is to compare the backup and the contents of