Infrastructure Software

It had to happen... the day I migrate our OVM Manager from an ESX host into an Oracle VM, we have a massive NetApp outage, and everything fails to come back. As a result of having lock errors when trying to start any VMs I noted on the forum various solutions and ended up following the steps concerning stopping ovs-agent and removal of /etc/ovs-agent/db/* on all the servers. Next I re-added the repo to all the servers using repos.py, but of course now none of the servers are in a pool so the --list command shows them as [R] rather than [*], and the /OVS directory is not yet mapped. So the next stage, according to the instructions which I am following, describes using the 'Restore' option in the OVM Manager GUI. Given that /OVS is not mounted and all of the servers are now config-less, I can't see how I can start the OVM Manager VM to get to the aforementioned "restore" option...
Thank Jeebus I kept the ESX copy of OVM manager on (but powered down), as I was able to fire it up and do the restore, and now everything is hunky dory. However, this is our Dev platform and I was going to build the Prod platform and deploy OVM Manager straight into the OVM architecture via the template, rather than having it on ESX, but this issue on the Dev install has made me think twice about the mobius nature of managing the VM architecture from within the VM architecture...
I am assuming I am missing some sort of commandline knowledge, so... given:
- empty db directory
- root repos [R] on all servers
- as yet unmapped /OVS
...how to get the server pool up and get something back into /OVS, and then start my OVM Manager VM so I can 'restore'? Is it even possible? because if it isn't, I'll be blowed if the Prod OVM manager is going to get deployed like this...
And no, there's no money in the budget for extra tin just to sit there running the OVM Manager and nothing else.
TIA
Kev