Il 09/03/2013 23:22, Stefan Hajnoczi ha scritto:
> @block-backup
>
> Start a point-in-time copy of a block device to a new destination.
>
> @device: the name of the device whose writes should be mirrored.
>
> @target: the target of the new image. If the file exists, or if it
> is a dev
On Thu, Mar 14, 2013 at 03:52:16PM -0600, Eric Blake wrote:
> On 03/09/2013 03:22 PM, Stefan Hajnoczi wrote:
> > @block-backup
> >
> > Start a point-in-time copy of a block device to a new destination.
> >
>
> I'm trying to figure out how this is different from drive-mirror. If I
> understand c
On 03/09/2013 03:22 PM, Stefan Hajnoczi wrote:
> @block-backup
>
> Start a point-in-time copy of a block device to a new destination.
>
I'm trying to figure out how this is different from drive-mirror. If I
understand correctly:
After starting drive-mirror, a write to the block device is also
On 03/09/2013 03:22 PM, Stefan Hajnoczi wrote:
> @block-backup
>
> Start a point-in-time copy of a block device to a new destination.
>
Is a BLOCK_JOB_COMPLETED event emitted when the copy is completed? If
not, it should be.
> +# Since 1.5
> +##
> +{ 'command': 'block-backup',
> + 'data': { '
@block-backup
Start a point-in-time copy of a block device to a new destination.
@device: the name of the device whose writes should be mirrored.
@target: the target of the new image. If the file exists, or if it
is a device, the existing file/device will be used as the new
de
