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@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@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.

Garanti sans virus. www.avast.com

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users