<div dir="ltr"><div><div>Hey guys,<br></div> Just giving this a bump in the hope that someone might be able to advise...<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 dir="ltr"><div><div>Hi all,<br></div> One of our engines has had a DB failure* & it seems there was an unnoticed problem in its backup routine, meaning the last backup I've got is a couple of weeks old.<br>Luckily, VDSM has kept the underlying VMs running without any interruptions, so my objective is to get the HE back online & get the hosts & VMs back under its control with minimal downtime.<br></div><br>So, my questions are the following...<br><ol><li>What problems can I expect to have with VMs added/modified since the last backup?</li><li>As it's only the DB that's been affected, can I skip redeploying the Engine & jump straight to restoring the DB & rerunning engine-setup?</li><li>The original docs I read didn't mention that it's best to leave a host in maintenance mode before running the engine backup, so my plan is to install a new temporary host on a separate server, re-add the old hosts & then once everything's back up, remove the temporary host. Are there any faults in this plan?</li><li>When it comes to deleting the old HE VM, the docs point to a paywalled guide on redhat.com...?<br></li></ol></div></blockquote><div> To add a bit more info to 4), I'm referring to the following...<br><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Note:
If the Engine database is restored successfully, but the Engine virtual
machine appears to be Down and cannot be migrated to another
self-hosted engine host, you can enable a new Engine virtual machine and
remove the dead Engine virtual machine from the environment by
following the steps provided in
<a href="https://access.redhat.com/solutions/1517683">https://access.redhat.com/solutions/1517683</a>.<br></blockquote>Source: <a href="http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment/">http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment/</a><br><br></div><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"><div><div><div>CentOS 7<br></div><div>oVirt 4.0.4<br></div><div>Gluster 3.8<br><br></div><div>* Apparently a write somehow cleared fsync, despite not actually having been written to disk?! No idea how that happened...<br><br></div><div>Many thanks,<span class="gmail-HOEnZb"><font color="#888888"><br></font></span></div><span class="gmail-HOEnZb"><font color="#888888"><div>-- <br><div class="gmail-m_-4460158654694414927gmail_signature">Doug</div>
</div></font></span></div></div></div>
</blockquote></div><br></div><div class="gmail_extra">Cheers,<br></div><div class="gmail_extra">-- <br><div class="gmail_signature">Doug</div>
</div></div>