Mailbox move during DAG failover is stuck

I have a DAG setup on exchagne 2010. I had several mailbox moves going, some in progress and some queued. The destination mailbox database failed over to a different server. Now the inprogress and queued moves are stuck and I cant
suspend them. Any suggestions would be great.
Thank you
At some point they should resume.
What does get-moverequeststatistics show for the status?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Mailbox move and dag members

Hello,
Exchange 2010 sp3 ru6
windows 2008R2 enterprise
I have 2 servers in HQ and 1 servers in DR site - all members of DAG
MailboxServer1
MB1 5 databases - Active node - HQ
db1 950GB
db2 200GB
db3 100GB
MailboxServer2
MB2 5 databases - passive node - HQ
db1 950GB
db2 200GB
db3 100GB
DRMailboxServer1
MB3 5 databases - passive node - DR site
db1 950GB
db2 200GB
db3 100GB
db1 is 950GB large and contains 800 mailboxes. I am planning to move users from db1 to db2 and db3, to keep db1 from growing beyong 1TB.
When I start moving users, I understand it will generate transactions logs on the active node, and the same transaction logs also gets transfeered
to db2 and db3 depending on where the mailboxes are being moved to. Is my understanding correct ?
What other impacts will this have on other members of the dag ?
What are some best practices and gotchas, I should be looking for ?
Thanks!
JOe

Hi,
Agree with Willard. Although the source server logs the record deletions, which are small, the target server must write all transferred data first to transaction logs. If you generate 10 GB of log files in one day, and keep a three-day buffer of 30 GB,
moving 50 2-GB mailboxes (100 GB) would fill your target log LUN and cause downtime. In cases such as these, you may have to allocate additional capacity for the log LUNs to accommodate your move mailbox practices.
I recommend you move a percentage of user mailboxes on a nightly or weekly basis to different databases.
Here is a related article for your reference.
http://technet.microsoft.com/en-gb/library/ee832796(v=exchg.141).aspx
Best regards,
Belinda Ma
TechNet Community Support

Mailbox Move stuck on StatusDetail Relinquished

Hi,
I am trying to do mailbox moves from Exchange 2010 SP3 to Exchange 2013 CU5. This morning they were working great for a few users with no issues. Mailboxes were about 1GB.
Now when I move a mailbox it goes into a StatusDetail of Relinguished and does not proceed past 0%
What does this status mean? Should i restart the Mailbox Replication Service? I was not sure about restarting the service as I have live users and dont want to disconnect them from their mailboxes..
Please help..

Hi,
Per my known, online mailbox moves are supported between Exchange 2010 databases and between Exchange 2007 SP3 and Exchange 2010 databases.
If you move mailbox in Exchange 2013, users can't access their mailboxes during mailbox move. I recommend you migrate mailbox off business hours.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Mailbox move stuck

Hello,
I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?
Thanks.
Memento Mori

Have increased diagnostic logging for mailbox move:
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Mailbox Move" -level high
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Service
" -level high
Getting the following exception:
2014-01-05T03:07:29.678Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5739226, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:34.732Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:35.372Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5744619, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:40.427Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:41.066Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.589772, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:[email protected]:SyncStarting:1/5/2014
1:26:13 AM::"
2014-01-05T03:07:46.136Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Error,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","MigrationJobItem.SetTransientError: job a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing, at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String
commandString, Exception ex) at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand
command, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't find a move request that corresponds to the specified identity
'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData
optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession, IConfigDataProvider
globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate
errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]",Set TransientError: Syncing:1/5/2014 2:41:56 AM:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.
--> Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.: count 10 original time 01/05/2014 02:41:56
2014-01-05T03:07:46.760Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,[email protected]","NotifyOfTransientException: at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)
at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions) at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1
ignoreExceptions) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId
subscriptionId) at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2() at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob
job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)|transient error occurred for job items:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:[email protected]:Syncing||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't
find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException:
Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID,
OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession,
IConfigDataProvider globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate
logHandler, ErrorLoggerDelegate errorHandler) at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
Memento Mori

Mailbox Move ForceOffline Parameter

Hell all,
scenario: Exchange 2013 RTM CU3, Exchange 2013 SP1 DAG
I'm trying to find a way to speed up Mailbox moves (local - from the RTM to the DAG environment) and I've pretty much exhausted all options I am aware of (MRS parameters, TCP Chimney, RSS etc.).
The one thing I haven't tried is the ForceOffline parameter, but unfortunately this switch appears to be very poorly documented.
Does anyone have any experience doing mailbox moves in "offline mode"? Does it speed up the transfer? Are the mailboxes automatically put back in "online mode" after the move?
Thx in advance!
M.

Hi,
ForceOffline forces a mailbox move to be performed in offline mode, meaning the user will have no access to email during the mailbox move. There is no official article explaining that it speeds up the migration using ForceOffline parameter. Your understanding
will be appreciated.
What's more, after finishing the migration, users will have access to email. In other words, mailboxes put back in "online mode".
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Mailbox Move Issues and Errors - Exchange 2010 to 2013

I'm trying to move mailboxes from 2010 to 2013, but I'm experiencing a lot of issues.
My move batches keep hanging (stalled) for minutes and hours on end, and I can't seem to keep them going consistently.
I have two DAG's, one for Archive boxes, and one for Primary mailboxes. Each DAG has three members with DB copies of each DB. The npdes and the clusters themselves are up and healthy. However, at random some of the DB's Content Index state will go to Failed
or SuspendedandFailed. At which point I force a catalog refresh and DB index update, and it goes to healthy.
I've created the "ContentSubmitters" AD group (and assigned it permissions), reset the Search and Host controller services on each server, and restarted the Replication service. I also deleted and recreated the Index for each DB prior to restarting
services. No dice. I've also already moved the system mailboxes over to the 2013 databases.
I'm also getting some "Transient" errors in the user move log, things like this:
Transient error ResourceUnhealthyException has occurred. The system will retry"
5/4/2014 8:43:55 AM [exmb1] The job encountered too many transient failures (60) and is quitting.
5/4/2014 8:43:55 AM [exmb1] Fatal error ResourceUnhealthyException has occurred.
Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The store ID provided isn‎'t an ID of an item. --> MapiExceptionNetworkError: Unable to open entry ID. ‎(hr=0x80040115, ec=0)‎ Diagnostic context: Lid: 45025 Lid: 45345 StoreEc: 0x80040115 Lid: 22894 Lid: 24942 StoreEc: 0x80040115
Any ideas would be appreciated!!!

Hi
I would suggest you to run the below command for this "My move batches keep hanging (stalled) for minutes and hours on end" issue and see the result
Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report
Just check if the MRS health is fine by running the below command
Test-MRSHealth -Identity "CAS Server" -MonitoringContext $true | Export-CliXml "C:\temp\CAS_MRSHealth.xml" and look at the xml file to get more information
When I run the Test command against either of my CAS servers, I get: " 'EXCH1' does not have the right Exchange Server version or role required to support this operation."
Run i run that command against any of the mailbox servers, it completes and generates the XML file, but I'm not sure what I need to be looking for within that file.
The first command spits out a ton of data, here's a little excerpt:
5/5/2014 8:59:28 AM [exmb1] Transient error ResourceUnhealthyException has occurred. The system will retry
(2/60).
5/5/2014 9:00:02 AM [exmb1] The Microsoft Exchange Mailbox Replication service 'exmb1.contoso.com'
(15.0.847.31 caps:03FF) is examining the request.
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'newmbi', Mailbox server 'Exmb1.contoso.com' Version 15.0 (Build 847.0).
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'newarci', Mailbox server 'EXARC2.contoso.com' Version 15.0 (Build 847.0), proxy server
'EXARC2.contoso.com' 15.0.847.31 caps:1FFFCB07FFFF.
5/5/2014 9:00:07 AM [exmb1] Connected to source mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'exmbi', Mailbox server 'Chsexmb2.contoso.com' Version 14.3 (Build 181.0).
5/5/2014 9:00:08 AM [exmb1] Connected to source mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'Exarci', Mailbox server 'CHSEXARC1.contoso.com' Version 14.3 (Build 181.0)
5/5/2014 9:00:12 AM [exmb1] Request processing continued, stage LoadingMessages.
5/5/2014 9:00:36 AM [exmb1] Messages have been enumerated successfully. 6657 items loaded. Total size:
332.3 MB (348,411,982 bytes).5/5/2014 9:06:14 AM [exmb1] The long-running job has been temporarily postponed. It will be picked up
again when resources become available.

Exchange 2010 DAG Failover does not works

Hi Experts,
I have a Exchange 2010 setup in a DAG environment. We have 2 MBX servers in the main site and 1 MBX server in the DR site , all part of one DAG. We have 2 HUB/CAS servers in the main site and 1 HUB/CAS server in the DR site.
Recently we had to do our BCP test for audit purpose. We had issues in doing failover to the DR site and below is the error faced.
Please advise urgently on the possible causes and resolution steps for it as we need to do this test again on the coming weekend.
"EvictDagClusterNode got exception Microsoft.Exchange.Cluster.Replay.AmClusterEvictWithoutCleanupException: An Active Manager operation failed. Error An error
occurred while attempting a cluster operation. Error: Evict node 'sme-ho-mbx01' returned without the node being fully cleaned up. Please run cluster.exe node <NodeName> /forcecleanup to complete clean up for this node.. ---> System.ComponentModel.Win32Exception:
The wait operation timed out"
So, basically one of the MBX server was not evicting from the Cluster due to which failover did not work.
Would appreciate some urgent thoughts for the possible resolution.
regards
abubakar
Md.Abubakar Noorani IT Systems Engineer Serco Ltd.

Hi,
Yes, you can run the Stop-DatabaseAvailabilityGroup without shutting down the Mailbox server. During the process of DAG failover to DR site, the Stop-DatabaseAvailabilityGroup cmdlet should be run against all servers in the primary datacenter. If the Mailbox
server is unavailable but Active Directory is operating in the primary datacenter, the Stop-DatabaseAvailabilityGroup command with the ConfigurationOnly parameter must be run against all servers in this state in the primary datacenter.
And please note that the Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly.
Based on the error message, it seems that you should run the cluster node nodename /forcecleanup cmdlet against the specified node in the main site. Have you tried this to check the result?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 mailbox moves get stalled

I am Experiencing an issue with Exchange 2010 SP3 UR2 two node DAG environment (server01 and server02). While moving mailboxes from old Exchange 2007 environment I get following errors.
Move for mailbox xxxxxxxxxxxx is stalled because DataMoveReplicationConstraint is not satisfied for the database 'MDB01' (agent MailboxDatabaseReplication). Failure Reason: Database does not satisfy constraint SecondCopy. Throttling completion as database copies
are falling behind.
Get-MailboxDatabaseCopyStatus informs me that server02 Copy and ReplayQueue length on the passive copy are getting big (from 10-500) while moving and the throttling will always pause the move for a while and then start again until it stops again because the
second copy is falling behind. This only happens when I move mailboxes to databases that have active copy of the database on my server01 and passive on server 02. If the active copy is moved to server02 and server01 is the passive copy this does not happen.
So this leads to a conclusion that there is something wrong with server02 replication from server01.
I've traced the replication network and there are no issues. What could be the reason that only the second node suffers from falling back during moves? I would not like to se the datamovereplicationconstraint value to none since this is the only Exhchange
2010 DAG environment where I am facing this issue and the replication should keep up while mailbox moves.

Hello,
" I would not like to see the datamovereplicationconstraint value to none". Do you mean you set
DataMoveReplicationConstraint to SecondCopy? If so, I recommend you use test-replicationhealth cmdlet to check all aspects of the replication and replay status.
Please check if you
configure a lagged database copy.
Please check if there is a witness server, and whether the witness is online.
If not, please set DataMoveReplicationConstraint to SecondCopy.
Besides, please check if there is any error in application log.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2010 - 2013 Mailbox move - Syncing with no progress (Stalled?)

I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move,
and some mailboxes did not move successfully.
I have since added additional space but can't seem to get the remaining mailboxes to sync.
I have tried :
Rebooting
Clearing out migration batches and recreating
Stopping and resuming batches.
I see nothing helpful in the Migration log files.
2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17
2:59:12 PM::"
When I download the report for one of the users I see this, but don't know what it means :
The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'
For one of the other users the downloaded report only shows :
2013-05-16
2:11:18 PM '' created move request.
DWW
Additional Info: I followed the info located here in regards to creating the ContentSubmitters group:
http://www.bullspit.co.uk/2013/04/08/exchange-2013-content-indexing-during-migration/
My mailbox database currently has Content index state: FailedAndSuspended
I only have one database, I am not using DAG

I had already created the contentsubmitters and it helped with the speed of the mailbox moves. We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013. If I had it to do over, maybe it would have been better
to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server. But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database. Everything
was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up. Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't
right. I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes. But from then on, nothing is being received and if you send,
it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue. I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one
lesson - I will read the planning and preparations documentation thoroughly from now on.
Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:
Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.
If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I. Not that I have taken the path of the Samurai network admin or anything....
And if you were able to fix it, I am impressed and would love to know how you fixed this.
Thanks and best,
Sam

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Multiple eventlog errors after mailbox-move to Exchange SP1

After a mailbox move completes on a Exchange 2013 SP1 server, multiple errors are logged in the eventlog. I opened a ticket with MS Support and they confirm this is a bug in SP1, but the moves itself aren't affected. They state the errors can be ignored.
About 10 error per move are being logged.
These are the errors occurring after completion of a mailbox move:
Event 1003:
An asynchronous Microsoft Exchange Server Information Store task has not handled an Exception gracefully. Exception text is (Microsoft.Exchange.Server.Storage.Common.StoreException: ErrorCode: NotSupported, LID: 43296 - Invalid counter range allocation at
this time.
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)).
Event 1050:
Global counter allocation in mailbox 3add23e8-7a32-4fb5-bc32-f5b1eae7f98c on database 0afbb5dc-b967-4ebd-acb0-15f85b8bad53 by source MailboxTask during operation 28 on call stack at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context
context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64&
globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, MailboxTaskQueue mailboxTaskQueue, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.Common.Task`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.SingleExecutionTask`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.Task`1.<Worker>b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)
at Microsoft.Exchange.Server.Storage.Common.WatsonOnUnhandledException.Guard(IExecutionDiagnostics executionDiagnostics, TryDelegate body)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
is temporary not allowed.

Here's the technical descpription from MS support:
Description of problem: “During the mailbox move finalization stage the Store move is finalized followed by MRS move. In this state MRS executes MRS specific functionality. The state might take
a pretty long time in some cases. During this state the destination mailbox cannot be changed. The defensive code on the global counters depicts that the task with task ID 28: TaskTypeId.PropertyPromotionBootstrap is trying to allocate new global counter values
as seen in the event below.”
This is not a critical issue, and the production team also suggest safely ignore this warning, also they are now making progress to fix this issue, hoping to release the solution in the next CU or SP.
Frank.

Exchange server 2010 DAG failover

Hi team ,
We have configured exchange server 2010 in DAG environment .
We have added 3 mailbox server in DAG . but my active mailbox copy failed the database are failover to another passive copy server & status is mounted . after failover emails service are not working.
Note : We have also configured NLB on CAS server .All exchange servers placed in single AD site
Please suggest

Hi
So are all your exchange servers the same? settings?
have you tried to fail the DB back to its original server? all services started on the other server?

Should cancelled mailbox moves result in any moved mail data removed from target server?

I was moving mailboxes from 1 DB to another. 3 out of 120 were left running for 12 hours; they were the biggest ones and it was very slow to process the items. There were also reports of slowness on the server so I had no choice but to cancel the moves.
My question is should cancelled mailbox moves result in any moved mail data being removed from the target database? It doesn't appear that my disk as increased in space again so I'm wondering if it's there as whitespace maybe? There is an event logged to say
the mailbox has been deleted from the target.
Would appreciate if someone can clear this up and possibly explain exactly what occurs during this type of scenario.
Thanks.

Hi,
Thank you for your kindly remind.
In Exchange 2000, 2003 and 2007 mailboxes become unavailable during movement, when a mailbox move takes place, the mailbox isn't actually moved, it's just copied to the destination location. Once that copy has finished, AD is updated to point to the new location
and the old mailbox is deleted from the source EDB file.
The most different between Exchange 2010 and legacy version in move mailbox is that allows end-users to be online in their email accounts. On completing the move users just needs to reopen their Outlook clients.
Mailbox Move Requests are a new feature set of Exchange 2010 and requires running a series of Cmdlets to perform asynchronous online mailbox moves with the help of a service agent called Mailbox Replication Service (MRS). MRS is available on all Exchange 2010
Client Access Servers.
Best Regards,
Allen Wang

Mailbox move requests remain in Queued status

My server is part of a two member DAG. DAG shows to be healthy. I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
Server is Exchange 2010 SP 3

Hi,
Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
check.
Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
Best Regards.

Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

Hello,
I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
Exchange 2010 has 2 databases:
1. Database with users mailboxes;    Journaling YES: Journal account.
2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
Exchange 2013 has 1 database:
1. Database with moved users mailboxes;    Journaling YES: Journal account.
I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
I'd like:
* to understand technically what happened,
* to avoid unnecessary growth of Journal Database.
I'd like not to switch off journaling for all users during mailbox move.
best regards Janusz Such

Hello Winnie,
your understanding is not correct:
I move mailboxes from first DATABASE which is journaled;
second database is dedicated solely for Journal user's mailbox and is not touched now.
Thank you for PS commands; I'll use them...
best regards Janusz Such
Hi Janusz,
Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
Journal rule instead of database journal as a workaround.
Regards,
Winnie Liang
TechNet Community Support

Mailbox move during DAG failover is stuck

Similar Messages

Maybe you are looking for