Hi Lukasz,

Thank you for testing the new Incrementa backup feature.

For those kinds of questions, it is better to send the mail to +users list so other people can learn/answer the question.

Please see my comments inline.

On Fri, 3 Jul 2020 at 15:55, Łukasz Kołaciński <l.kolacinski@storware.eu> wrote:

Dear Eyal Shenitzky

Could you help me with setting up ovirt 4.4? I am trying to implement incremental backups to our application and I have some questions.

1. First of all I am using mostly this documentation: https://www.ovirt.org/develop/release-management/features/storage/incremental-backup.html and I saw session on youtube. Are there any other sources of knowledge?

Currently no, those are the two best resources for this feature at this moment.

Note that we updated https://www.ovirt.org/develop/release-management/features/storage/incremental-backup.html recently so now it contains up-to-date information about all the operations that need to be done with the Engine in order to use this feature.

2. I can't change fields on diskattachment with PUT Method (to set incremental in backup field). I think I tried in every way and I am getting 405 Method Not Allowed.

Please try the following request -

PUT path-to-engine/ovirt-engine/api/vms/vm-uuid/diskattachments/disk-attachment-uuid

<disk_attachment>
  <disk>
    <name>disk-uuid</name>
    <backup>incremental</backup>
  </disk>

</disk_attachment>

3. When I am using REST API to get info about checkpoints with "GET /vms/vm-uuid/checkpoints/" I am getting response: "Could not find resource for full path". So this looks like something is not enabled or missing.

There is no 'checkpoints' service under any path at this moment, so the path you are using is not valid.

There is a backups service that you can find under -

GET path-to-engine/ovirt-engine/api/vms/vm-uuid/backups

To get a single backup you can use

GET path-to-engine/ovirt-engine/api/vms/vm-uuid/backups/backup-uuid

We are now working on exposing also the checkpoints service to allow removal of checkpoints, but this isn't ready yet.

4. I don't understand what ticket-uuid in imageio API is. How can I get dirty bitmaps after full backup? And how to use it because there is not "images" resource on /ovirt-engine/api/

Please look and the example script we developed in order to use this feature -

https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/backup_vm.py

Using this script you will be able to do all the needed operations in order to back up a VM.

There is a very detailed manual for it (when using --help / -h).

This script can interact with ImageIO in order to download the backup disks using the new 'client' library in ImageIO.

You can use it as a reference on how to interact with the Engine API and ImageIO.

On my environment I have:

CentOS 8.2

ovirt 4.4.0.3-1

libvirt 6.0.0-17

qemu-kvm 4.2.0

kvm 4.2.0-19

vdsm 4.40.16-1

It looks like you have the correct versions in order to use Incremental backup, but remember that the

Engine blocks incremental backup operations and allows only full backup by default.

In order to allow incremental backup in the engine, you need to do the following commands -

# engine-config -s "IsIncrementalBackupSupported=true"
# systemctl restart ovirt-engine

I look forward to hearing from you.

Best regards,

Łukasz Kołaciński

Junior Java Developer

e-mail: l.kolacinski@storware.eu

ul. Leszno 8/44
01-192 Warszawa
www.storware.eu

Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

Regards,

Eyal Shenitzky