<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="font-family:arial">On Tue, Jan 7, 2014 at 2:43 AM, Yedidyah Bar David </span><span dir="ltr" style="font-family:arial"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span><span style="font-family:arial"> wrote:</span><br>
</div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">----- Original Message -----<br>
> From: "Blaster" <<a href="mailto:Blaster@556nato.com">Blaster@556nato.com</a>><br>
> To: "Yedidyah Bar David" <<a href="mailto:didi@redhat.com">didi@redhat.com</a>><br>
> Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
</div><div class="im">> Sent: Monday, January 6, 2014 5:20:00 PM<br>
> Subject: Re: [Users] virtualized engine / port to self-hosted engine<br>
><br>
</div><div class="im">> On 1/6/2014 7:12 AM, Yedidyah Bar David wrote:<br>
> > Did you have problems with engine-backup? Or had other reasons to not<br>
> > use it? Thanks!<br>
><br>
> Can engine-backup be used to move an AIO configuration from one host to<br>
> another?<br>
<br>
</div>I didn't try that. In principle it can. Note that it will only backup/restore<br>
the engine - not local storage domains (ISO or data), VM images, etc.<br>
<br>
If you try that, please report back. Thanks!<br>
<div class="im"><br>
><br>
> I currently need to move an AIO configuration from AMD hardware to Intel<br>
> I7 hardware. The engine-backup WIKI discusses backups, but not<br>
> restores. I am a bit concerned about using engine-backup to restore an<br>
> AIO configuration to a different system as another WIKI page with<br>
> step-by-step instructions to do what engine-backup does for you,<br>
> mentions you have to do some extra steps if you are changing hostnames<br>
> as the hostname of the ovirt-engine is embedded in the database.<br>
<br>
</div>Changing the hostname is specifically not in the scope of engine-backup.<br>
<br>
Note that you do not need to have the hostname equal to the "fqdn" input<br>
during engine-setup - this last one just needs to be dns-resolvable and<br>
point to the machine intended.<br>
<br>
Also, there is another utility to do that, called ovirt-engine-rename -<br>
see this for details and implications:<br>
<br>
<a href="http://www.ovirt.org/Changing_Engine_Hostname" target="_blank">http://www.ovirt.org/Changing_Engine_Hostname</a><br>
<div class="im"><br>
><br>
> There really needs to be some work done in Ovirt on making it easier to<br>
> import existing disk images and just generally moving things around<br>
> without having to bounce off an NFS server.<br>
><br>
> Should I do a BZ on that?<br>
<br>
</div>Not sure what you mean exactly, but you are always welcome to open BZs on<br>
bugs/RFEs...<br>
<br>
Best regards,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Didi</font></span></blockquote><div><br></div><div> </div></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Sorry for going slightly off topic, but how is everyone's hosted engine deployment going? Are you restricted to NFS? </div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I tried the migration procedure last month and it worked.. but had quite a lot of issues so I ended up reverting back. I didn't open any bugs in the assumption it was in super alpha stage.</div>
<br></div></div>