Specifications

Best Practices for Virtualizing and Managing Exchange 2013
29
29
Figure 17: Faster SAN-attached virtual machine migrations with ODX
Best Practices and Recommendations
If you are using SAS or FC in all clustered servers, all elements of the storage stack should be
identical. It is required that the MPIO and DSM software be identical. It is recommended that the
mass storage device controllers (that is, the HBA, HBA drivers, and HBA firmware attached to
cluster storage) be identical.
25
If you are using iSCSI, each clustered server should have a minimum of two network adapters or
iSCSI HBAs that are dedicated to the cluster storage. The network being used for iSCSI should not
be used for network communication. In all clustered servers, the network adapters being used to
connect to the iSCSI storage target should be identical, and we recommend that you use Gigabit
Ethernet or higher. Network adapter teaming (also called load balancing and failover, or LBFO) is
not supported for iSCSI. MPIO software should be used instead.
ODX is enabled by default, but check with your storage vendor for support, as upgraded firmware
may be required.
Networking Considerations
Networking in a virtualized Exchange environment is a critical component for managing traffic in an
optimal way. The appropriately architected network seamlessly routes people to their mailboxes while
maintaining a consistent end-user experience. Network performance and availability are essential for
mission-critical applications like Exchange 2013.
Windows Server 2008 R2 introduced several networking-related features that help to reduce networking
complexity while simplifying management tasks. Windows Server 2012 improves on this functionality in
several ways, including new and enhanced features for NIC Teaming, the Hyper-V Extensible Switch,
virtual LANs (VLANs), and Virtual Machine Queue (VMQ).