<div dir="ltr">Adding Jiri.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary <span dir="ltr"><<a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.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">Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility.</div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : <a href="tel:%2B972%20%289%29%207692306" value="+97297692306" target="_blank">+972 (9) 7692306</a>
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Tue, Jun 28, 2016 at 1:22 PM, Ricky Schneberger <span dir="ltr"><<a href="mailto:ricky@schneberger.se" target="_blank">ricky@schneberger.se</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div><div>On 2016-06-28 10:21, Yedidyah Bar David wrote:<br>
> On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger<br>
> <<a href="mailto:ricky@schneberger.se" target="_blank">ricky@schneberger.se</a>> wrote:<br>
>> On 2016-06-27 19:15, Fernando Fuentes wrote:<br>
>><br>
>> Ricky,<br>
>><br>
>> I am under the impression that the DB migration was implemented in<br>
>> release 3.6.6.<br>
>><br>
>> I might be wrong.<br>
>><br>
>> <a href="https://www.ovirt.org/release/3.6.6/" rel="noreferrer" target="_blank">https://www.ovirt.org/release/3.6.6/</a><br>
>><br>
>> What's New in 3.6.6?<br>
>> Enhancement<br>
>> oVirt Engine<br>
>><br>
>> BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from<br>
>> el6->el7.<br>
>> BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored<br>
>> on 3.6 on el7<br>
>> Feature:<br>
>><br>
>> Allow engine-backup on el7 to restore backups taken on el6.<br>
>><br>
>> Reason:<br>
>><br>
>> engine 4.0 does not support el6. Users that want to upgrade from 3.6 on<br>
>> el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6<br>
>> and restore on 4.0/el7.<br>
>><br>
>> This feature, backported from 4.0, allows to do such a migration also in<br>
>> 3.6.<br>
>><br>
>> Result:<br>
>><br>
>> Using this flow, it's possible to migrate a el6 setup to el7:<br>
>><br>
>> On the existing engine machine run:<br>
>> 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log<br>
>><br>
>> On a new el7 machine:<br>
>> 2. Install engine, including dwh if it was set up on el6.<br>
>> 3. Copy engine-3.6.bck to the el7 machine<br>
>> 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log<br>
>> --provision-db --no-restore-permissions<br>
>> 5. engine-setup<br>
>><br>
>> Check engine-backup documentation for other options, including using<br>
>> remote databases, extra grants/permissions, etc.<br>
>><br>
>><br>
>> One step forward, two backward....<br>
>><br>
>> - upgrade the old EL6 to ovirt 3.6.6<br>
>> - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log<br>
>> - install <a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm</a>, to<br>
>> have ovirt-engine 4.0.0.6.<br>
>> - yum install ovirt-engine<br>
>> - engine-backup --mode=restore --no-restore-permissions --provision-db<br>
>> --file=engine-backup.tar.gz --log=engine-backup-restore.log<br>
>><br>
>> Then I got this error...<br>
>><br>
>> "Preparing to restore:<br>
>> - Unpacking file 'engine-backup.tar.gz'<br>
>> Restoring:<br>
>> - Files<br>
>> ------------------------------------------------------------------------------<br>
>> Please note:<br>
>><br>
>> Operating system is different from the one used during backup.<br>
>> Current operating system: centos7<br>
>> Operating system at backup: centos6<br>
>><br>
>> Apache httpd configuration will not be restored.<br>
>> You will be asked about it on the next engine-setup run.<br>
>> ------------------------------------------------------------------------------<br>
>> Provisioning PostgreSQL users/databases:<br>
>> - user 'engine', database 'engine'<br>
>> Restoring:<br>
>> FATAL: Can't connect to database 'ovirt_engine_history'. Please see<br>
>> '/usr/bin/engine-backup --help'."<br>
>><br>
> The backup/restore here is just like normal ones, so for details you can read<br>
> the output of 'engine-backup --help' or [1].<br>
><br>
> In your specific case, you seem to have dwh in your backup.<br>
><br>
> To restore it, you have to either prepare a database with the same credentials<br>
> as the one used in the old machine, or, if it was automatically-provisioned by<br>
> engine-setup, you can pass the option '--provision-dwh-db' to make engine-backup<br>
> create it for you.<br>
><br>
> I think I should add an option '--provision-all-databases' or something like<br>
> that. Didn't feel very good about it so never done, and no-one asked for it...<br>
><br>
> Best regards,<br>
><br>
> [1] <a href="http://www.ovirt.org/develop/release-management/features/engine/engine-backup/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/release-management/features/engine/engine-backup/</a><br>
><br>
><br>
<br>
</div></div>#engine-backup --mode=restore --no-restore-permissions --provision-db<br>
--provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz<br>
--log=engine-backup-restore.log<br>
<br>
Success with the restore!<br>
<br>
Thanks for pointing me out. What I did was just following the<br>
documentation, right or wrong.<br>
<br>
But when I run "Engine-setup" I got stucked with<br>
<br>
"[ INFO ] Stage: Setup validation<br>
[WARNING] Less than 16384MB of memory is available<br>
[ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade<br>
from unsupported versions: 3.5<br>
[ INFO ] Stage: Clean up<br>
Log file is located at<br>
/var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log<br>
[ INFO ] Generating answer file<br>
'/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf'<br>
[ INFO ] Stage: Pre-termination<br>
[ INFO ] Stage: Termination<br>
[ ERROR ] Execution of setup failed"<br>
<br>
Seems to be something missing from an earlier db-upgrade?<br>
<div><div><br>
--<br>
Ricky Schneberger<br>
<br>
------------------------------------<br>
<br>
<br>
Use PGP to protect your own privacy!<br>
<br>
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63<br>
Key-ID: 0xB88C0B63<br>
<br>
<br>
<br>
</div></div><br></div></div><span class="">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>