<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 6 February 2017 at 13:30, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><span class=""><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 class="gmail_extra"><div class="gmail_quote"><span class="m_-2207223826498537483gmail-"><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 class="gmail_extra"><div class="gmail_quote"><span><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 class="gmail_extra"><div class="gmail_quote"><span class="m_-2207223826498537483gmail-m_9161705508979663336m_-6832179091052571113m_-7945937269453396598gmail-"><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"><ol><li>What problems can I expect to have with VMs added/modified since the last backup?</li></ol></div></blockquote></span></div></div></div></blockquote></span><div>Modified VMs will be reverted to the previous configuration; additional VMs should be seen as external VMs, then you could import.<br></div></div></div></div></blockquote><div><br></div></span><div>Given VDSM kept the VMs up whilst the HE's been down, how will the running VMs that were present before & after the backup be affected?<br></div><div><br>Many of the VMs that were present during the last backup are now on different hosts, including the HE VM. Will that cause any issues?<br></div></div></div></div></div></blockquote><div><br></div></span><div>For normal VMs I don't expect any issue: the engine will simply update the correspondent record once it will find them on the managed hosts.</div><div>A serious issue could instead happen with HA VMs:</div><div>if the engine finds earlier an HA VM as running on a different host it will simply update its record, the issue is if it finds earlier the VM a not on the original host since it will try to restart it causing a split brain and probably a VM corruption.</div><div>I opened a bug to track it:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1419649" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1419649</a><br></div><span class=""></span></div></div></div></blockquote><div><br></div><div>Ouch. *All* of our VMs are HA by default.<br><br></div><div>So the simplest current solution would be to shutdown the running VMs in VDSM, before restoring the backup & running engine-setup?<br></div></div><br clear="all"></div><div class="gmail_extra">Cheers,<br></div><div class="gmail_extra">-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Doug</div>
</div></div>