similar to: how "safe" is blockcommit ?

Displaying 20 results from an estimated 9000 matches similar to: "how "safe" is blockcommit ?"

2018 Sep 10
1
Re: how "safe" is blockcommit ?
----- On Sep 7, 2018, at 9:26 PM, Eric Blake eblake@redhat.com wrote: > On 09/07/2018 12:06 PM, Lentes, Bernd wrote: >> Hi, >> >> currently i'm following >> https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit. I 'm >> playing around with it and it seems to be quite nice. >> What i want is a daily consistent backup of my image file
2018 Sep 08
1
Re: how "safe" is blockcommit ?
Il 07-09-2018 21:26 Eric Blake ha scritto: > We're also trying to add support for incremental backups into a future > version of libvirt on top of the qemu 3.0 feature of persistent > bitmaps in qcow2 images, which could indeed guarantee that you > transfer only the portions of the guest disk that were touched since > the last backup. But as that's still something I'm
2018 Sep 07
0
Re: how "safe" is blockcommit ?
On 09/07/2018 12:06 PM, Lentes, Bernd wrote: > Hi, > > currently i'm following https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit. I 'm playing around with it and it seems to be quite nice. > What i want is a daily consistent backup of my image file of the guest. > I have the idea of the following procedure: > > - Shutdown the guest (i can live
2020 Feb 07
2
Re: does the guest have a snapshot ?
----- On Feb 7, 2020, at 3:43 PM, Peter Krempa pkrempa@redhat.com wrote: > On Fri, Feb 07, 2020 at 15:25:22 +0100, Lentes, Bernd wrote: ... > > Libvirt is probably lacking the metadata for the snapshot. That is not a > problem though, because since libvirt doesn't support deletion of > external snapshots anyways currently you'd need to use the below > approach anyways.
2019 Jun 04
2
blockcommit of domain not successfull
Hi, i have several domains running on a 2-node HA-cluster. Each night i create snapshots of the domains, after copying the consistent raw file to a CIFS server i blockcommit the changes into the raw files. That's running quite well. But recent the blockcommit didn't work for one domain: I create a logfile from the whole procedure:
2019 Jun 11
2
Re: blockcommit of domain not successfull
----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion
2018 Mar 09
2
snapshot with libvirt tools or with lvm tools ?
Hi, i asked already a time ago about snapshots. I have some guests, each resides in a raw file, placed on an ext3 fs which is on top of a logical volume, for each guest a dedicated lv. The raw is not a "must have", if there are obvious reasons i can convert them to a qcow2. What i want is a consistent backup of each guest taken overnight. If possible i won't have downtime. I can use
2015 Dec 01
6
snapshot of running vm's
Hi, i'd like to create snapshots of my running vm's. I have several hosts with SLES11 SP4 64bit. I use libvirt 1.2.5-7.1 . VM's are Windows 7, SLES, Ubuntu, Opensuse. I use raw files for the vm's. I try to orientate myself by http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit . The hosts are backuped every night by a network based backup solution (Legato). My
2018 Feb 13
3
snapshot of a raw file - how to revert ?
Hi, i have the following system: pc59093:~ # cat /etc/os-release NAME="SLES" VERSION="11.4" VERSION_ID="11.4" PRETTY_NAME="SUSE Linux Enterprise Server 11 SP4" ID="sles" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:11:4" pc59093:~ # uname -a Linux pc59093 3.0.101-84-default #1 SMP Tue Oct 18 10:32:51 UTC 2016 (15251d6) x86_64
2020 Feb 07
2
does the guest have a snapshot ?
Hi, i'm cuurently a bit confused if a guest does have a valid snapshot or not. This is the xml: ... <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/crispor_1604/crispor_1604.sn'/> <backingStore type='file' index='1'> <format
2015 Dec 03
3
Re: snapshot of running vm's
> -----Oorspronkelijk bericht----- > Van: Lentes, Bernd [mailto:bernd.lentes@helmholtz-muenchen.de] > Verzonden: donderdag 3 december 2015 13:54 > Aan: libvirt-ML > CC: Dominique Ramaekers > Onderwerp: RE: snapshot of running vm's > > > ... > > > > > > Hi, > > > > > > i have inserted: > > > > > > <channel
2019 Jun 13
0
Re: blockcommit of domain not successfull
----- On Jun 13, 2019, at 1:08 PM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote: I found further information in /var/log/messages for both occurrences: 2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[14253]: Core Dumping has been disabled for process 30590 (qemu-system-x86). 2019-06-01T03:05:31.712673+02:00 ha-idg-2 systemd-coredump[14253]: Process 30590 (qemu-system-x86) of
2019 Jun 05
3
Re: blockcommit of domain not successfull
Hi Peter, thanks for your help. ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: >> ============================================================= >> ... >> 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor >> 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 :
2018 Mar 09
0
Re: snapshot with libvirt tools or with lvm tools ?
----- On Mar 9, 2018, at 4:39 PM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote: > Hi, > > i asked already a time ago about snapshots. I have some guests, each resides in > a raw file, placed on an ext3 fs which is on top of a logical volume, for each > guest a dedicated lv. > The raw is not a "must have", if there are obvious reasons i can convert them to
2019 Jun 05
1
Re: blockcommit of domain not successfull
----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion
2019 Jun 13
2
Re: blockcommit of domain not successfull
----- On Jun 13, 2019, at 9:56 AM, Peter Krempa pkrempa@redhat.com wrote: > > Thanks for comming back to me with the information. > > Unfortunately this is not a full debug log but I can try to tell you > what I see here: I configured libvirtd that way: ha-idg-1:~ # grep -Ev '^$|#' /etc/libvirt/libvirtd.conf log_level = 1 log_filters="1:qemu 3:remote 4:event
2015 Nov 30
1
virsh uses internally qemu-img ?
Hi, i read that virsh uses internally qemu-img (http://serverfault.com/questions/692435/qemu-img-snapshot-on-live-vm). Is that true ? so snapshotting a running vm with virsh or qemu-img is the same ? Bernd -- Bernd Lentes Systemadministration institute of developmental genetics Gebäude 35.34 - Raum 208 HelmholtzZentrum München bernd.lentes@helmholtz-muenchen.de phone: +49 (0)89 3187 1241
2019 Apr 25
1
Live Disk Backup with Active Blockcommit
Hi! I was reading the Wiki about 'Live Disk Backup with Active Blockcommit, https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit and see that example shown seems to be using two different names for the same file. First showing the current block device in use: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda
2019 Apr 03
2
is it possible to create a snapshot from a guest residing in a plain partition ?
Hi, i can store the disk of a guest in a plain partition which isn't formatted. That's no problem, i did it already several times, although the promised speed increase didn't appear. But is it possible to create from such a guest a snapshot in a .sn file using virsh ? Regards, Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum
2019 Jun 14
1
Re: blockcommit of domain not successfull
On Thu, Jun 13, 2019 at 16:01:18 +0200, Lentes, Bernd wrote: > > ----- On Jun 13, 2019, at 1:08 PM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote: > > I found further information in /var/log/messages for both occurrences: > > 2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[14253]: Core Dumping has been disabled for process 30590 (qemu-system-x86). >