Home

Local Mailbox Move

%3CLINGO-SUB%20id%3D%22lingo-sub-670494%22%20slang%3D%22en-US%22%3ELocal%20Mailbox%20Move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-670494%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20are%20trying%20to%20move%20some%20local%20mailbox%20moves%20from%20one%20exchange%202016%20db%20to%20another.%20We%20can%20see%20that%20the%20move%20request%20created%2016%20hours%20back%20haven't%20started%20syncing%20and%20still%20in%20Que%20state.%26nbsp%3B%3C%2FP%3E%3CP%3Ewhen%20i%20take%20stats%20with%20-IncludeReport%20i%20get%20the%20below%20message.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESetting%20up%20ISInteg%20repair%20run%20up%20front%20for%20this%20mailbox%20since%20it's%20a%20large%20mailbox.%20%22Primary%20mailbox%20size%20%3D%2038817545084%2C%20Archive%20mailbox%20size%20%3D%200%2C%20Large%20mailbox%20size%20threshold%20config%3CBR%20%2F%3Evalue%20%3D%2010737418240%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMailbox%20size%20varies%20from%205%20GB%20to%2020%20GB%20and%20that%20should%20be%20ok%20as%20were%20doing%20maintenance%20every%20week%20and%20was%20able%20to%20move%20some%20Mailbox%26nbsp%3B%20with%2030%20GB%26nbsp%3B%20before%20this%20migration%20batch.%20Let%20us%20know%20with%20you%20suggestions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-670494%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-670955%22%20slang%3D%22en-US%22%3ERe%3A%20Local%20Mailbox%20Move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-670955%22%20slang%3D%22en-US%22%3EThe%20report%20doesn't%20mention%20other%20information%20as%20well%3F%20Sounds%20like%20the%20move%20is%20not%20picked%20up%20for%20some%20reason.%20Run%20the%20following%20to%20check%20the%20MRS%20status%3A%3CBR%20%2F%3EGet-MailboxServer%20%7C%20Test-MRSHealth%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-670973%22%20slang%3D%22en-US%22%3ERe%3A%20Local%20Mailbox%20Move%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-670973%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Michel%2C%20We%20can%20see%20the%20service%20is%20ok.%20The%20one%20which%20is%20having%20the%20Error%20is%20our%20Exchange%202010%20server%20which%20is%20only%20used%20for%20some%20restore%2F%20Our%20production%20box%20are%20ok%20.%20The%20only%20difference%20is%20that%20last%20week%20last%20week%20these%20mailboxes%20were%20moved%20from%20one%20DB%20to%20another%20and%20during%20that%20time%20move%20requests%20filled%20like%20400%20GB%20of%20log%20files%20which%20made%20the%20DB%20to%20dismount.%20We%20enabled%20circular%20logging%20and%20remove%20the%20spaces.%20Now%20the%20DB%20is%20back%20on%20track%20hence%20moving%20these%20mailboxes.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Sri_messagingguy
New Contributor

Hi All, 

we are trying to move some local mailbox moves from one exchange 2016 db to another. We can see that the move request created 16 hours back haven't started syncing and still in Que state. 

when i take stats with -IncludeReport i get the below message. 

 

Setting up ISInteg repair run up front for this mailbox since it's a large mailbox. "Primary mailbox size = 38817545084, Archive mailbox size = 0, Large mailbox size threshold config
value = 10737418240

 

Mailbox size varies from 5 GB to 20 GB and that should be ok as were doing maintenance every week and was able to move some Mailbox  with 30 GB  before this migration batch. Let us know with you suggestions. 

 

 

Regards, 

 

2 Replies
Highlighted
The report doesn't mention other information as well? Sounds like the move is not picked up for some reason. Run the following to check the MRS status:
Get-MailboxServer | Test-MRSHealth

Hello Michel, We can see the service is ok. The one which is having the Error is our Exchange 2010 server which is only used for some restore/ Our production box are ok . The only difference is that last week last week these mailboxes were moved from one DB to another and during that time move requests filled like 400 GB of log files which made the DB to dismount. We enabled circular logging and remove the spaces. Now the DB is back on track hence moving these mailboxes.

Related Conversations
AD User Migration Exchange Mailbox last
Hermulus in Exchange on
1 Replies
How to export Office 365 mailbox to PST?
alainajodi in Office 365 on
8 Replies