Many of you who hit the SvMotion / VDS / HA problem requested the hotpatch that was available for it. Now that Update 1a has been released with a permanent fix how do you go about installing it? This is the recommended procedure:
- Backup your vCenter Database
- Uninstall the vCenter hot-patch
- Install the new version by pointing it to the database
The reason for this is that the hot-patch increased the build number, and this could possibly conflict with later versions.
And for those who have been waiting on it, the vCenter Appliance has also been update to Update 1 and now includes a vPostgress database by default instead of DB2!
Which hot fix do you mean? I only know of the scripts that were posted in your blog and the KB article. I asked out VMware TAM several times if there is a temporary fix.
Great to see the movement from DB2 to PostgreSQL, but why still the limitation 5 hosts/50 VM’s? If PostgreSQL is supported as embedded DB why is it not supported as external so you can manage larger environments with the vCenter Appliance. Create a bundle with vFabric Data Director to create adoption.
Oracle is still the only option no migration path for the current MSSQL users either.
@ralf: a hotfix was available on specific request…
@christian: just a matter of time…
I’ve to talk with our VMware TAM…
Hi Duncan,
Maybe I just missed the section but I cant seem to find the vds bug being fixed in the release info. Is that not mentioned on the u1a release or should I get more coffee?
I am running vCSA with MSSQL. It may require some additional hacks to work with U1.
http://blog.laspina.ca/ubiquitous/running-vmwares-vcsa-on-mssql
I didn’t see it right away either, but I think this might be where it is in the Release Notes:
VMware HA and Fault Tolerance
HA fails to restart a virtual machine with the error: Failed to open file /vmfs/volumes/UUID/.dvsData/ID/100 Status (bad0003)= Not found
In vCenter Server, a virtual machine remains powered off after an HA event.
The vSphere Client shows the following error:
Failed to open file /vmfs/volumes/UUID/.dvsData/ID/100 Status (bad0003)= Not found.
fdm.log displays:
Got fault while failing over vm. /vmfs/volumes/UUID/VM/VM.vmx: [N3Vim5Fault19PlatformConfigFaultE:0xecba148] (state = reconfiguring)
Note: You can manually start the virtual machine.
For more information, see KB 2013639.
This issue is resolved in this release.
I attempted to use the Install Updates feature from the web console and it has been hung on “Installing updates xxxxxxxx” for over 36 hours. Before it installed there was a reference to create a new temp disc slice for logs or DB conversion from the console which is what I did. That is growing but it is only 10GB out of 22GB in the above mentioned time. Is it possible it takes this long? The vCSA is running on a Dell R610 with 8GB of RAM and mirrored 120GB SSD drives for a 5 host VI. Would think it would complete after only a few hours. Wonder if anyone else has seen this?
It shouldn’t take that long. I suggest dropping Support a call if you are worried about the process failing,
Will do. Thanks. Is it supposed to be able to replace the DB as the update occurs. I assume that is why there is a 22GB slice created and mounted as temp space. Also I’ve now had two outside consulting firms tell me that vCSA “isn’t recommended” and to stick with Windows based vCenter. I have to admit that I had way less problems with Windows vCenter 4X compared to vCSA. When I first installed it, it filled the disk with core dumps because I didn’t have enough RAM on the R610.
I tested in my lab this morning and the fix is working. Was able to Storage vMotion some VM’s around that are on a vDS switch and HA powered them on when I killed thier host.
One thing that should be mentioned is, that this update only prevents VMs from getting affected by this bug. In other words, with this Patch vSwitch Ports are moved along with the virtual machine vmx File during Storage vMotion. It does not fix the impact, that VMs can not be restarted with missing dvSwitch Ports.
If you already have broken VMs, you have to repair them by yourself. So i would suggest to run the well known pearl or powercli script after applying the vCenter Update.