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