Re: [Users] Migrate simple configuration to self-hosted

Thanks for the careful reading. First to repeat my start point and goals: Comments inline: On 03/16/2014 04:12 AM, Yedidyah Bar David wrote: I see two demographics interested in migrating their current Ovirt deployment to self-hosted: 1 Those interested in freeing up a machine to use as another hypervisor. 2 Those (like me) interested in freeing up a machine to use for another purpose. Both groups want to free up a machine, presumably because they need more resources. So I don't think our primary How-To should involve requiring a new machine in order to migrate. I think many (like me) will find such a solution intractable. For those who have resources to spare, the current How-To seems fine, but that might not be the majority. This sounds like the most interesting approach for my needs. I like simple, and I can live with some downtime. Can you give me a complete list of things I should back up please? Also (and this gets back to my comment about the usefulness of some kind of date on pages visible to people who are not logged in) there are many pages regarding backup/restore. Is there one in particular you are thinking of/recommend? For backing up VMs I imagine it will not be sufficient for me to export my VMs to an export domain somewhere remote to host C (which I'll be scratching/reinstalling OS in order to target self-hosted). Later if I restore actual engine data, and then import my VMs, I imagine the UUIDs won't match? Or is the UUID preserved across export/import? What if I were to create a new temp NFS Storage Domain with my current oVirt, someplace other than host C, and then move my VMs to it? Then, after I set up self-hosted and restore my engine data, I could move them back and nuke my temp domain? I'm willing to be a guinea pig here, and report back what I find, if I can get a little more guidance as to avenues that might be useful to pursue. Many Thanks, Bob