REF: E14 Mailbox Role – Move Requests – Part 5
Auto Complete Mailbox Moves
MoveMailbox.ps1 provides a synchronous mailbox move management experience similar to the Move-Mailbox cmdlet provided in Exchange 2007. By default, scripts are installed at C:\Program Files\Microsoft\Exchange Server\V14\Scripts. For more information, see Move Mailboxes by Using the MoveMailbox.ps1 Script in the Shell.
Archive Mailboxes
If archive exists, then the archive gets moved with the primary mailbox because the archive and the primary mailbox must reside on the same mailbox database. You will need to factor in the size of the archive before moving the mailbox, not only for database size, but for how long the move will take to complete.
If you are moving from an Exchange 2010 server to Exchange 2003 or Exchange 2007 server, you will need to disable the archive before you can move the mailbox. For more information, see Disable a Personal Archive for a Mailbox.
Shared Mailboxes and Resource Mailboxes
In addition to the default user mailboxes, you can move shared mailboxes and resource mailboxes. A shared mailbox is a mailbox to which multiple users can log on. A resource mailbox is a mailbox that represents a type of resource, such as a conference room or video equipment. Resource mailboxes have additional properties in Active Directory that user mailboxes and shared mailboxes do not have, such as capacity.
Exchange 2003 does not support resource mailboxes. Instead, you must use shared mailboxes to represent resources. If you move a shared mailbox from Exchange 2003 to Exchange 2010 MRS creates the mailbox as a shared Exchange 2010 mailbox. After you move the mailbox to Exchange 2010, you can convert it to a resource mailbox. For more information about how to convert a shared mailbox to a resource mailbox, see Convert a Mailbox.
Mailbox Moves during Server Failures
Move requests can handle transient errors. MRS conducts checkpoints every 5 minutes to ensure that the database the mailbox being moved is still operational. If MRS finds that the target database is not operational, MRS will sleep for 30 seconds and then retry the move. If you have a failover, the move will not fail. MRS will detect a database failover, determine where the new database is now and restart the move process.
Another error condition that could occur is that the Client Access server where MRS instance is running goes down. If this happens, the move will stop, and then one of the other MRS instances will pickup and complete the move.
Blog Extended Reading
1. REF: E14 Mailbox Role – Move Requests – Part 1
2. REF: E14 Mailbox Role – Move Requests – Part 2
3. REF: E14 Mailbox Role – Move Requests – Part 3
4. REF: E14 Mailbox Role – Move Requests – Part 4
5. REF: E14 Mailbox Role – Move Requests – Part 5
More Information & Reference
1. Understanding Move Requests
Comments
Post a Comment