Anyone running Exchange 2010 on vSphere 4.1?

Looking to see if anyone has any experience running Exchange 2010 fully virtualized as we are looking to do so.

At first I didn't think it would be a big deal but as I read through the Exchange 2010 and VMware best practices guide I started to come up with some concerns, mainly: We have a NetApp backend so we can't use only VMDK's, our SnapManager for Exchange Product won't work. DAG requires Fiberchannel - ugh, is anyone using HA instead of DAG?

Did anyone use the 'building block' approach? Go with more, smaller mailbox servers?

Posted Jun 14, 2011, 3:59 PM UTC

511
eatspam88•

DAG doesn't require fiber channel. It works with anything that can be presented as local storage. I'm running it with local VMDK files.

3
Forgery•

We've been doing Exchange on VMware since VMware 2.5. We're a 300 mailbox site and we use NetApp & SnapManager for Exchange.

DAG doesn't require fiber Channel. We use iSCSI for computers in our data center and we are even doing DAG across the WAN to our DR site.

Check out the NetApp best practices instead of the VMware ones.

3
simulated_conscienceOP•

Awesome, thanks for the link - that is really helpful.

1
ReliantG•

This is how we're set up and we're substantially larger than 300 mailboxes. We're also using NFS for the guest OS.

1
remlik•

I'm running it fully virtualized on Vsphere 4.0. But we only have 100 users and a single server for all roles. Stores are on iscsi VMDK, no DAG. Windows backs up exchange to another vmdk and we use Veeam to backup the VM offsite.

2
montecas•

I've done it. Why don't you just present the VM with LUNs for the databases and logs? I create VMDKs for the OS and swap file and LUNs for the databases.

2
simulated_conscienceOP•

Because we use NetApp SnapManager for Exchange and with that product it needs to work with LUNs.

1
fleebworks•

We're running it on esx4.1. We have UCS/EMC Cellara as our hardware and it has been pretty stable. We are still in the roll out phase, though. I work infrastructure and not the exchange side. We are built for 15-20k users.

We're using RDMs due to some MS recommendations but would prefer paravirtual vmdks.

We are using DAG due to Microsoft's flapping on not supporting HA. In other words, we could not find definitive prove that the VMWorld 2010 presentations by VMWare for exchange 2010 would be supported. After investigation it boiled down to "We'll support it if you're a microsoft essential customer."

We used the building block approach (with Microsoft's wizard) and then had a freebee EMC consultant use their building block wizard, which was almost identical.

The biggest thing we did that wasn't in anyone's recommendations was to use metaluns (at the time, we had trouble finding GOOD docs) so they spanned multiple spindles on the SAN. This was a MAJOR performance increase for us.

Our exchange guru wanted to use 4 mailboxes in a DAG, but we eventually agreed on 6 MBs. The smaller VMs are easier to commit resources for and move if necessary. It also is very important if you're going to run other projects/servers on the same cluster/hosts. We saved a bunch by going smaller Mbs and spreading them out over more pieces of hardware by being able to put other things on it.

I'd be happy to answer specific questions when I have a bit more time, so I'll check back.

edit again: Link to one blog article that had us questioning VMware's advice - http://blogs.technet.com/b/exchange/archive/2010/11/09/3411471.aspx

2
simulated_conscienceOP•

Thanks for the great information. The boss has been looking at a single MB with DAG and after seeing your comment plus reading some of the literature I am leaning towards the building block approach as well.

I'll certainly follow up if I have specific questions.

1
systutorials•

Just want to add a few things to your question, I know it's a month old already but I just came across this post:

Your mailbox servers (still being on vsphere) can use the MS iscsi initiator to connect directly to a Netapp Lun. (Storage on a separate vlan) You must install snap drive and snapmanager for exchange on the mailbox servers. For mail databases that you must restore individually, you must create these on separate volumes. i.e. 1 database per volume. The Snapinfo and Logs can sit on the same volume.

DAG doesn't require fiberchannel.

If you try to use RDM's you won't be able to warm vmotion your mailbox servers between hosts, only when they're shut down.

2
simulated_conscienceOP•

Thanks for your reply.

I ended up talking to an external consultant about this and he had a pretty good solution. Install netapp snapdrive inside the virtual machine and use the ESX host igroup to connect to the lun via FCP. Since all of the ESX servers are part of the same igroup the virtual machine is able to be warm vmotioned.

1