Problem
You have two Exchange 2016 mailbox servers configured as a DAG and one server providing witness servers. One of the mailbox server experiences an issue and goes down so the remaining mailbox server continues to service mailbox requests and has the databases mounted. The remaining operational server is restarted and you immediately notice that the databases are not mounted after the restart:
Attempting to mount the databases with the Mount-Database command throws the following error:
[PS] C:Windowssystem32>Mount-Database contoso-edb16-01
Failed to mount database “contoso-edb16-01”. Error: An Active Manager operation failed. Error: An Active Manager operation
encountered an error. To perform this operation, the server must be a member of a database availability group, and the
database availability group must have quorum. Error: Automount consensus not reached (Reason: ConcensusUnanimity does
not allow auto mount. (IsAllNodesUp: False)). [Server: contoso-MBX16-01.contoso.NET]
+ CategoryInfo : InvalidOperation: (contoso-EDB16-01:ADObjectId) [Mount-Database], InvalidOperationException
+ FullyQualifiedErrorId : [Server=contoso-MBX16-01,RequestId=ae45aaee-8113-4908-a0fd-34e3d4a032a2,TimeStamp=17/08/2017
12:20:16] [FailureCategory=Cmdlet-InvalidOperationException] A5CACA44,Microsoft.Exchange.Management.SystemConfigu
rationTasks.MountDatabase
+ PSComputerName : contoso-mbx16-01.contoso.net
[PS] C:Windowssystem32>Get-DatabaseAvailabilityGroup
Executing the Get-DatabaseAvailabilityGroup cmdlet displays the following message:
Warning: Unable to get Primary Active Manager information due to an Active Manager call failure. Error: An Active Manager operation failed. Error: An Active Manager operation encountered and error. To perform this operation, the server must be a member of a database availability group, and the database availability group must have a quorum. Error: Automount consensus not reached (Reason: ConcensusUnanimity does not allow auto mount. (IsAllNodesUp: False)).
Executing the Get-MailboxDatabaseCopyStatus * cmdlet indicates the status of the mailbox databases in the DAG as Unknown:
Solution
The reason why the databases would not automount and manually mounting them would fail is because the DAG has Datacenter Activation Coordination (DAC) mode enabled and this forces starting DAG members to acquire permission in order to mount any mailbox databases. In the example above, the DAG is unable to achieve a quorum with the second node down and therefore the DAG isn’t started and databases would not be able to mount. If you are sure that the second node is down as in the example above, you can manually start the DAG with the cmdlet:
Start-DatabaseAvailabilityGroup -Identity <DAG NAME> -MailboxServer <MailboxServerName>
The status of the mailbox databases should now be listed from Unknown to Dismounted once the DAG has been started and issuing the Mount-Database cmdlet will now successfully mount the databases:
The following are TechNet blog posts that provide a more in depth explanation of DAG and DAC:
2 Responses
hi
executing the Start-DatabaseAvailabilityGroup command does not show a type error
> Start-DatabaseAvailabilityGroup -Identity dag-name -MailboxServer mbx-01
WARNING: The operation was not successful because an error was encountered. You may find more details in log file
"C: ExchangeSetupLogs DagTasks dagtask_2019-12-05_13-43-32.537_start-databaseavailabilitygroup.log" on "mbx-01".
You can run this command on a database availability group (DAG) only when the DatacenterActivationMode parameter for
the DAG is set to DagOnly, which is not true for DAG dag-name.
+ CategoryInfo: InvalidArgument: (:) [Start-DatabaseAvailabilityGroup], TaskCanOnlyRunOnDacException
+ FullyQualifiedErrorId: [Server = mbx-01, RequestId = 81c6422e-e7cd-4836-917e-bbd631341da1, TimeStamp = 05/12/12 2019 13: 4
3:32] [FailureCategory = Cmdlet-TaskCanOnlyRunOnDacException] 889B7C37, Microsoft.Exchange.Management.SystemConfigure
tionTasks.StartDatabaseAvailabilityGroup
+ PSComputerName: mbx-01.domain.local
how can you proceed?
is it necessary to recreate a new dag and switch the servers / db under the new one?
Hi,
Thanks for the solution. I am facing the same issue and your blog solves the issue.
I really appreciate it.