<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 9, 2017 at 12:11 PM, Maton, Brett <span dir="ltr"><<a href="mailto:matonb@ltresources.co.uk" target="_blank">matonb@ltresources.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Good point<br></div><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-h5"><div><div class="gmail-m_8434921292854423827h5"><br>
</div></div>Just wanted to add that freezing activity is not only important for<br>
databases, but also for plain file systems. In order to do a consistent<br>
backup it is important to freeze the file systems before creating a live<br>
snapshot, and thaw it afterwards. oVirt does that automatically, but<br>
only if the guest agent is installed and running. So, remember to have<br>
the guest agent installed and running in the virtual machines that you<br>
plan to backup using this mechanism.<br>
</div></div><div class="gmail-m_8434921292854423827HOEnZb"><div class="gmail-m_8434921292854423827h5"><br>
<br><span class="gmail-">
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</span></div></div></blockquote></div><br></div>
</blockquote></div><br></div><div class="gmail_extra">Yes, indeed.</div><div class="gmail_extra">I forgot to write it before, but I did verify that my VM with guest agent installed had this inside its /var/log/messages file:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">Mar 9 10:49:36 T-ORACLE73 qemu-ga: info: guest-fsfreeze called</div><div class="gmail_extra">Mar 9 10:49:36 T-ORACLE73 qemu-ga: info: executing fsfreeze hook with arg 'freeze'</div><div class="gmail_extra">Mar 9 10:49:37 T-ORACLE73 qemu-ga: info: executing fsfreeze hook with arg 'thaw'</div><div class="gmail_extra"><br></div><div class="gmail_extra">Also, with vm_backup.py utility, I verified that inside the VM where the snapshotted disk was attached (c7testovn1), I got this:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 kernel: pci 0000:00:09.0: BAR 4: assigned [mem 0x40000000-0x40003fff 64bit pref]</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 kernel: pci 0000:00:09.0: BAR 1: assigned [mem 0x40004000-0x40004fff]</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 kernel: pci 0000:00:09.0: BAR 0: assigned [io 0x1000-0x103f]</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 kernel: virtio-pci 0000:00:09.0: enabling device (0000 -> 0003)</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 kernel: vdb: vdb1 vdb2</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 systemd: Starting LVM2 PV scan on device 252:18...</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 lvm: 2 logical volume(s) in volume group "mainvg" now active</div><div class="gmail_extra">Mar 9 10:49:42 c7testovn1 systemd: Started LVM2 PV scan on device 252:18.</div><div class="gmail_extra">Mar 9 10:49:44 c7testovn1 systemd: Stopping LVM2 PV scan on device 252:18...</div><div class="gmail_extra">Mar 9 10:49:44 c7testovn1 lvm: Device 252:18 not found. Cleared from lvmetad cache.</div><div class="gmail_extra">Mar 9 10:49:44 c7testovn1 systemd: Stopped LVM2 PV scan on device 252:18.</div><div><br></div><div>Gianluca</div></div><div><br></div></div></div>