This content has been marked as final. Show 4 replies
I've never done this but... I'd export the schema. Drop the schema using the cascade option. Reinstall the OVM using the same options and then reimport the schema. I'd defintely test first.1 person found this helpful
Or... p2v the OVM and just make your OVM virtual. That way you can run it on anything moving forward. If I ever have to move mine.... that's probably what I will do.
I have considered virtualizing it, but just seems conflicting to virtualize the virtual manager....
I should probably not be so skeptical and just do it...
I used to a make full backup by follow Oracle VM document and reinstall a new Oracle VM 3.1.1 in different hardware (Sun and IBM), reinstall a new Oracle VM Manager with the same UUID of previous Oracle VM Manager (3.1.1) and then restore by follow Oracle VM docs is working fine.
Just to put a period on this and let anyone else who cares to know...
Was able to install the manager (using the runinstaller.sh --uuid option) without dropping the schema or having to re-import.
During the install...
Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...
Database schema 'ovs' already exists in the database
Select Number (1-2): 1
And the rest worked without issue.
Manager started up just as I left it before the hardware changeout.
Yes, I did take a full backup plus a schema export of ovs.
But I saved a step in not having to import.