[ovirt-users] oVirt's VM backup

Nathanaël Blanchet blanchet at abes.fr
Mon Sep 25 09:51:44 UTC 2017



Le 25/09/2017 à 11:27, Yaniv Kaul a écrit :
>
>
> On Mon, Sep 25, 2017 at 11:02 AM, Nathanaël Blanchet <blanchet at abes.fr 
> <mailto:blanchet at abes.fr>> wrote:
>
>
>
>     Le 24/09/2017 à 11:11, Yaniv Kaul a écrit :
>>
>>
>>     On Sep 21, 2017 7:09 PM, "Nathanaël Blanchet" <blanchet at abes.fr
>>     <mailto:blanchet at abes.fr>> wrote:
>>
>>         Hi Bernardo,
>>
>>         Thanks, I knew this tool, but it is based on sdk3 which will
>>         be removed in the next version 4.2, so I'm looking at sdk4
>>         project.
>>
>     So it has recently changed! There was a dedicated ticket in
>     bugzilla about this and many warnings intended to users, but
>     nothing to tell sdk3 removal will be postponed...
>
>
> We decided to just let it stay, instead of forcing everyone to convert.
Nice to hear such a new, community is the key, and ovirt devs seem to 
remember!
> Note that none of the new features since 4.0 are supported in v3 API, 
> it has far fewer examples, documentation or features for the SDKs 
> themselves (see[1] for example).
So does that mean v3 API will be kept far in the future? What about 
derivated tools like ovirt-shell?
>
> From personal experience, I believe it is also easier to develop with 
> the new SDKs.
> Y.
>
> [1] https://ovirt.org/blog/2017/05/higher-performance-for-python-sdk/
>
>
>>
>>     SDKv3 will not be removed in 4.2.
>>
>>         You may want to adapt it?
>>
>>
>>     Note that you can gradually move to v4. You can mix v4 API with
>>     v3 API and convert function by function.
>>     Y.
>>
>>
>>         Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>>>         Hi Nathanael,
>>>
>>>         You may want to take a look at this too:
>>>
>>>         https://github.com/bjuanico/oVirtBackup
>>>         <https://github.com/bjuanico/oVirtBackup>
>>>
>>>         Regards,
>>>
>>>         Bernardo
>>>
>>>         PGP Key
>>>         <http://pgp.mit.edu/pks/lookup?op=get&search=0x695E5BCE34263F5B>
>>>         Skype: mattraken
>>>
>>>         2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet
>>>         <blanchet at abes.fr <mailto:blanchet at abes.fr>>:
>>>
>>>             Hello Victor,
>>>
>>>             I have some questions about your script
>>>
>>>
>>>             Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a
>>>             écrit :
>>>>             Hello everyone, i created a python tool to backup and
>>>>             restore oVirt's VMs.
>>>>
>>>>             Also i created a little "how to" on my blog:
>>>>             http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>>>             <http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/>
>>>
>>>               * Backup step is okay, and I get a usable qcow2 image
>>>                 of the snapshot vm in the backup vm. It seems to be
>>>                 compliant with the official backup API, except on
>>>                 the step 2.
>>>
>>>              1. /Take a snapshot of the virtual machine to be backed
>>>                 up - (existing oVirt REST API operation)/
>>>              2. /Back up the virtual machine configuration at the
>>>                 time of the snapshot (the disk configuration can be
>>>                 backed up as well if needed) - (added capability to
>>>                 oVirt as part of the Backup API)/
>>>
>>>             I can't see any vm configuration anywhere but only the
>>>             qcow2 disk itself
>>>
>>>              1. /Attach the disk snapshots that were created in (1)
>>>                 to the virtual appliance for data backup - (added
>>>                 capability to oVirt as part of the Backup API)/
>>>              2. /
>>>                 /
>>>              3. /Detach the disk snapshots that were attached in (4)
>>>                 from the virtual appliance - (added capability to
>>>                 oVirt as part of the Backup API)/
>>>
>>>             An other case is when the vm to backup has more than one
>>>             disk. After I tested it, I found that only one qcow2
>>>             disk is saved on the backup vm. This is really a matter
>>>             when the original vm has many disks part of lvm, it
>>>             makes the vm restoration unusable.
>>>
>>>               * About vm restoration, it seems that you are using
>>>                 the upload_disk api, so the disk is uploaded to the
>>>                 pre-defined storage domain, so it is not a real vm
>>>                 restoration.
>>>
>>>             Do you plan to backup and restore a full VM (disks + vm
>>>             definition) in a next release?
>>>
>>>>
>>>>             I hope it help someone else
>>>>
>>>>             Regards
>>>>
>>>>             Victor Acosta
>>>>
>>>>
>>>>
>>>>
>>>>             _______________________________________________
>>>>             Users mailing list
>>>>             Users at ovirt.org <mailto:Users at ovirt.org>
>>>>             http://lists.ovirt.org/mailman/listinfo/users
>>>>             <http://lists.ovirt.org/mailman/listinfo/users>
>>>
>>>             -- 
>>>             Nathanaël Blanchet
>>>
>>>             Supervision réseau
>>>             Pôle Infrastrutures Informatiques
>>>             227 avenue Professeur-Jean-Louis-Viala
>>>             <https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala&entry=gmail&source=g>
>>>             34193 MONTPELLIER CEDEX 5 	
>>>             Tél. 33 (0)4 67 54 84 55
>>>             Fax  33 (0)4 67 54 84 14
>>>             blanchet at abes.fr <mailto:blanchet at abes.fr>  
>>>
>>>
>>>             _______________________________________________
>>>             Users mailing list
>>>             Users at ovirt.org <mailto:Users at ovirt.org>
>>>             http://lists.ovirt.org/mailman/listinfo/users
>>>             <http://lists.ovirt.org/mailman/listinfo/users>
>>>
>>>
>>
>>         -- 
>>         Nathanaël Blanchet
>>
>>         Supervision réseau
>>         Pôle Infrastrutures Informatiques
>>         227 avenue Professeur-Jean-Louis-Viala
>>         <https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala&entry=gmail&source=g>
>>         34193 MONTPELLIER CEDEX 5 	
>>         Tél. 33 (0)4 67 54 84 55
>>         Fax  33 (0)4 67 54 84 14
>>         blanchet at abes.fr <mailto:blanchet at abes.fr>  
>>
>>
>>         _______________________________________________
>>         Users mailing list
>>         Users at ovirt.org <mailto:Users at ovirt.org>
>>         http://lists.ovirt.org/mailman/listinfo/users
>>         <http://lists.ovirt.org/mailman/listinfo/users>
>>
>>
>
>     -- 
>     Nathanaël Blanchet
>
>     Supervision réseau
>     Pôle Infrastrutures Informatiques
>     227 avenue Professeur-Jean-Louis-Viala
>     <https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala&entry=gmail&source=g>
>     34193 MONTPELLIER CEDEX 5 	
>     Tél. 33 (0)4 67 54 84 55
>     Fax  33 (0)4 67 54 84 14
>     blanchet at abes.fr <mailto:blanchet at abes.fr>  
>
>

-- 
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5 	
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanchet at abes.fr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170925/32821a24/attachment.html>


More information about the Users mailing list