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ó" <bjuan...@gmail.com
<mailto:bjuan...@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 <blanc...@abes.fr
<mailto:blanc...@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
<blanc...@abes.fr <mailto:blanc...@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
blanc...@abes.fr <mailto:blanc...@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
blanc...@abes.fr <mailto:blanc...@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
blanc...@abes.fr
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
