<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Liberation Serif">Hello Alexander,<br>
<br>
You are right. The FQDN was the culprit. Once I entered the FQDN
in /etc/hosts file, the problem got resolved.<br>
</font>
<div class="moz-cite-prefix">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<meta name="generator" content="LibreOffice 5.0.3.2 (Linux)">
<meta name="created" content="00:00:00">
<meta name="changedby" content="Anantha Raghava">
<meta name="changed" content="2016-01-05T17:20:50.677541300">
<meta name="created" content="00:00:00">
<meta name="changedby" content="Anantha Raghava">
<meta name="changed" content="2015-12-20T09:03:26.251763811">
<meta name="created" content="2015-02-21T00:00:00">
<meta name="changedby" content="Anantha Raghava">
<meta name="changed" content="2015-12-20T09:02:11.666821134">
<style type="text/css">
                @page { margin: 2cm }
                p { margin-bottom: 0.25cm; color: #000000; line-height: 120% }
                address { color: #000000 }
                a:link { so-language: zxx }</style><br>
Thanks for your guidance.<br>
<br>
By the way any document that explains what is
--restore-permissions in engine-backup process?<br>
<p>-- </p>
<p style="margin-bottom: 0cm; line-height: 100%"><font face="Times
New Roman, serif">Thanks
& Regards,</font></p>
<address style="line-height: 100%"><font face="Times New Roman,
serif">Anantha
Raghava</font></address>
<br>
On Wednesday 08 June 2016 10:28 PM, Anantha Raghava wrote:<br>
</div>
<blockquote
cite="mid:CAF_HQmV2u6cP_gJmrSjcKjUhZ=W8DTZpQCtuz9UqK739Wk_Trw@mail.gmail.com"
type="cite">
<p dir="ltr">Hi,</p>
<p dir="ltr">I will try both options tomorrow & revert back
here.</p>
<p dir="ltr">Regards,<br>
Anantha Raghava</p>
<div class="gmail_quote">On Jun 8, 2016 10:04 PM, "Alexander Wels"
<<a moz-do-not-send="true" href="mailto:awels@redhat.com">awels@redhat.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
Wednesday, June 08, 2016 08:49:16 PM Anantha Raghava wrote:<br>
> Hi,<br>
><br>
> I was able to migrate the oVirt Engine from one host to
another using<br>
> engine-backup utility. On the new host, the data is
loaded properly but<br>
> the Administration Portal is terribly slow.<br>
><br>
> It take about 2 to 3 minutes to allow me to enter user
name & password.<br>
> Once logged in, it takes hell a lot of time to show up
the data. Click<br>
> on a tab, we need to wait for a good amount of time to
see the actual<br>
> data. Even the refresh is taking time to execute although
it is set to 5<br>
> Seconds.<br>
><br>
> But if I enable old server and connect, every thing works
quickly.<br>
><br>
> Note:<br>
><br>
> 1. We do not have DNS in our environment.<br>
> 2. Engine name & even the IP is retained the same.<br>
> 3. Before migration, we stopped ovirt-engine on old
server, took the<br>
> backup, shutdown & disconnected the old server.<br>
> 4. We installed the ovirt-engine on new server, run
engine setup, noted<br>
> down the DB password, did engine-cleanup, restored the
data using<br>
> engine-backup utility and executed engine-setup again. It
did recognize<br>
> restored data and only httpd configuration was sought and
we selected<br>
> the defaults.<br>
><br>
<br>
It is highly likely 1 of 2 things:<br>
<br>
1. The entropy mentioned by Brett, however that is mostly
applicable on hosted<br>
engine as VMs don't usually have good entropy.<br>
2. The engine cannot resolve itself (which looking at your
description is the<br>
likely culprit). Since you don't have DNS, you need to add the
fqdn to<br>
/etc/hosts so it can resolve itself.<br>
<br>
> Result is terribly slow Web Console.<br>
><br>
> First, we attempted to setup ovirt-reports and later
removed it thinking<br>
> that may be slowing down the engine server. Yet the same
result.<br>
><br>
> Commands used to backup from old server: "engine-backup
--mode=backup<br>
> --file=<filename> --log=<log file name>
--provision-db"<br>
> Command used to restore on new server: "engine-backup
--mode=restore<br>
> --file=<backup-file-name>
--log=<log-file-name> --change-db-credentials<br>
> --db-host=localhost --db-user=engine --db-name=engine<br>
> --db-password=<password noted down in step 4>
--no-restore-permissions"<br>
><br>
> The command executed without any errors, resulting in a
terribly slow<br>
> web console.<br>
><br>
> Note: Without --restore-permissions, the restore fails.
Did not<br>
> understand what to give as restore permissions. Hence
used<br>
> --no-restore-permissions.<br>
><br>
> *Hardware configuration:*<br>
> *<br>
> **Old Server:* i3 Processor, 4 GB Memory, 1 Gbps NIC<br>
> *New Server :* Lenovo x3250 M5 Server with Intel Xeon
Processor, 16 GB<br>
> RAM, 2 X 1 Gbps NIC.<br>
><br>
> Just unable to understand why it is terribly slow.<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>