Virtualisation is good, but don't forget, you're introducing an abstraction layer into your solution. Because of this, there is now one more layer that can go wrong. Also, you lose performance because some clock cycles are taken up by virtualisation and also house-keeping within VMWare.
Sharing a RAID1 disk for the 3 OSes wouldn't be a good idea, as you will now have 3 systems contending for the same disk reads and writes. VMs are good in test and dev environments, but I wouldn't run them on PROD environments. Until recently, I worked for IBM and they are pushing VMWare like crazy and I have seen many perculiar problems on VM machines than on physical hosts.
If you can afford a beefy physical hardware to run ESX, then just break up the budget and invest in smaller physical servers. The hardware is not expensive these days (I got myself a QuadCore with 4GB RAM - and other components - for Aus$1200 and I'm only using it to browse the Net!)
Main Topics
Browse All Topics





by: Jay_Jay70Posted on 2007-10-31 at 23:51:26ID: 20191132
i would be going a bigger server than that...the 1950 is a baby limited to 2 disks....
Take a look at vmware ESX server...this runs at a hardware level and removes the potential of OS cutting out all your servers....You can also assign hardware to each server as it views hardware as a pool, you can have them all on the same array, and just build the servers as you see fit partition wise....I am looking at a similar solution so have been researching this a lot...before you go anywhere, look at ESX