Re: oVirt Open Source Backup solution?
Derek, That's risky. Just read lock the DB, create the lvm snapshot and release the lock. Otherwise you risk a transaction to be interrupted. Best Regards, Strahil NikolovOn May 13, 2019 16:47, Derek Atkins <derek@ihtfp.com> wrote:
Strahil <hunter86_bg@yahoo.com> 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.
What I do (on systems that have a running database) is to run a "flush" operation to sync the database to disk, and then from within the flush operation I create an LVM snapshot, and then I backup off the snapshot. If I'm not running a database, then I just create the snapshot directly.
Best Regards, Strahil Nikolov
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/JS6YVB3S33VYLP...
Hi, I am sorry I was unclear. Of course the long operation happens with the DB unlocked. Once the LVM snapshot is created (from within the locked environment), the lock is of course released and the backup proceeds from a db-unlocked environment. I apologize for my lack of clarity with "and then I backup off the snapshot" not making that clear. -derek On Tue, May 14, 2019 6:20 am, Strahil wrote:
Derek,
That's risky. Just read lock the DB, create the lvm snapshot and release the lock. Otherwise you risk a transaction to be interrupted.
Best Regards, Strahil NikolovOn May 13, 2019 16:47, Derek Atkins <derek@ihtfp.com> wrote:
Strahil <hunter86_bg@yahoo.com> 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.
What I do (on systems that have a running database) is to run a "flush" operation to sync the database to disk, and then from within the flush operation I create an LVM snapshot, and then I backup off the snapshot. If I'm not running a database, then I just create the snapshot directly.
Best Regards, Strahil Nikolov
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/JS6YVB3S33VYLP...
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
In such case ,you use the same approach for the VM in whole - lock + snapshot on oVirt + unlock.This way you keep OS + app backup in one place , which has it's own Pluses and Minuses. Best Regards,Strahil Nikolov В вторник, 14 май 2019 г., 6:40:56 ч. Гринуич-4, Derek Atkins <derek@ihtfp.com> написа: Hi, I am sorry I was unclear. Of course the long operation happens with the DB unlocked. Once the LVM snapshot is created (from within the locked environment), the lock is of course released and the backup proceeds from a db-unlocked environment. I apologize for my lack of clarity with "and then I backup off the snapshot" not making that clear. -derek On Tue, May 14, 2019 6:20 am, Strahil wrote:
Derek,
That's risky. Just read lock the DB, create the lvm snapshot and release the lock. Otherwise you risk a transaction to be interrupted.
Best Regards, Strahil NikolovOn May 13, 2019 16:47, Derek Atkins <derek@ihtfp.com> wrote:
Strahil <hunter86_bg@yahoo.com> 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.
What I do (on systems that have a running database) is to run a "flush" operation to sync the database to disk, and then from within the flush operation I create an LVM snapshot, and then I backup off the snapshot. If I'm not running a database, then I just create the snapshot directly.
Best Regards, Strahil Nikolov
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/JS6YVB3S33VYLP...
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
Strahil Nikolov <hunter86_bg@yahoo.com> writes:
In such case , you use the same approach for the VM in whole - lock + snapshot on oVirt + unlock. This way you keep OS + app backup in one place , which has it's own Pluses and Minuses.
Sure.... But the minus being it requires SIGNIFICANTLY more space. I've got over a dozen VMs, all running the same (pretty much) OS. If I based up the VM Snaphot there would be 12x space usage for OS files that I don't need to backup because I can recreate those from the initial repositories. Of course, this is at the expense of more time to restore from the backup. YMMV.
Best Regards, Strahil Nikolov
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On 5/14/19 2:43 PM, Derek Atkins wrote:
Strahil Nikolov <hunter86_bg@yahoo.com> writes:
In such case , you use the same approach for the VM in whole - lock + snapshot on oVirt + unlock. This way you keep OS + app backup in one place , which has it's own Pluses and Minuses. Sure.... But the minus being it requires SIGNIFICANTLY more space. I've got over a dozen VMs, all running the same (pretty much) OS. If I based up the VM Snaphot there would be 12x space usage for OS files that I don't need to backup because I can recreate those from the initial repositories. Of course, this is at the expense of more time to restore from the backup.
YMMV.
Maybe split it in 2 disks? One OS and one APP/DATA? You can then backup only one. I prefer to do this anyway as I then can just redeploy the OS and attach the second disk to get things back up and running. Regards, Jorick Astrego
Best Regards, Strahil Nikolov -derek
Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------
Jorick Astrego <jorick@netbulae.eu> writes:
Maybe split it in 2 disks? One OS and one APP/DATA? You can then backup only one.
I prefer to do this anyway as I then can just redeploy the OS and attach the second disk to get things back up and running.
Are you suggesting that /etc and /var should go onto their own disks? There is lots of configuration in /etc (which is usually in the root disk) that needs to be backed up. Also, different apps store configuration and data in different places, so saying "just put it on a second disk" can be hard. Sure, it works fine for /home -- but mysql? imapd? ... -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On 5/16/19 4:12 PM, Derek Atkins wrote:
Jorick Astrego <jorick@netbulae.eu> writes:
Maybe split it in 2 disks? One OS and one APP/DATA? You can then backup only one.
I prefer to do this anyway as I then can just redeploy the OS and attach the second disk to get things back up and running. Are you suggesting that /etc and /var should go onto their own disks? There is lots of configuration in /etc (which is usually in the root disk) that needs to be backed up.
Also, different apps store configuration and data in different places, so saying "just put it on a second disk" can be hard.
Sure, it works fine for /home -- but mysql? imapd? ...
-derek
/etc for us is mostly generated by deployment and provisioning, in production at least so that is not a problem. All changes have to go through puppet/ansible. The /var I have been putting on a seperate disk for a long time. And a lot of VM's have separate disks for /data or /home. So this combination works for us but it depends on your layout and whether you have any provisioning/config management tools an procedures running. Regards, Jorick Astrego Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------
participants (4)
-
Derek Atkins -
Jorick Astrego -
Strahil -
Strahil Nikolov