Troubleshooting

Migrating Exchange 2010 To Dell Advanced Infrastructure Manager Environment

Page 18

Migrating Exchange 2010 to AIM Environment

The Exchange 2010 solution considered in this paper consists of a two-copy DAG. We migrate one

Exchange 2010 multi-role servers one at a time in order to keep the databases available during the

migration process. Server Migration Utility (SMU) is used to copy the OS bits to the shared storage and

prepare them for net booting

Discovery of hardware components by AIM

AIM needs to identify the servers and switches in order to manage them. We discover and configure the

components in following order:

1. Discover PowerEdge M1000e modular enclosure (Needs CLI).

2. Discover chassis switches as well as top of rack (TOR) switches in read only mode.

3. Set the default channel ID for the switches (Needs CLI).

4. Configure the switchports on the chassis and TOR switches as host / unmanaged/ external /

interconnect from AIM console as needed (Needs CLI).

5. Update the switches to fully managed mode (Needs CLI).

6. Discover the Servers to be managed by AIM: This can be accomplished by simply restarting the

machine from the SMU. Ensure that a PXE boot is in progress. After a couple of minutes, the

server will shut down and the AIM console should show all the NIC‘s on the server with their

MAC addresses and channels. If all the NIC‘s have not been discovered, it may be necessary to

boot up the server in to the discovery image again.

Please refer to the CLI reference distributed with AIM documentation for detailed guide on using CLI

commands.

Migration using Server Migration Utility: Moving over to an image on SAN

The next step is to use the SMU and transition the Exchange servers, one at a time. In order to ensure

availability to end users, it is recommended that you migrate members of a DAG one at a time. For

example, in the test bed, all the copies of the database were mounted on Exchange-2 manually.

Exchange-1 was then rebooted into the SMU, moved over to the SAN on EqualLogic PS 4000X (Array 3)

first. Then the databases were mounted using the SAN image for Exchange-1. Migration of Exchange-2

was performed at this point and then the original High Availability (HA) pair configuration was

restored, with AIM managing the personas and networking. The single server migration process includes

copying the operating system image having Exchange 2010 multi-role server installed, from local disks

to SAN. Once copied, the newly copied image on the SAN needs to be prepared for network boot.

1. Boot into the SMU CD.

2. Copy the image from the local disk to the EqualLogic array

a. Advanced Operations > Mount a LUN via iSCSI connection

Enter your initiator (any string value) and target (192.168.14.50). Use the default port (3260)

3. Main Menu > Copy Windows Boot Image

a. Choose the local disk source (usually C)

b. Choose the iSCSI LUN previously created on the SAN array

Ensure that the iSCSI LUN is at least as large as the local disk‘s LUN before copying the image. Dell

recommends that you use 10k or 15k disks in your SAN for the OS images. The process to transfer the

image should take about five minutes. Reboot the machine once complete.

SMU version 3.4.3 or later should be used with AIM release 3.4.1 GA.