Beginner here, so bear with me.
I just created an ESX server ona brand new HP Proliant. Version details are as follows:
"VMware ESX Server 3i, Version 3.5.0, Build 130755"
Now I have a crap ball physical production server running Win2k3 Enterprise Edition. This server has a few apps on it, but the main thing is SQL 2005.
I want to know if I install the VMWare VCenter Converter Standalone Client V 4 build 146302 on this server, will the server be effected in anyway? Do the static network settings carry over with the conversion? Will it maintain integrity for all services offered and users connected while the converter does it thing?
Im real nervous running this on a production system, even though tests with non production systems have been ok.
The crap ball server itself has 4 - 20 GB partitions. Would this be an issue in the conversion? Other then that, the server is pretty normal.
Thanks for all your help!
The only safe way to convert a SQL server is to shut down the SQL services during the conversion. That way noone is updating any of the databases during the conversion and you have a guaranteed clean cutover. V4 does a nice job of allowing you to do that with the wizard. You will need to verify the static network settings on the new VM once it is done converting. V3 lost all static settings, it looks like V4 is supposed to save them, but I personally haven't tried it yet. Everything should come across fine as long as you don't try to do any customizations other than basic disk resizing.
Of course, some time, either before or after conversion, you will need to get rid of all your RAID management and other hardware management tools installed on your server, etc.
I allways take my server down when converting. This way I am sure that no data corruption can occur due to updates while converting.
Especially with database servers!
-Arnim van Lieshout
If you find this information useful, please award points for "correct" or "helpful".