I was able to move a VMware Server 2.0 (v7) vm to VMware ESX.. it was a *live* copy where I performed a Windows Volume Shadow copy of the vm files. Everything worked for the most part but because the database, Sybase ASE 15.0.3, was running when the shadow copy was made, we had corruption in one database. Restore from backup and all is good.
Now we need to get an updated license file from Sybase as the NIC mac address has changed.. You can *not* use the mac address from the VMware Server on ESX. grr.
Twenty hours for the volume shadow copy to complete plus another 12 hours to scp the files to the esx box (esx console access is sloooow). Keep in mind that the host VMware Server box was rebooting itself randomly so I really couldn’t leave it alone. Then 3 hours to convert/clone the vmdk files and 2 hours to correct the database… I’m tired.
It turned out to be an issue with allocating 3.75GB to a VM that was causing the rebooting. Dropping it to 2 GB resolved the rebooting… who knew? Nothing in Google and VMware Support wasn’t able to find anything on their side.
The opinions expressed within are the sole rantings of a raving lunatic and in no way reflect the rantings, fits, tantrums, errors, corrections, allocutions, or aimless thoughts of Sybase or its employees or of TeamSybase or ISUG. Any resemblance to reasonable thought, or any official or published opinion of Sybase, TeamSybase or ISUG is merely coincidental, and should be totally ignored.