
This is a multi-part message in MIME format. --------------CD14183D7010EED916923476 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Is it just me just finds strange the way oVirt/RHEV does backup ? At the present you have to snapshot the VM (fine by that), but them you have to clone AND export it to an Export Domain, then delete the cloned VM. That means three copies of the same VM somewhere. Wouldn't it be more logical to take a snapshot, get the then read-only disk and export it directly from any host that can read it, and finally remove the snapshot ? Why the need to clone AND export ? What is the limitation to pull this VM directlly from host decreasing the time it takes the overall process and mainly the amount of storage necessary to do this job. Ohh and before I forget by this workflow the disks are hammered a lot more decreasing their lifetime and may causing performance issues mainly during the clone process. Fernando On 21/09/2017 14:59, Nathanaël Blanchet wrote:
Yes seems to be good, the UI is very nice, but I didn't manage to make one backup though the connection to the API is okay. I followed the README but Nothing happens when lauching the backup processus...
Le 21/09/2017 à 19:34, Niyazi Elvan a écrit :
Hi,
You may check my project Bacchus at https://github.com/openbacchus/bacchus
On Sep 21, 2017 19:54, "Bernardo Juanicó" <bjuanico@gmail.com <mailto:bjuanico@gmail.com>> wrote:
I didnt know that, we may adapt it in the future, but at first we will probably just write a basic set of scripts for minimal backup functionally since our dev time is limited.
Ill keep you in mind when looking into it.
Regards,
Bernardo
PGP Key <http://pgp.mit.edu/pks/lookup?op=get&search=0x695E5BCE34263F5B> Skype: mattraken
2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet <blanchet@abes.fr <mailto:blanchet@abes.fr>>:
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.
You may want to adapt it?
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@abes.fr <mailto:blanchet@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@ovirt.org <mailto:Users@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@abes.fr <mailto:blanchet@abes.fr>
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@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@abes.fr <mailto:blanchet@abes.fr>
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@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 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------CD14183D7010EED916923476 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <p>Is it just me just finds strange the way oVirt/RHEV does backup ?</p> <p>At the present you have to snapshot the VM (fine by that), but them you have to clone AND export it to an Export Domain, then delete the cloned VM. That means three copies of the same VM somewhere.</p> <p>Wouldn't it be more logical to take a snapshot, get the then read-only disk and export it directly from any host that can read it, and finally remove the snapshot ?</p> <p>Why the need to clone AND export ? What is the limitation to pull this VM directlly from host decreasing the time it takes the overall process and mainly the amount of storage necessary to do this job.<br> Ohh and before I forget by this workflow the disks are hammered a lot more decreasing their lifetime and may causing performance issues mainly during the clone process.</p> <p>Fernando<br> </p> <br> <div class="moz-cite-prefix">On 21/09/2017 14:59, Nathanaël Blanchet wrote:<br> </div> <blockquote type="cite" cite="mid:a04a5248-4735-90b6-90f8-33c59c88c914@abes.fr"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <p>Yes seems to be good, the UI is very nice, but I didn't manage to make one backup though the connection to the API is okay. I followed the README but Nothing happens when lauching the backup processus...<br> </p> <br> <div class="moz-cite-prefix">Le 21/09/2017 à 19:34, Niyazi Elvan a écrit :<br> </div> <blockquote type="cite" cite="mid:CAKwPMRfD0md25+85NkuviM+W8Cv3WmxNe2ZHXTZSxC4pLPRzoQ@mail.gmail.com"> <div dir="auto"> <div>Hi, <div dir="auto"><br> </div> <div dir="auto">You may check my project Bacchus at <a href="https://github.com/openbacchus/bacchus" moz-do-not-send="true">https://github.com/openbacchus/bacchus</a> </div> <div dir="auto"><br> </div> <div dir="auto"><br> </div> <br> <div class="gmail_extra"><br> <div class="gmail_quote">On Sep 21, 2017 19:54, "Bernardo Juanicó" <<a href="mailto:bjuanico@gmail.com" moz-do-not-send="true">bjuanico@gmail.com</a>> wrote:<br type="attribution"> <blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">I didnt know that, we may adapt it in the future, but at first we will probably just write a basic set of scripts for minimal backup functionally since our dev time is limited. <div><br> </div> <div>Ill keep you in mind when looking into it.</div> <div><br> </div> <div>Regards,</div> <div><br> </div> <div>Bernardo</div> </div> <div class="gmail_extra"><br clear="all"> <div> <div class="m_297017758352693916gmail_signature" data-smartmail="gmail_signature"> <div dir="ltr"><a href="http://pgp.mit.edu/pks/lookup?op=get&search=0x695E5BCE34263F5B" target="_blank" moz-do-not-send="true">PGP Key</a><br> <div><a moz-do-not-send="true">Skype: mattraken</a><br> </div> </div> </div> </div> <div class="elided-text"> <br> <div class="gmail_quote">2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet <span dir="ltr"><<a href="mailto:blanchet@abes.fr" target="_blank" moz-do-not-send="true">blanchet@abes.fr</a>></span>:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div text="#000000" bgcolor="#FFFFFF"> <p>Hi Bernardo,</p> <p>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. <br> </p> <p>You may want to adapt it?<br> </p> <div> <div class="m_297017758352693916h5"> <br> <div class="m_297017758352693916m_-8694593473241100559moz-cite-prefix">Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :<br> </div> <blockquote type="cite"> <div dir="ltr">Hi Nathanael, <div><br> </div> <div>You may want to take a look at this too:<br> <br> <a href="https://github.com/bjuanico/oVirtBackup" target="_blank" moz-do-not-send="true">https://github.com/bjuanico/oV<wbr>irtBackup</a><br> </div> <div><br> </div> <div>Regards,</div> <div><br> </div> <div>Bernardo</div> <div class="gmail_extra"><br clear="all"> <div> <div class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401gmail_signature" data-smartmail="gmail_signature"> <div dir="ltr"><a href="http://pgp.mit.edu/pks/lookup?op=get&search=0x695E5BCE34263F5B" target="_blank" moz-do-not-send="true">PGP Key</a><br> <div><a moz-do-not-send="true">Skype: mattraken</a><br> </div> </div> </div> </div> <br> <div class="gmail_quote">2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet <span dir="ltr"><<a href="mailto:blanchet@abes.fr" target="_blank" moz-do-not-send="true">blanchet@abes.fr</a>></span>:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div text="#000000" bgcolor="#FFFFFF"> <p>Hello Victor,</p> <p>I have some questions about your script<br> </p> <br> <div class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505moz-cite-prefix">Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :<br> </div> <blockquote type="cite"> <div dir="ltr"> <div>Hello everyone, i created a python tool to backup and restore oVirt's VMs.</div> <div><br> </div> <div>Also i created a little "how to" on my blog:</div> <div><a href="http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/" target="_blank" moz-do-not-send="true">http://blog.infratic.com/2017/<wbr>07/create-ovirtrhevs-vm-backup<wbr>/</a></div> </div> </blockquote> <ul> <li>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.</li> </ul> <ol> <li><i>Take a snapshot of the virtual machine to be backed up - (existing oVirt REST API operation)</i></li> <li><i>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></li> </ol> <p><font color="#ff0000">I can't see any vm configuration anywhere but only the qcow2 disk itself</font></p> <ol> <li><i>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)</i></li> <li> <i><br> </i></li> <li><i>Detach the disk snapshots that were attached in (4) from the virtual appliance - (added capability to oVirt as part of the Backup API)</i></li> </ol> <p>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.<br> </p> <ul> <li>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. <br> </li> </ul> <p>Do you plan to backup and restore a full VM (disks + vm definition) in a next release?<br> </p> <blockquote type="cite"> <div dir="ltr"> <div><br> </div> <div>I hope it help someone else</div> <div><br> </div> <div>Regards</div> <div><br clear="all"> <div> <div class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505gmail_signature"> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"> <div> <div dir="ltr"><span>Victor Acosta<br> <br> </span></div> <div><span></span></div> <div dir="ltr"><span></span><span><span><img src="https://docs.google.com/uc?id=0BxRkeOBHApwsV2Ywcl92YWlaQnc&export=downlo..." moz-do-not-send="true" height="96" width="77"><img src="https://docs.google.com/uc?id=0BxRkeOBHApwsWDFFcGZ2X1czc1E&export=downlo..." moz-do-not-send="true" height="96" width="76"><img src="https://docs.google.com/uc?id=0BxRkeOBHApwsMTVrSHp2Y0NEY28&export=downlo..." moz-do-not-send="true" height="96" width="93"></span></span><br> <img alt="" moz-do-not-send="true"></div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> <br> <fieldset class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505mimeAttachmentHeader"></fieldset> <br> <pre>______________________________<wbr>_________________ Users mailing list <a class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505moz-txt-link-abbreviated" href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send="true">Users@ovirt.org</a> <a class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><span class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401HOEnZb"><font color="#888888"> </font></span></pre> <span class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401HOEnZb"><font color="#888888"> </font></span></blockquote> <span class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401HOEnZb"><font color="#888888"> <br> <pre class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques <a href="https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala&entry=..." target="_blank" moz-do-not-send="true">227 avenue Professeur-Jean-Louis-Viala</a> 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class="m_297017758352693916m_-8694593473241100559m_-6967630627070421401m_7400844792036080505moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr" target="_blank" moz-do-not-send="true">blanchet@abes.fr</a> </pre> </font></span></div> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send="true">Users@ovirt.org</a><br> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br> <br> </blockquote> </div> <br> </div> </div> </blockquote> <br> <pre class="m_297017758352693916m_-8694593473241100559moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques <a href="https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala&entry=..." target="_blank" moz-do-not-send="true">227 avenue Professeur-Jean-Louis-Viala</a> 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class="m_297017758352693916m_-8694593473241100559moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr" target="_blank" moz-do-not-send="true">blanchet@abes.fr</a> </pre> </div> </div> </div> </blockquote> </div> <br> </div> </div> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" moz-do-not-send="true">Users@ovirt.org</a><br> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br> <br> </blockquote> </div> <br> </div> </div> </div> </blockquote> <br> <pre class="moz-signature" cols="72">-- 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 <a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr" moz-do-not-send="true">blanchet@abes.fr</a> </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------CD14183D7010EED916923476--