White Papers

BP1013 Best Practices for Enhancing Microsoft Exchange Server 2010 Data Protection and Availability 51
Table 14 lists the relation between the hypervisor host and each of the virtual machines, with a brief
summary of the virtual resources allocated for each virtual machine:
Table 14 Configuration – Host and guest allocation
Host
VM
Purpose
vCPUs
Memory
Network Adapters
INFRA (M610)
DC1
Active Directory
Domain Controller
4 8GB E1000
VCENTER VMware vCenter Server 2 4GB 2x E1000
ESX1 (M710)
MBX1
Exchange Server
Mailbox Role
DAG node 1
4 48GB
2x E1000
4x VMXNET3
HUBCAS1
Exchange Server
Client Access and
HUB Transport roles 1
4 8GB E1000
ESX2 (M710)
MBX2
Exchange Server
Mailbox Role
DAG node 2
4 48GB
2x E1000
4x VMXNET3
HUBCAS2
Exchange Server
Client Access and
HUB Transport roles 2
4 8GB E1000
MGMT (M610)
LOAD
Exchange Load Generator
2
4GB
E1000
MONITOR
SAN/systems monitoring
2
4GB
2x E1000
A.3.1 ESXi Virtual Network Configuration
The networks of the ESXi hypervisor servers were configured following the guidelines listed below:
• One virtual switch aggregating all the network adapters designated for regular IP traffic, with
the default load balancing policy (‘Route based on the originating virtual switch port ID’)
o Management Network port group (VMkernel type) – all hosts
o vCenters port group (Virtual Machine type) – only for the INFRA host
o Public Network port group (Virtual Machine type) – all hosts
o Exchange Replication network port group (Virtual machine type) – only for the
ESX1/ESX2 hosts
o Each port group traffic segregated by tagged packets (VLANs)
• One virtual switch aggregating all the network adapters designated for iSCSI storage traffic,
with the default load balancing policy (‘Route based on the originating virtual switch port ID’)
o iSCSI network port group (Virtual machine type) – only for SAN attached virtual
machines