Hi Alex,
could you share more details on your setup ? I also had issues with restoring the engine from a backup and it made me
think of running engine not a self hosted HA. I don’t have any experience with pacemaker/corrosync and drbd, but I’m willing to test and find out how to use these for the engine. I think details on your config would provide a good starting point. Of course
a working backup of any solution is necessary.
Thank you, Sven
Von: Alex McWhirter [mailto:alex@triadic.us]
Gesendet: Dienstag, 15. Januar 2019 02:19
An: maoz zadok <maozza@gmail.com>
Cc: michael@wanderingmad.com; users <users@ovirt.org>
Betreff: [ovirt-users] Re: multiple engines (active passive)
real HA is complicated, no way around that...
As stated earlier, we also run engine bare metal using pacemaker / corosync / drbd to keep both nodes in perfect sync, failover happens in a few seconds. We also do
daily backups of the engine, but in the 4 years or so that we have been running ovirt, we have luckily never had to use them with this setup. STONITH is pretty important to setup if you are running less than three nodes as the engine, just to keep split brain
from corrupting everything.
On 2019-01-14 14:16, maoz zadok wrote:
Well, I really love oVirt, but I don't know.. All the solutions mentioned here are complicated and or dangerous. Including hosted ha engine that
fails while deploying(for me). I think that test the backup for recovery is very important and need to be done on a regular basis, What good is a backup if you cannot restore?? I worked for a whole night trying to recover the failed engine...recovery from
backup was very painful. does anyone here have a solution for testing backups (not in crises mode)?
I'm still sort of new to ovirt, but I went through a similar things. I had my original engine fail and had to recover, so here is my "oVirt HA plan"
1. I do NOT use hosted ovirt, I had issues getting it deployed correctly, and that doesn't help if they engine VM itself has issues. My engine is hosted on a completely separated 2-node hyper-converged Hyper-V Cluster. Unless you have a cluster larger than
3 hosts, I really don't think hosted ovirt is a good idea, it would make more sense to just load ovirt on another PC by itself.
2. I plan on loading another copy of ovirt in a "cold storage" configuration. Where it will be loaded on centos, and configured as close as I can without adding in any hosts. I'll probably keep it turned off and try to updated it once a month or so.
3. If I have another oVirt failure, I know to log in, put the storage domains into maintenance mode if possible, and copy out any needed config items i may have missed. I will the shut it off and delete it. I then will reboot all the hosts one at a time to
clear out any sanlock issues, then add the hosts to the new copy of ovirt and import the storage. I estimate that process to take around 2-4hrs.
_______________________________________________
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/AHD3OABM65FWYMRHBFI6IHRZUE27PVWA/