[ovirt-users] Ovirt 4.1 testing backup and restore Self-hosted Engine
Alan Griffiths
apgriffiths79 at gmail.com
Fri Aug 25 08:28:28 UTC 2017
As I recall (a few weeks ago now) it was after restore, once the host had
been registered in the Manager. However, I was testing on 4.0, so maybe the
behaviour is slightly different in 4.1.
Can you see anything in the Engine or vdsm logs as to why it won't remove
the storage? Perhaps try removing the stale HostedEngine VM ?
On 25 August 2017 at 09:14, wodel youchi <wodel.youchi at gmail.com> wrote:
> Hi and thanks,
>
> But when to remove the hosted_engine storage ? During the restore
> procedure or after ? Because after I couldn't do it, the manager refused to
> put that storage in maintenance mode.
>
> Regards
>
> Le 25 août 2017 08:49, "Alan Griffiths" <apgriffiths79 at gmail.com> a
> écrit :
>
>> As I recall from my testing. If you remove the old hosted_storage domain
>> then the new one should get automatically imported.
>>
>> On 24 August 2017 at 23:03, wodel youchi <wodel.youchi at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am testing the backup and restore procedure of the Self-hosted Engine,
>>> and I have a problem.
>>>
>>> This haw I did the test.
>>>
>>> I have two hypervisors hosted-engine. I am used iSCSI disk for the VM
>>> engine.
>>>
>>> I followed the procedure described in the Self-hosted Engine document to
>>> execute the backup, I put the first host in maintenance mode, the I create
>>> the backup and save it elsewhere.
>>>
>>> Then I've create a new iscsi disk, I reinstalled the first host with the
>>> save IP/hostname, then I followed the restore procedure to get the Manager
>>> up and running again.
>>> - hosted-engine --deploy
>>> - do not execute engine-setup, restore backup first
>>> - execute engine-setup
>>> - remove the host from the manager
>>> - synchronize the restored manger with the host
>>> - finalize deployment.
>>>
>>> all went well till this point, but I have a problem with the VM-engine,
>>> it is shown as down in the admin portal. the ovirt-ha-agent cannot retrieve
>>> the VM config from the shared storage.
>>>
>>> I think the problem, is that the hosted-engine storage domain is still
>>> pointing to the old disk of the old manager and not the new one. I don't
>>> know where is this information is stored, in the DB or in the Manager's
>>> config files, but when I click Manager hosted-engine domain, I can see the
>>> old LUN grayed and the new one (which is used by the restored Manager) is
>>> not grayed.
>>>
>>> How can I fix this?
>>>
>>> Regards.
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Garanti
>>> sans virus. www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> <#m_9177001278217562974_m_7731007781891096843_m_3883279741882476845_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170825/b6fe3daf/attachment.html>
More information about the Users
mailing list