RHEV-M migration from one host to another
Hello!
Could you please to provide information: is there any possibility to migrate RHEV Manager from one host to another?
I need to migrate my RHEV Manager to another host with another IP. But I’ve not founded this solution in docs. As I know, it is needed to migrate a RHEV-M database. Is it possible to backup db on one RHEV-M and restore it on another? If it is OK, there is another problem – different IP address. Is it enough to change RHEV-M address in hypervisor’s admin panel? I haven’t a dedicated storage and use a local storage on hypervisor.
Thanks in advance!
Responses
Hello Ivan,
I don't have a complete or succint answer to your questions, but I have a few links that I think will be helpful.
First - regarding migrating RHEV-M:
http://www.redhat.com/resourcelibrary/reference-architectures/RHEV-3-Disaster-Recovery
That doc goes in to great detail explaining how the database works, how to use the API, xml files, etc...
Even though I generally have done most of my work in lab environments, I still install RHEV-M on a VM for the fundamental advantages of virtualization (encapsulation, portability, etc...)
Also - in the old 3.0 RHEV Administrator guide, you should look at Chapter 15. Backing Up and Restoring the Red Hat Enterprise Virtualization Manager... otherwise, you can check Appendix D in the 3.1 Beta Guide...
It is also possible to cluster the RHEVM hosts using Red Hat Cluster Suite (ricci and luci) which may provide some benefit for you, and there are docs out there for that also:
https://access.redhat.com/knowledge/articles/115743
Today I successfully migrated RHEV-M 3.1.2 from one machine to another.
I used backup & restore procedures as documented in:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/appe-Backups.html
Steps which worked for me:
- $ service ovirt-engine stop
- Backup RHEV-M database.
- Backup configuration files.
- Restore configuration files as described in documentation.
- Don't forget to stop ovirt-engine after rhevm-setup (documentation bug #910760)
- Use correct file permissions for file /etc/ovirt-engine/notifier/notifier.conf (documentation bug #910722)
- Restore RHEV-M database on the new host.
- Use workaround mentioned in bug #910748
- $ service ovirt-engine start
Everything worked (with three workarounds mentioned above)
Please note also comment #2 in bug #910748. There are some other steps necessary for correct database restoration!
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
