idiots guide to VMWare

[AZCOMIT]

My head was about to hit the pillow when I remembered I had to post a question.

Firstly apologies.  I am a VMWare noob and don't really know the first thing.

I have a situation where:

-my client has an ageing Windows 2000 server with Exhcange 5.5

-it is dying a slow death; one CPU is off line and 1 of the 3 HDD's is now dead

My best guess is that a VM is going to be a silver bullet to solve the problem.

I inherited the network some time ago.  It has a number of custom bits of software that have been configured to use Exchange.

I have been loathed to upgrade it as the new owners (my client) don't have the source code for the applications (an oversight) and while it works I don't want to change it. $ have also been an issue.

As this server is dying, my suggestion to the client is to migrate it to a VM.  The obvious advantages being: ability to migrate to different hardware, availability etc, etc, but.... I don't know the first thing about VMWare or migrating/P2V a server.

Is there an idiots guide I can follow?

I guess I need to know the steps; compatible hardware, supported guest OS's etc, etc.

My apolgies if, and I know it has, been adressed before.  I'm not in a mind to search for it at this moment and would much rather post (given the time difference in AU).

Perhaps there is a link to such an idiots guide?

Any advise much appreciated.

Cheers.

Andrew.

[kmriaz]

Hello Andrew

How many virtual servers you will be  running on one physical server. And do you plan to continnue wiht the same Windows 2000 & Ex 5.5? Honestly the answer to your question depends on this.

If you can manage to get yourself a copy of TrainSignals vSphere Training, then it will be good

First go to http://www.vmware.com/resources/compatibility/search.php and under Systems Tab you can search for a compatible server. Once you decide on the server, then you have to decide which flavor of vSphere OS you are interested in. You have 3 options

ESXi 4 Free (totally free of cost; support less features)

ESXi 4 (Slimmed down version of ESX. Most of the fuction in ESX can be handled here also. Major think it lacks is the linux shell)

ESX (Full version)

And then you need to install this as the OS. Then you can start building the VM's

Do let us know if you need more information. If  the answer is helpful please mark it helpful or correct.

Thanks

Riaz

[AZCOMIT]

Hi Riaz.

I intend only to run 1 Virtual Server on 1 Physical Server and yes, I intend to keep the same Windows 2000 Exchange 5.5 environment.  I know it is old and clunky but it is in an environment I inherited, it works and both I and the client are unwilling to upgrade.

I am guessing that ESXi Free is going to be the OS of choice.

The hardware shouldn't be an issue, my supplier will help with that. Lasty, creating VM's I assume should be straight forward, though creating a P to V will be a challenge.

Initially, I will try and locate the resource you suggested.

Thanks for helping me with the first steps.

Andrew.

[kmriaz]

Hi Andrew

The whole idea of vitualization is to use the maximum resource available on a server and thus save on the number of physical servers. In your case, you are going to run a ESXi server just for one Windows 2000 server hosting Ex 5.5. Do you think that using virtualization is justified.

For ESXi you need a 64 bit processor with atleast 2 GB RAM. But in production environment, you will have to add more RAM. Say 8 GB. And on top of that you are running a 32 bit OS with a 32 bit application. I am afraid that a lot of resource will be wasted.

Insalling ESXi & creating VM are straight forward. First get a server that is compatible with ESXi. Install ESXi. During installation you can specify the IP, Subnet etc. Connect it to the network. Once the installation is complete, go to any windows PC on the network; open ie and point it to the ip of the ESXi Server you just installed. This will open up a web interface. Login with the root & password. You can then dowload vSphere Client from there.

Once you have the vSphere Client installed on any windows PC, you can log into the vSphere client and add VM's.

I wont recommed you doing P2V unless really required. P2V takes everyhing in the physical server to the virtual which means, all good & bad in the physical server will be converted. My advice, go with a brand new installtion.

Many thanks

Riaz

[AZCOMIT]

Hi kmriaz, thanks again for your advice.

1. I located the suggested resource and am almost half way through the first disc.  I am learning lots.

2. I managed to source a second hand HDD from ebay so I have gotten the array out of a degraded state - a short reprieve until the next failure.

I read your post and, after listening to the videos, am becoming quite au fait with ESXi.

As for my client, I have already prepped them with regard to possible cost etc and have explained possible outcomes to them.  They are accepting.

With the cost of hardware these days, 8Gb of RAM will not be too expensive, and my hardware supplier can provide a whitebox (intel mobo, xeon cpu) that I am sure will meet spec, and as far as P2V goes, the environment I inherited has lots of custom software (that was not bought as part of the business) that I do not have installation source or source code for, I cannot re-install it.  I will have to take the good with the bad.  Plus moving the server to a VM gives me hardware independence.

Thanks again for your insight and advice.

[kmriaz]

You are welcome mate. Happy to note that my post helped you. All the best in your effort. Do let us know your progress.

Thanks

Riaz