REF: E14 Mailbox Role – Move Requests – Part 1

 

1. 提供跨 forest 的信箱遷移功能
2. 信箱資料是非同步搬移
3. 線上搬移不影響使用者存取
4. 信箱遷移記錄不存在於server 上, 而記錄於信箱上
5. Microsoft Exchange Mailbox Replication Service (MRS) - CAS 負責信箱遷移
6. 透過CAS 的MRS, 可以於ORG外進行move mailbox request
7. local mailbox move & remote mailbox move
8. 另一個文章未提到的重點, CAS role 的Loading 又加重很多

 

Cautions and Prerequisites to Moving Mailboxes
  • You can't use the Exchange System Manager or Active Directory Users and Computers to move mailboxes from Exchange 2003 to Exchange 2010.
  • You can't use the Move-Mailbox cmdlets in Exchange 2007 to move mailboxes from Exchange 2007 to Exchange 2010.
  • When you move mailboxes, the user will lose the ability to view their message tracking information.
Advantages to move requests

Move requests are a new feature in Exchange 2010. Creating a move request consists of running a series of cmdlets that perform the move request. There are multiple advantages to using move requests to perform the move:

  • Moving the mailboxes is asynchronous and is carried out by the Mailbox Replication Service.
  • Mailboxes are kept online during the asynchronous moves.
  • The mailbox's Recoverable Items are moved with the mailbox, which is available only in Exchange 2010.
  • Fast search is available upon completion. As soon as the mailbox begins to move, content indexing starts to scan the mailbox so that fast searching is available upon completion of the move.
  • You can configure throttling for each MRS instance, each mailbox database, or each mailbox server.
  • Remote mailbox moves work over the Internet by way of MSProxy. You don't need to set up a direct back-end server and active directory access between the forests.
  • Mailbox moves can be managed from anywhere within the organization.
  • Mailbox content doesn't move through an administrative machine.
  • The mailbox's move history is maintained in the mailbox.
Asynchronous Mailbox Moves

In Exchange Server 2007, when you use the Move-Mailbox to move a mailbox, the cmdlet logs into both the source database and the target database and moves the content from one mailbox to the other mailbox. While the cmdlet is running you can't close the Shell until the command completes. If you close the Shell during the move, the move will fail. The move process can take several hours to complete.

The new Move Request cmdlets can perform an asynchronous move because the cmdlets do not perform the actual move. The move is performed by the Microsoft Exchange Mailbox Replication Service (MRS), which is a new service running on all Exchange 2010 Client Access servers in your organization. The New-MoveRequest sends a request to MRS. The benefit of using the service is that it enables you to manage mailbox moves from anywhere within the organization after the move request is placed. For more information, see the Mailbox Replication Services section later in this topic.

image

Online Mailbox Moves

In an online mailbox move, the mailbox is moved while the end-users can still access their e-mail accounts and the account only locks out the user for a very brief time during the end of the process when the final synchronization occurs. Online mailbox moves are only supported between Exchange 2010 databases, and between Exchange 2007 SP2 and Exchange 2010 databases. You can perform an online mailbox move across forests or in the same forest. The process for a local mailbox move and a remote mailbox move differ and are outlined later in this topic.

image

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

image

Comments

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

Ticket: RemoteAPP certificate revocation check error