Troubleshooting

Migrating Exchange 2010 To Dell Advanced Infrastructure Manager Environment
Page 30
Summary
The paper focuses on a method to migrate Exchange 2010 SP1 to an AIM managed environment – A
brownfield scenario. It also provides guidelines to freshly deploy Exchange 2010 in a newly configured
AIM environment. It is goes without saying that once migrated, Exchange 2010 in AIM environment
should be validated to see possible impact on its performance.
From the values discussed in the Performance Analysis section, it is clear that using Exchange 2010
with AIM does not affect the performance. The disk latencies are somewhat better with AIM. There is
an increase in the passive Database Write Latency with persona is configured in trunk mode, but these
values are well within thresholds. CPU and memory utilization is also comparable between AIM and
non-AIM environments.
Conclusion
In the case of Brownfield deployment, migration should be done one Exchange Server at a time to
ensure that there is no loss of service to end users. Greenfield deployments are simpler to implement
since the AIM controller networking can be setup as desired. The AIM management console, CLI with
auto-complete and SMU are the primary tools that work together to ease migration to an AIM
environment. Exchange on AIM presents an advantage to IT departments seeking to minimize
management overhead while not compromising on performance. The primary motivation for using AIM
is to separate your OS and application from local disks and make them available to a pool of servers. If
one server fails, the OS and application are brought up on another server in the same pool.