Another option is to create a snapshot, backup the snapahot and merge the disks (delete the snapshot actually). Sadly that option doesn't work with Databases, as you might inyerrupt a transaction and leave the DB in inconsistent state.

Best Regards, Strahil Nikolov

On Mon, May 13, 2019 at 3:47 PM Derek Atkins <derek(a)ihtfp.com&gt; wrote: > Strahil <hunter86_bg(a)yahoo.com&gt; writes: > > > Another option is to create a snapshot, backup the snapahot and merge > > the disks (delete the snapshot actually). > > Sadly that option doesn't work with Databases, as you might inyerrupt > > a transaction and leave the DB in inconsistent state. > > Yet another reason to do it from inside the VM. > Actually doable, depending on DB architecture and if some "logging/archiviing" supported/enabled on database. See here related threads where I was involved: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LJFQOLIWU22... and here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/J65N7E2PY3KW... When you install qemu-guest-agent (in my case version 0.12.1.2-2.506.el6_10.1) you also get an example for MySQL in /usr/share/qemu-kvm/qemu-ga/fsfreeze-hook.d/mysql-flush.sh.sample and eventually updated code (actually I see it is dated 2013...) here: https://github.com/guillon/qemu-plugins/blob/master/scripts/qemu-guest-ag... In case of PostgreSQL you would need to have WAL enabled and do an Exclusive Low Level Backup, because the pre-snapshot and post-snapshot could not be inside the same RDBMS session connection: https://www.postgresql.org/docs/10/continuous-archiving.html#BACKUP-BASE-... so the freeze option of your freeze-hook script would contain a call to a connection that runs SELECT pg_start_backup('label', true); to minimize time to do checkpoint and the thaw option would contain SELECT pg_stop_backup(); This needs also that archives during the elapsed of backup (and the last generaed when stopping backup) are copied in some way externally in respect of the VM OS for complete recoverability, if you don't already have it for your standard archiving policy. And thoroughly test the whole workflow, both backups and restores, especially when upgrading your software layers, oVirt, VM OS, PostgreSQL.... HIH, Gianluca _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2RAVXSCEPPC...

I've been using oVirtBackup in the past few years and also I've done more restores from this backup than I'd have liked. All restores were successful. I'm pretty happy with this script: https://github.com/wefixit-AT/oVirtBackup Well documented, easy to install and configure. In summary the script uses the API to take a snapshot, convert it to a VM, export the VM, remove the snapshot. It also removes old backups, checks for free storage space, and so on. It's basically set and forget. I just wrote my own little bash wrapper that will grab the output of the script and email it to me. Hope this helps, -- Peter On Mon, May 13, 2019 at 8:12 AM Jayme <jaymef(a)gmail.com&gt; wrote: > I know that a robust API is provided for performing VM backup functions, > but it seems crazy to me that oVirt has not implemented a simple method to > backup VM to a storage domain such as an NFS export domain. Is this > functionality being left out for a reason (perhaps not wanting to step on > toes of 3rd party software vendors providing backup solutions for > oVirt/RHEV)? > > On Mon, May 13, 2019 at 11:21 AM Gianluca Cecchi < > gianluca.cecchi(a)gmail.com&gt; wrote: > >> On Mon, May 13, 2019 at 3:47 PM Derek Atkins <derek(a)ihtfp.com&gt; wrote: >> >>> Strahil <hunter86_bg(a)yahoo.com&gt; writes: >>> >>> > Another option is to create a snapshot, backup the snapahot and merge >>> > the disks (delete the snapshot actually). >>> > Sadly that option doesn't work with Databases, as you might inyerrupt >>> > a transaction and leave the DB in inconsistent state. >>> >>> Yet another reason to do it from inside the VM. >>> >> >> Actually doable, depending on DB architecture and if some >> "logging/archiviing" supported/enabled on database. >> See here related threads where I was involved: >> >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LJFQOLIWU22... >> and here: >> >> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/J65N7E2PY3KW... >> >> When you install qemu-guest-agent (in my case >> version 0.12.1.2-2.506.el6_10.1) you also get an example for MySQL in >> /usr/share/qemu-kvm/qemu-ga/fsfreeze-hook.d/mysql-flush.sh.sample >> and eventually updated code (actually I see it is dated 2013...) here: >> >> https://github.com/guillon/qemu-plugins/blob/master/scripts/qemu-guest-ag... >> >> In case of PostgreSQL you would need to have WAL enabled and do an >> Exclusive Low Level Backup, because the pre-snapshot and post-snapshot >> could not be inside the same RDBMS session connection: >> >> https://www.postgresql.org/docs/10/continuous-archiving.html#BACKUP-BASE-... >> >> so the freeze option of your freeze-hook script would contain a call to >> a connection that runs >> SELECT pg_start_backup('label', true); >> to minimize time to do checkpoint >> >> and the thaw option would contain >> SELECT pg_stop_backup(); >> >> This needs also that archives during the elapsed of backup (and the last >> generaed when stopping backup) are copied in some way externally in respect >> of the VM OS for complete recoverability, if you don't already have it for >> your standard archiving policy. >> >> And thoroughly test the whole workflow, both backups and restores, >> especially when upgrading your software layers, oVirt, VM OS, PostgreSQL.... >> >> HIH, >> Gianluca >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2RAVXSCEPPC... >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/7DVSYQLZ6DG... >