<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Le 2015-10-12 09:09, Barak Korren a écrit :</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br /> <br /> What that procedure describes is backing up an existing engine,<br /> installing a new one and then restoring the backed up data into it.<br /> This was probably written to describe migration from a stand-alone<br /> engine host, not an AllInOne.<br /> Theoretically this should work for your setup, but I am not sure if<br /> the new hosted engine will be able to properly use the AllInOne node<br /> as a hypervisor (it would probably depend on the copied configuration<br /> containing enough details to allow the engine to connect to it over<br /> the network. you will probably at the very last have to shut down the<br /> existing engine before starting up the hosted engine)<br /> I would suggest doing as many backups as you can before starting, and<br /> performing the H.E. setup on a host that wasn't used by the existing<br /> engine, that way if it fails you can just shut it down and bring your<br /> old engine back up.<br /> </blockquote>
</div>
</blockquote>
<p>I got a backup running at this moment, scping /gluster/ovirt/d44ee4b0-8d36-467a-9610-c682a618b698/images/ to a third device.</p>
<p>So, once done, i'll give a shot on the node2 which is running only VDSM as Host agent.</p>
<p>Hope all will be fine !</p>
</body></html>