AnsweredAssumed Answered

Exchange 2013 NTFS Mount Points on VMware Performance Policy?

Question asked by julez on Apr 7, 2014
Latest reply on May 9, 2014 by julez

We are in the process of rolling out Exchange 2013 SP1 on Server 2012 R2 in a VMware environment.

 

The plan is to use NTFS mount points for all the database and log volumes, mainly we don't want to deal with looking at 15+ drive letters and in general is a lot cleaner.

The question really comes down to is would we be better off creating small Nimble iSCSI volumes and using those for the mount point drive letters? (seems like a waste to me).

Or should we use a small VMDK to contain the NTFS mount points? (seems cleaner to me)

 

The only real gotcha here is that the NTFS mount points will be using the Microsoft Exchange 2013 best practice of 64K allocation units where as the VMDK will of course be using the 1MB block size, both with different Nimble performance policies of course.

 

I guess the next question should be, do I use the Exchange 2010 performance policy for Exchange 2013?

Outcomes