Hello VMTN Members,
first of all the facts of the implementation:
SQL 2000 SP4 englisch on Windows 2003 Std. englisch SP1 \[VM running in the VI]
VC2.0.2 build 50618 on Windows 2003 SP1 \[another one standalone VM running in the VI]
4 ESX3.0.2 build 52242
In case of migrating the SQL Server using VMotion - afterwards the Virtual Center Service is down ... al connections broken
On the other hand, in case of migration the VC VM nothing happens and all connections from VI-Clients to the VC functioning properly.
Thanks a Lot for any possilbe way to get closer to a solution
VC is very attached to it's db, if it loses connectivity even for a few seconds the service can stop. Vmotion's are not alway's 100% seamless, if the networking dropped for a few seconds and VC was writing to the db it could of shutdown. The later versions of VC handle this better, if you use 2.0.2 it shoudl try and auto-reconnect.
Thanks a Lot for your opinion - I have one customer facing troubles and the other one functions correctly... about the watchdog in VC 2.0.2 restarting VC Service every 5 minutes I red in the release notes.