[pve-devel] new pve-qemu-kvm 2.5 packages on pvetest

[Alexandre DERUMIER]

>> I think they use qcow2.
>
>>Who? Do you talk about the RHEV backup?

I'm just talking about qemu qmp commands.

I really don't known how ovirt/rhev/openstack have implemented it . (If they have implemented backup)


But I think I'm wrong, they can use any disk format for backup target

I think it's more like the disk mirror feature, but at the time of the begin of backup start

So the backup file is a disk that you can reuse directly without need to restore



drive-backup
------------
Start a point-in-time copy of a block device to a new destination.  The
status of ongoing drive-backup operations can be checked with
query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
The operation can be stopped before it has completed using the
block-job-cancel command.
Arguments:
- "device": the name of the device which should be copied.
            (json-string)
- "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
            destination.  If it does not exist, a new file will be created.
            (json-string)
- "format": the format of the new destination, default is to probe if 'mode' is
            'existing', else the format of the source
            (json-string, optional)
- "sync": what parts of the disk image shou

blockdev-backup
---------------
The device version of drive-backup: this command takes an existing named device
as backup target.
Arguments:
- "device": the name of the device which should be copied.
            (json-string)
- "target": the name of the backup target device. (json-string)
- "sync": what parts of the disk image should be copied to the destination;
          possibilities include "full" for all the disk, "top" for only the
          sectors allocated in the topmost image, or "none" to only replicate
          new I/O (MirrorSyncMode).
- "speed": the maximum speed, in bytes per second (json-int, optional)
- "on-source-error": the action to take on an error on the source, default
                     'report'.  'stop' and 'enospc' can only be used
                     if the block device supports io-status.
                     (BlockdevOnError, optional)
- "on-target-error": the action to take on an error on the target, default
                     'report' (no limitations, since this applies to
                     a different block device than device).
                     (BlockdevOnError, optional)


----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 22 Janvier 2016 15:49:06
Objet: Re: [pve-devel] new pve-qemu-kvm 2.5 packages on pvetest

> >>What is the qemu backup format? 
> 
> I think they use qcow2. 

Who? Do you talk about the RHEV backup?