Advice on Setting up Exchange 2013

Question

I put this in the Hyper-V forum because the questions I have are more related to overall Hyper-V config than Exchange. Since I am more familiar with VMWare, I do not know if the concept I have on Hyper-V is correct for Exchange. We have two Hyper-V hosts
connected to an EMC SAN via 10GB iSCSI. On the SAN, we created the Storage Pool and LUNs to handle the Exchange 2013 databases and Logs. The Hyper-V environment already had a CSV for the various VMs and that seems to work nicely. We created the Exchange
VMs in there as well. Now, to add the LUNs for the databases and logs, we also created CSV out of all those LUNs and then started to create virtual hard disks (.vhdx format) to fill up the LUNs. This was done through the Settings on the Exchange 2013 VMs using
a SCSI controller.
So, my question is, should the databases and LUNs be CSVs or should we do this some other way that will allow the VMs to failover and still maintain a connection to the storage. I read about Pass-Through disks and iSCSI within the VM itself, but both of
these seem to have either failover issues or performance issues. So what are my options here?
Thanks.
MCITP Exchange 2010 | MCITP Lync Server 2010 | MCTS Windows 2008

Answer 1

Yes, see the recommendations from the Exchange team.
A search immediately took me here:
Best Practices for Virtualizing & Managing Exchange 2013
<cite>download.microsoft.com/download/4/A/C/4AC32FD3-220E-45DC-AA97...</cite>
Best Practices for Virtualizing and Managing Exchange 2013 6 6 Target Audience This guide is intended for IT professionals and technical decision makers (TDMs ...
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.