Testing out new vSphere 5.1 w/ VDP. Not an easy install...VCenter or VDP.
I'm also testing out starwind iSCSI.
So I made a few backups with VDP. Ran few test restores. Everything functional following great post on the disk.uuid VSS workaround here. http://www.bluemunkey.com/?p=338 (Amazing these things are being overlooked)
So made some changes to my Starwind and managed to corrupt inventory service DB on my vcenter. No working vcenter/inventory service...No restore with VDP.. .Ugh. So I tried all the tricks of rebuilding DB, reinstalling inventory service, re-registering inventory service with vcenter. No go, webclient no connection to inventory service. So I reinstalled entire vsphere suite. Inventory service remains functional following install but wont start following reboot. So reinstall everything again, no reboot. Get into VDP. Restore Vcenter backup and restore MSSQL DB. Now restored Vcenter fully functional following reboots.
Yet now following restore of vcenter from VDP...all my VDP jobs and restore points are missing. Store reads all space available. Acting like it's never been configured. What is going on?
Where does VDP get it's information on backup jobs, Backups themselves, ect?
Side note for vmware reps...Vmware loves saying..."on a single plain of glass" I hope one day ALL components of vsphere suite will report logs to your "single plain of glass" Every issue creates another. Error, followed by...now where's the log for that. Same thing on components...why VDP only web client and not viclient? Whole vCenter suite is becoming very bloated and scattered. KISS