This Knowledgebase article provides information about best practices for moving or migrating mailboxes with Microsoft Exchange 2000 or 2003.
Neverfail recommends that Neverfail for Exchange be shutdown for the duration of any mailbox moves or migrations on the Neverfail Heartbeat server pair.
Minimizing the Impact of Migration
System resources, particularly CPU and disk activity can be exhausted during migration. Problems with mailbox data may be experienced during the migration. For these reasons, Microsoft recommends backing up all data prior to performing the migration.
Neverfail recommends that general Microsoft guidelines should be followed when performing migration. For further information, please see the following Microsoft Knowledge Base articles.
Following Neverfail and Microsoft's advice reduces the likelihood of having to resort to a time consuming restore in the event of a migration failure. By stopping replication between servers, pre-migrated data is preserved on the Secondary server, providing a recovery server in the event of migration failure.
Please contact Neverfail Support if you require assistance with the recovery in these circumstances.
- Start the Neverfail Heartbeat Management Client and check that the system is in-sync.
- Perform a switchover from Primary to Secondary and check the stores mount.
- Wait 15 minutes.
- Perform a switchback from Secondary to Primary.
- Shutdown Neverfail Heartbeat – leave the application running.
- Perform mailbox moves / data migration.
- Stop Exchange services and perform an off-line defrag of the mailbox stores if required.
- Start Neverfail Heartbeat on the Primary server.
- Start Heartbeat on Secondary server.
Start the Management Client and check that the Full System Check completes.
Notes: Steps 2-4 are required if you want to test the Exchange environment on the Secondary server prior to the migration.
Neverfail for Exchange