Active Mailbox database move itself

Hi Team,

I have issue, suddenly my Exchange mailbox move to other passive mailbox with healthy condition, no downtime

I have Exchange 2013 Cu7 and 3 Member DAG

this is event id log when move happened

can you tell me what this event id describe?

is Exchange Server have capability to move database itself if the server is healthy?

Thanks

May 21st, 2015 11:59pm

You can use CollectOverMetrics.ps1 to determine why a database failedover to a different server.
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 4:26pm

Hi iam have a trouble when execute the command,

this error show

WriteHtmlReport : Cannot bind argument to parameter 'Data' because it is null.
At F:\Scripts\CollectOverMetrics.ps1:1493 char:31
+         WriteHtmlReport -Data $AmOperationsData -ReportPath $HtmlSummaryReportNa ...
+                               ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [WriteHtmlReport], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,WriteHtmlReport

after that HTML and CSV report go blank

Btw, is the Exchange Server 2013 have capability to move active database automatically?

Thanks

May 25th, 2015 3:42am

<title>Failover summary report</title> <style type="text/css">COLGROUP { border-width: 1px; border-style: solid; border-color: black; border-collapse: collapse; padding: 7px; } TABLE { border-width: 1px; border-style: solid; border-color: black; border-collapse: collapse; padding: 7px; } TBODY { border-width: 1px; border-style: solid; border-color: black; border-collapse: collapse; } TH { border-width: 1px; border-style: solid; border-color: black; background-color:#666699; color: white; padding:7px } TD { border-width: 1px; border-style: solid; border-color: black; background-color: #99AADD; padding: 7px } TR.Light TD { background-color: #BBCCDD; color: black; padding: 7px } TR.Dark TD { background-color: #AABBDD; color: black; padding: 7px } </style>

This is the result of the scipt

Action Type Action Trigger Action Reason Total Failures Under 30s Over 30s Lossy Mount DurationOutage Average DurationOutage Maximum DurationOutage 90th Percentile DurationOutage Quartiles DurationDismount Average DurationDismount Maximum DurationDismount 90th Percentile DurationDismount Quartiles DurationBcs Average DurationBcs Maximum DurationBcs 90th Percentile DurationBcs Quartiles DurationAcll Average DurationAcll Maximum DurationAcll 90th Percentile DurationAcll Quartiles DurationMount Average DurationMount Maximum DurationMount 90th Percentile DurationMount Quartiles DurationOther Average DurationOther Maximum DurationOther 90th Percentile DurationOther Quartiles AcllCopiedLogs Average AcllCopiedLogs Maximum AcllCopiedLogs 90th Percentile AcllCopiedLogs Quartiles ReplayedLogs Average ReplayedLogs Maximum ReplayedLogs 90th Percentile ReplayedLogs Quartiles LostLogs Average LostLogs Maximum LostLogs 90th Percentile LostLogs Quartiles LostBytes Average LostBytes Maximum LostBytes 90th Percentile LostBytes Quartiles AcllFinalReplayQueue Average AcllFinalReplayQueue Maximum AcllFinalReplayQueue 90th Percentile AcllFinalReplayQueue Quartiles
Total Total Total 1 0 0 1 0 1018451169 1018451169 1018451169 1018451169 : 1018451169 : 0 9044125 9044125 9044125 9044125 : 9044125 : 0 50383419 50383419 50383419 50383419 : 50383419 : 0 162507341 162507341 162507341 162507341 : 162507341 : 0 796057955 796057955 796057955 796057955 : 796057955 : 0 50841748 50841748 50841748 50841748 : 50841748 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0
Move Automatic FailureItem 1 0 0 1 0 1018451169 1018451169 1018451169 1018451169 : 1018451169 : 0 9044125 9044125 9044125 9044125 : 9044125 : 0 50383419 50383419 50383419 50383419 : 50383419 : 0 162507341 162507341 162507341 162507341 : 162507341 : 0 796057955 796057955 796057955 796057955 : 796057955 : 0 50841748 50841748 50841748 50841748 : 50841748 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0 0 0 0 0 : 0 : 0

No failed operations found in the data

Operations taking more than 30 seconds

To see all the operations, load the CSV files in Excel and choose "Format as table".

ActionCategory ActionInitiator ActionReason Result DurationOutage DurationDismount DurationBcs DurationAcll DurationMount DurationOther NumberOfAttempts AcllCopiedLogs LostLogs ReplayedLogs LostBytes AcllFinalReplayQueue StoreMountProgress DatabaseName TimeRecoveryStarted TimeRecoveryEnded ActiveOnStart ActiveOnFinish PAMServer BcsTimingDetails AcllTimingDetails MountRpcTimingDetails StoreMountLids EseDismountTiming EseMountTiming
Move Automatic FailureItem Success 1018451169 9044125 50383419 162507341 796057955 50841748 1 0 0 0 0 0 DB 01 25/05/2015 10:43:00 25/05/2015 10:44:42 Server A Server A Server A PMQOStET=00:00:00; PMQOExET=00:00:02.1405368; SMET=00:01:12.3159382
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2015 5:49am

Hi,

The Event 167 in your posting indicates that the Exchange Store database DBBRONZE01 copy on this server could not be reached.

If a database cant be reached, the mailbox which is located in another copy database would be mounted and connected automatically so that the client user would still connect to their mailbox without any problem. It is the High Availability for your mailbox database which is provided by DAG feature. For more information about the feature, please refer to Using a database availability group for high availability part in:

https://technet.microsoft.com/en-us/library/dd979799(v=exchg.150).aspx

Please check the status about the database DBBRONZE01 and collect more logs information about it.

Regards,

David

May 25th, 2015 6:05am

Is there any relation between CPU consume and mailbox connectivity?

because this cas happend when CPU process is peak

in my case, server availability is good, server still can be reached and ping reply

Thanks

Free Windows Admin Tool Kit Click here and download it now
May 25th, 2015 6:20am

Absolutely, if CPU is spiking and resources are being consumed (more than normal), the server is essentially in a 'hung' state. Response times will drop and communication to the database will fail/ become too slow. The DAGs PAM will move the database to a server that is healthy. Use Perfmon or ProcExplorer to determine what is causing your CPU to spike. Do you know what service is causing this spike? Do you have any third party apps installed on this machine? Does it happen at a specific time everyday? We need to trace down what/when/why this is happening.
May 26th, 2015 9:52am

Hi,

in my case, only one database move to others node.

I have 2 active database. DB01 with high traffic, and DB02 with standard traffic.

only DB01 move to others node, DB02 not move.

I think there is no CPU hung state, if the server Hung, two database will be move to other node

Thanks

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 12:18am

Hi,

Please use the below command to check the database status:

get-MailboxDatabase Status | format-table Name,StorageGroup,

Mounted,BackupInProgress,OnlineMaintenanceInProgress

if you have some related logs, please post them here for further analysis.

for more information,please refer to: https://technet.microsoft.com/en-us/magazine/dd560707.aspx    

Regards

David

June 10th, 2015 3:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics