[ovirt-users] Backup solution using the API

Mon Feb 16 12:44:32 UTC 2015

Dear Liron,

thanks alot, i know, i was following that, however the Live Merge Feature was missing in CentOS 7, that was already the discussion.

Now on Fedora 20 the Live Merge works (we have to stick to Fedora then until this is in CentOS 7.1 ?! )

I am experimenting with scripts to iterate through all machines and do a backup for all machines on a separate VM, I will let you know how that goes

Cheers
Soeren 

-----Original Message-----
From: Liron Aravot [mailto:laravot at redhat.com] 
Sent: Monday, February 16, 2015 10:15 AM
To: Soeren Malchow
Cc: Adam Litke; Nir Soffer; Thomas Keppler (PEBA); users at ovirt.org
Subject: Re: [ovirt-users] Backup solution using the API

----- Original Message -----
> From: "Soeren Malchow" <soeren.malchow at mcon.net>
> To: "Adam Litke" <alitke at redhat.com>, "Nir Soffer" 
> <nsoffer at redhat.com>
> Cc: "Thomas Keppler (PEBA)" <thomas.keppler at kit.edu>, users at ovirt.org
> Sent: Wednesday, February 11, 2015 7:30:48 PM
> Subject: Re: [ovirt-users] Backup solution using the API
> 
> Dear all,
> 
> i am a little lost, i tried quite a few things with the snapshots, so 
> far with python scripts I can iterate through the existing machines, 
> take one, make a snapshot and all this.
> 
> However, there are 2 problems I can not get around:
> 
> 1. even when on 3.5.1 I can not delete a snapshot on a running VM, if 
> I understood that correctly this relies on the Live Merge Feature 
> where the code is available in vdsm already but it needs a certain 
> libvirt version !?!?
> So question here is, can I delete a snapshot or not ? can I use only 
> the rest API not python  (excuse me I am not a developer)
> 
> 2. when I attach a snapshot to another virtual machine, how do I do 
> the backup then ? Does anybody have this already ?
Hi Soeren,
you can find detailed example for Backup/Restore flows here - http://www.ovirt.org/Features/Backup-Restore_API_Integration

thanks,
laravot.
> 
> The environment is running on CentOS 7 (hypervisors), Centos 6 (hosted 
> engine), the ovirt is on version 3.5.1, also we use gluster as a 
> storage backend where the gluster servers are managed within the 
> hosted engine in a separate cluster exporting the storage only.
> 
> Regards
> Soeren
> 
> 
> -----Original Message-----
> From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On 
> Behalf Of Adam Litke
> Sent: Tuesday, January 6, 2015 5:04 PM
> To: Nir Soffer
> Cc: Thomas Keppler (PEBA); users at ovirt.org
> Subject: Re: [ovirt-users] Backup solution using the API
> 
> On 15/12/14 04:31 -0500, Nir Soffer wrote:
> >----- Original Message -----
> >> From: "Blaster" <Blaster at 556nato.com>
> >> To: "Thomas Keppler (PEBA)" <thomas.keppler at kit.edu>, 
> >> users at ovirt.org
> >> Sent: Wednesday, December 10, 2014 8:06:58 PM
> >> Subject: Re: [ovirt-users] Backup solution using the API
> >>
> >> On 11/27/2014 9:12 AM, Keppler, Thomas (PEBA) wrote:
> >>
> >>
> >>
> >> Now, before I go into any more hassle, has somebody else of you 
> >> done a live-backup solution for oVirt? Are there any recommendations?
> >> Thanks for any help provided!
> >>
> >>
> >> I've been looking for a similar scheme for the last year. It was 
> >> not
> >> (really) possible in the past as there wasn't any way to destroy a 
> >> snapshot w/o shutting down the VM. Is this still the case, or are 
> >> snap shots fully implemented now?
> >>
> >> Basically, I'd like to:
> >> Tell VM to flush it's buffers
> >> suspend VM
> >> take snap shot of boot virtual disk resume VM
> >
> >You don't need to suspend the vm, qemu can create live snapshot. When 
> >the snapshot is done, you don't care about future io, it will simply 
> >not included in the backup.
> >
> >> backup the virtual boot disk from the Hypervisor using standard 
> >> commands (tar, cp, whatever)
> >
> >You can by attaching the snapshot to another vm
> >
> >> destroy the snapshot
> >
> >You can in ovirt 3.5.1 - we do not depend any more on future libvirt 
> >features.
> >Adam, can you confirm?
> 
> Yes, on 3.5.1 you'll be able to destroy the snapshot without impacting 
> the running VM.
> 
> >>
> >> This would at least give some BMR capabilities of your VMs.
> >>
> >> Ideally, I'd also like to be able to create a snapshot from within 
> >> the VM, do
> >
> >You can do this "within" the vm by using the engine REST API. But 
> >this can be fragile - for example, if the vm pauses, your backup tool 
> >within the vm will never complete :-)
> >
> >> a yum update, see if I like it or not, if I do, then destroy the 
> >> snap shot.
> >
> >Possible in 3.5.1 using REST API
> >
> >> If I don't, I want to promote the snapshot and boot from that, then 
> >> destroy the "original".
> >
> >Same
> >
> >Nir
> 
> --
> Adam Litke
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 