邮箱移动失败 - 故障排除和修复

我们必须将邮箱从 Exchange Online 移出到本地 Exchange。按照这些步骤操作后，我们最后收到邮箱移动失败的消息，并且邮箱将无法完成。为什么邮箱移动失败，解决方案是什么？让我们看看如何解决邮箱移动失败的问题。

状态详细信息瞬态失败

让我们连接到 Exchange Online PowerShell 并按照将邮箱从 Exchange Online 移动到本地的文章进行操作。但是，迁移结束时会出现错误，并且邮箱不会最终确定。

StatusDetail 显示：

• 瞬时故障

• 瞬时故障目标

PS C:\> Get-MoveRequest | Get-MoveRequestStatistics

DisplayName    StatusDetail           TotalMailboxSize           TotalArchiveSize       PercentComplete
-----------    ------------           ----------------           ----------------       ---------------
Boris Campbell TransientFailureTarget 2.279 MB (2,389,872 bytes) 3.235 KB (3,313 bytes) 100

我们确实暂停并恢复了邮箱移动请求，这在大多数情况下都有帮助。但这次没有，错误仍然存在。

那么发生了什么事，以及如何修复邮箱移动失败？让我们更好地查看移动状态详细信息。

解决邮箱移动失败问题

添加-IncludeReport 参数以返回有关邮箱移动的其他信息。将邮箱移动报告存储在 $stats 变量中。

PS C:\> $stats = Get-MoveRequestStatistics "[email protected]" -IncludeReport

获取所有移动请求失败及其计数。

PS C:\> $stats.report.Failures | group FailureType | fl


Name   : CannotEnterFinalizationTransientException
Count  : 36
Group  : {CannotEnterFinalizationTransientException: Cannot enter finalization because Data Guarantee is lagging behind by more than 00:05:00. Failure: Database b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 doesn't satisfy the constraint SecondCopy
         because the commit time 5/28/2022 9:13:28 AM isn't guaranteed by replication time 5/28/2022 9:12:54 AM.., CannotEnterFinalizationTransientException: Cannot enter finalization because Data Guarantee is lagging behind by more than
         00:05:00. Failure: Database b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 doesn't satisfy the constraint SecondCopy because the commit time 5/28/2022 9:14:02 AM isn't guaranteed by replication time 5/28/2022 9:12:54 AM..,
         CannotEnterFinalizationTransientException: Cannot enter finalization because Data Guarantee is lagging behind by more than 00:05:00. Failure: Database b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 doesn't satisfy the constraint SecondCopy because
         the commit time 5/28/2022 9:14:38 AM isn't guaranteed by replication time 5/28/2022 9:12:54 AM.., CannotEnterFinalizationTransientException: Cannot enter finalization because Data Guarantee is lagging behind by more than 00:05:00.
         Failure: Database b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 doesn't satisfy the constraint SecondCopy because the commit time 5/28/2022 9:15:12 AM isn't guaranteed by replication time 5/28/2022 9:12:54 AM.....}
Values : {CannotEnterFinalizationTransientException}

获取上次失败的完整详细信息。

PS C:\> $stats.report.Failures[0]


Timestamp         : 5/28/2022 10:19:03 AM
FailureType       : CannotEnterFinalizationTransientException
FailureHash       : 317e
FailureCode       : -2146233088
MapiLowLevelError : 0
FailureSide       :
FailureSideInt    : 0
ExceptionTypes    : {CannotEnterFinalization, MRSExpected, MRS, MRSTransient...}
ExceptionTypesInt : {632, 14, 10, 11...}
WorkItem          : CheckDataGuaranteeIfNeeded
Message           : Cannot enter finalization because Data Guarantee is lagging behind by more than 00:05:00. Failure: Database b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 doesn't satisfy the constraint SecondCopy because the commit time 5/28/2022
                    10:14:07 AM isn't guaranteed by replication time 5/28/2022 10:07:15 AM..
MessageData       :
DataContext       : --------
                    >>>> Current WorkItem: CheckDataGuaranteeIfNeeded, Scheduled WorkItems: PostContentVerificationBadItemCheck(P:0,R:-63789329909495,S:63789329909495,C:0,D:0);
                    CheckDataGuaranteeIfNeeded(P:0,R:-63789329909495,S:63789329909495,C:374,D:0); BeginJob(P:0,R:0,S:0,C:0,D:0); ConfigureProviders(P:0,R:-63789329939897,S:63789329939897,C:0,D:0);
                    BeforeConnections(P:0,R:-63789329939897,S:63789329939897,C:0,D:0); CheckTriggerRecoveryActions(P:0,R:-63789329939897,S:63789329939897,C:0,D:0); MakeConnections(P:0,R:-63789329939897,S:63789329939897,C:2016,D:0);
                    StartMove(P:0,R:-63789329941913,S:63789329941913,C:264,D:0); IncrementalSync(P:0,R:-63789329942178,S:63789329942178,C:751,D:0); PostContentVerificationBadItemCheck(P:62,R:-63789329942929,S:63789329942929,C:0,D:0)
DataContextData   :
StackTrace        :    at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CheckDataGuaranteeIfNeeded()
                       at Microsoft.Exchange.MailboxReplicationService.Job.ExecuteWorkItemCallback(WorkItem workItem)
InnerException    :
UnknownElements   :
UnknownAttributes :
XmlSchemaType     :

邮箱移动失败的解决方法

查看消息，它显示：

消息：无法进入最终确定，因为数据保证滞后超过 00:05:00。失败：数据库 b6a840a4-670e-43d7-9ecc-1d8b99e66ba4 不满足约束 SecondCopy，因为复制时间 5/28/2022 10:07 不能保证提交时间 5/28/2022 10:14:07 AM：上午 15 点..

这种情况发生在邮箱数据库 b6a840a4-670e-43d7-9ecc-1d8b99e66ba4（即 DB01）中。

验证邮箱数据库 GUID

以管理员身份运行 Exchange 命令行管理程序并确定邮箱数据库 GUID。

[PS] C:\>Get-MailboxDatabase "b6a840a4-670e-43d7-9ecc-1d8b99e66ba4" | ft -AutoSize

Name Server    Recovery ReplicationType
---- ------    -------- ---------------
DB01 EX01-2019 False    Remote

获取 DataMoveReplicationConstraint 值

DataMoveReplicationConstraint 参数指定高可用性邮箱移动的限制行为。

运行 Get-MailboxDatabase cmdlet 并获取邮箱数据库 DB01 DataMoveReplicationConstraint 值。

注意：DataMoveReplicationConstraint 值默认设置为SecondCopy。

[PS] C:\>Get-MailboxDatabase "DB01" | ft Name,Guid,DataMoveReplicationConstraint

Name Guid                                 DataMoveReplicationConstraint
---- ----                                 -----------------------------
DB01 b6a840a4-670e-43d7-9ecc-1d8b99e66ba4                    SecondCopy

将 DataMoveReplicationConstraint 设置为 None

运行 Set-MailboxDatabase cmdlet 并将邮箱数据库 DataMoveReplicationConstraint 设置为 None。

[PS] C:\>Set-MailboxDatabase "DB01" -DataMoveReplicationConstraint None

获取邮箱移动请求统计信息

稍等片刻并验证邮箱移动状态。它表明它已成功完成邮箱到本地 Exchange 的移动。

PS C:\> Get-MoveRequest | Get-MoveRequestStatistics

DisplayName    StatusDetail TotalMailboxSize           TotalArchiveSize       PercentComplete
-----------    ------------ ----------------           ----------------       ---------------
Boris Campbell Completed    2.279 MB (2,389,872 bytes) 3.235 KB (3,313 bytes) 100

将 DataMoveReplicationConstraint 设置为 SecondCopy

不要忘记将邮箱数据库上的 DataMoveReplicationConstraint 值设置回默认的 SecondCopy 值。

[PS] C:\>Set-MailboxDatabase "DB01" -DataMoveReplicationConstraint SecondCopy

了解更多：删除 Exchange Server 中的移动请求失败 »

结论

您了解了如何排除邮箱移动故障并修复它们。首先，在检索邮箱移动请求统计信息时使用 -IncludeReport 参数来获取所有详细信息。接下来，实施修复。之后，邮箱移动将成功完成。

您喜欢这篇文章吗？您可能还喜欢 Exchange 中的 New-MigrationBatch 或 New-MoveRequest。不要忘记关注我们并分享这篇文章。