Troubleshooting

Migrating Exchange 2010 To Dell Advanced Infrastructure Manager Environment
Page 8
case of failure to access an active copy of a database, one of the passive copies of the database is
activated to provide availability.
AIM‘s high availability complements Exchange DAG. As an example scenario, consider an infrastructure
which already has two Exchange 2010 mailbox servers that are in a Database Availability Group (DAG).
If one of these servers fails, the other active server can mount those database copies. The AIM
controller will then detect that there has been a failure in the managed pool and will re-target the
failed operating system image along with the application on to the stand-by server. The original
distribution of databases can then be restored on the running servers. A pool of servers can be assigned
to these personas or images on SAN. AIM can automatically restore normalcy or provide availability to
IT environments.
Exchange Sample Solution Summary
Table 2. Exchange 2010 test solution summary
1800
.15 IOPS (~160 messages/day)
512MB
2
Backup and recovery infrastructure
Disaster recovery or site resiliency
UM and Edge roles
Detail
2x PowerEdge M610 servers
2x quad-core processors and 48GB of RAM
2x PowerEdge M610 server
2x quad-core processors and 48GB of RAM
1
2
900 active + 900 passive
Details
2x EqualLogic PS6000E
16 drives each; 32 total drives
2
1
900
3.5‖ 7.2k rpm SATA 500GB
RAID 10
Databases and logs combined;
1 volume = 1 DB + 1 Log
38% estimated capacity for growth
NTFS allocation unit size = 64KB
For the above deployment, 48 GB of RAM was used across the board for non-AIM and AIM environment
test results. As explored in the results section, 20 GB per server should be sufficient.
Exchange has its own application-specific networks, namely the public/MAPI (Messaging API) network,
primarily used by Active Directory/Domain controller to communicate to the mailbox servers and a
private/replication network used for log-based synchronization of databases in the Database