Solved

Exchange 2003 on vmware ESX 3.0.2 or not ?

Posted on 2007-11-14
4
1,045 Views
Last Modified: 2008-02-25
Hi all

I have an exchange 2003 SP2 in a active/passive cluster environment.
Because we are using fiber and veritas enterprise manager to go to our san storage on netapp (which is not supported by netapp), we are planning to migrate to something else.
We have two options to do this:

Option1:
Install a new exchange 2003 cluster on new hardware and using iscsi to connect to our netapp storage. We also want to use snapdrive and snapmanager for exchange (netapp products).

Option2:
Install exchange 2003 on our vmware environment as a single server (no cluster) and use Vmotion, HA, ... to "replace" the cluster.
We have ESX 3.0.2 and connecting to our storage with NFS.


Which option would you guys prefer and why ?

Thanks,
Robin
0
Comment
Question by:Geert Bettens
4 Comments
 
LVL 6

Assisted Solution

by:AbhijeetNigam
AbhijeetNigam earned 50 total points
ID: 20279845
I would suggest option one is good keeping performance in mind. I dont recommend keeping production on virtual environment untill we have a very less number of users
0
 
LVL 1

Assisted Solution

by:ParvinderSohal
ParvinderSohal earned 50 total points
ID: 20279869
I would stick with option 1. for better performance.
0
 
LVL 21

Accepted Solution

by:
robocat earned 200 total points
ID: 20280032
This is a well kept secret, but NFS actually outperforms iSCSI on VMWare by 30% to 45% if all else is kept the same. We can testify to this.

Is some cases NFS can even outperform Fibre Channel.

There are 2 reasons for this, the elimination of the slow VMFS filesystem (replaced by WAFL) and the fact that there's no longer a single I/O queue for each datastore.

Google for keywords: netapp nfs vmware datastore
This is currently a hot topic on lots of sites.
0
 
LVL 22

Assisted Solution

by:ATIG
ATIG earned 200 total points
ID: 20280261
You can look at my blog to see who I work with.......

even if going to vmware  vmotion give the ability to move the box while running,
HA is more of failover but could take 20 minutes to kick in...

with that said  vmware is a great solution but remember MS does not 100% support virtualisation of Exchange and if you run into problem may be ask to build a physical machine.

0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question