I have an exchange 2003 server and I need to determine what resources it uses and if my ESX host can support this server
feedback
|
|
The correct mechanism for doing this is to use VMWare's own "Guided Consolidation" approach which is a plug-in for vCenter. It monitors candidate servers for a period of days, noting max/average/min stats for CPU, memory, disk and network usage - coming up with a an overall profile and recommendations for minimum ESX/i host configuration. I couldn't recommend it higher, it was created for situations exactly like yours. | ||||
|
feedback
|
|
You can install Exchange 2003 on a ESX virtual machine with Windows Server 2003 or 2008, that should be fine. Give the Guest OS the same CPU/Memory you currently have or the server has as minimum requirements. What you need to figure out is does the hardware meet ESX requirements or not and you can find that on VMWare site. | |||
|
feedback
|
|
What resources does your current Exchange server have, what resources (total and free) do your ESX hosts have? Exchange will run happily on ESX, we do it with Exchange 2003, but on vmware as with physical hardware, if you starve it of CPU, memory or especially disk, it won't be pleasant. Do check your host on the ESX compatibility guides. | |||
|
feedback
|
it is called eyes.
You tell me. Does the ESX host have enough IO, CPU and memory to support that server? All that is quite easy to figure out. Look at CPU load, memory and IO, plus the hardware side especially of IO - you will not get a loaded 10 disc exchhane be happy with a large slow vmware store. | |||
|
feedback
|
