<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Hello oVirt Padawan,</div><div class="gmail_default" style="font-family:monospace,monospace">You can install new engine machine and import existing storage domains there. <a href="https://www.ovirt.org/develop/release-management/features/storage/importstoragedomain/">https://www.ovirt.org/develop/release-management/features/storage/importstoragedomain/</a> Please read restrictions and limitations.</div><div class="gmail_default" style="font-family:monospace,monospace">I think it's more safe way to go in such kind of situations.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 4, 2017 at 6:40 PM, Rogério Ceni Coelho <span dir="ltr"><<a href="mailto:rogeriocenicoelho@gmail.com" target="_blank">rogeriocenicoelho@gmail.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">Hi oVirt ObiWan´s,<div><br></div><div>Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-(</div><div><br></div><div>I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME).</div><div><br></div><div>After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production.</div><div><br></div><div>I think the right steps are :</div><div><br></div><div>1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.<wbr>`date +%d%m%Y.%H%M%S`.ovirt-engine.<wbr>bkp --log=/tmp/ovirt-engine_<wbr>backup.log</div><div>2. Shutdown ovirt engine vm.</div><div>3. Make new checkpoint to rollback with something goes wrong</div><div>4. Rollback to checkpoint witch 4.0.4</div><div>5. Restore engine-backup (from version 4.0.5)</div><div>6. Start everything and check if all are ok</div><div><br></div><div>This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ???</div><div>This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ???</div><div><br></div><div>Thanks in advance.</div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr">Pavel Zhukov</div><div dir="ltr">Software Engineer</div><div dir="ltr">RHEV Devops</div><div dir="ltr">IRC: landgraf</div><div><br></div></div></div></div></div>
</div>