We're getting ready to upgrade to ESX 3.0.2. The first step is to upgrade Virtual Center to 2.0.2. There is mention in the docs of a possible need to export the SQL database to a new database. It does not look like it applies to us.
My question (hypothetical) is this: What info is stored in the VC database? What would I lose if one "lost" my database and had to create a new one from scratch? I'm sure it would not affect running VMs but what would be the impact on a VM that was restarted after the data loss?
There's a good write up here: http://www.vmware-land.com/Vmware_Tips.html#VC6
If you lost the database, your VMs would still be running, but you would loose things like user permissions, HA/DRS setup, performance data , etc.
A VM would be able to restart after the lose of the database, but you would have to manage the VMs by connecting the VI client to the ESX host directly. If you lost the VC server completely you would be good for 14 days with licensing. Without the VC database you would loose vmotion / DRS.
There's a good write up here: http://www.vmware-land.com/Vmware_Tips.html#VC6
If you lost the database, your VMs would still be running, but you would loose things like user permissions, HA/DRS setup, performance data , etc.
A VM would be able to restart after the lose of the database, but you would have to manage the VMs by connecting the VI client to the ESX host directly. If you lost the VC server completely you would be good for 14 days with licensing. Without the VC database you would loose vmotion / DRS.
Excellent source, thanks Dave!