Hello Raul, i think the best solution is this to put engine on one site, managing both. I'd put to an external vm, not self hosted engine, for better flexibility in this kind of scenario. Once done, move a copy of the data frequently to the remote site (copy the vm via storage replication or backup/restore, or with engine-backup). Once the primary site goes down, you can recover the engine vm (start from the backup, or restore the backup with engine-restore). The database contains all the references to the managed resources, so you can connect back to the engine UI and see everything. I'd suggest also to refer to resources via DNS, so there's no issues when addressing changes. Luca On Wed, May 8, 2019 at 10:02 AM <raul.caballero.girol@gmail.com> wrote:

Hi Luca, thank you for your reply,

The idea is that the 2 sites will be up. I have read a disaster recovery guide, but I dont need a disaster recovery, I need that, when a site with my manager down, I can have visibility of the situation. And for this I need my manager. And, when I recover my site all should be running (not 2 manager or similar situation). _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UQZD5D56JBURKW...

-- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.luca@gmail.com>