docs/block-replication: use blockdev-backup
We are going to deprecate drive-backup, so don't mention it here. Moreover, blockdev-backup seems more correct in the context. Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Reviewed-by: John Snow <jsnow@redhat.com>
This commit is contained in:
parent
2b22e7540d
commit
9a599217a4
@ -79,7 +79,7 @@ Primary | || Secondary disk <--------- hidden-disk 5 <---------
|
|||||||
|| | |
|
|| | |
|
||||||
|| | |
|
|| | |
|
||||||
|| '-------------------------'
|
|| '-------------------------'
|
||||||
|| drive-backup sync=none 6
|
|| blockdev-backup sync=none 6
|
||||||
|
|
||||||
1) The disk on the primary is represented by a block device with two
|
1) The disk on the primary is represented by a block device with two
|
||||||
children, providing replication between a primary disk and the host that
|
children, providing replication between a primary disk and the host that
|
||||||
@ -101,7 +101,7 @@ should support bdrv_make_empty() and backing file.
|
|||||||
that is modified by the primary VM. It should also start as an empty disk,
|
that is modified by the primary VM. It should also start as an empty disk,
|
||||||
and the driver supports bdrv_make_empty() and backing file.
|
and the driver supports bdrv_make_empty() and backing file.
|
||||||
|
|
||||||
6) The drive-backup job (sync=none) is run to allow hidden-disk to buffer
|
6) The blockdev-backup job (sync=none) is run to allow hidden-disk to buffer
|
||||||
any state that would otherwise be lost by the speculative write-through
|
any state that would otherwise be lost by the speculative write-through
|
||||||
of the NBD server into the secondary disk. So before block replication,
|
of the NBD server into the secondary disk. So before block replication,
|
||||||
the primary disk and secondary disk should contain the same data.
|
the primary disk and secondary disk should contain the same data.
|
||||||
|
Loading…
Reference in New Issue
Block a user