Exchange Server Event 7024 – How to Move a Database From One Server to Another in a DAG
The DAG service terminated unexpectedly.
When an Exchange Server high availability setup is configured with multiple sites, the Exchange Database Availability Group (DAG) members may be deployed in each site. When one or more DAG members in a site fail, the databases won’t be mounted on the remaining servers. This can prevent users from accessing their data.
The DAG service on the failed server encountered a failure while trying to determine whether the other server(s) on the started mailbox servers list were still online. This means that a quorum of DAG members is not present and the DAG service was unable to form a cluster.
The failure could be due to hardware or software problems with the network adapter on the computer or in other network components. You can display the service-specific error code for this event by running sc query
The DAG service is not running.
When I try to move a mailbox database copy from one server in the DAG to another, it gives me this error: The Microsoft Exchange Replication service does not appear to be running on PassiveMailboxServer. This server may be experiencing an issue that prevents it from functioning as part of the cluster.
This is a generic event that Windows logs when the Service Control Manager can’t start or stop a service. The description in the Service_Exit_Code field provides more information about what caused the service to stop. You can also view this information at the command prompt by typing sc query service name.
To resolve the issue, remove the Exchange Server EX01-2016 from the DAG using the Remove-MailboxDatabaseCopy cmdlet. After completing the removal, verify that the column Servers with copies in the DAG Management Console doesn’t show the failed Exchange server. If you’re still experiencing the issue, try recovering the database to a healthy state using EseUtil Soft Recovery or an advanced Exchange repair tool.
The DAG service is not available.
This error occurs when you try to add or move a mailbox database copy in a DAG configuration. The error says “The Microsoft Exchange Replication service does not appear to be running on the Passive Mailbox Server.” If you’re using a DAG for high availability and site resilience, this problem can prevent you from moving your mailboxes or adding new servers.
This problem can occur if one of the Exchange Servers in your DAG fails or is taken offline for maintenance tasks like hardware installation, software upgrades and patches, etc. To resolve this issue, you can use a powerful Exchange repair tool that can quickly restore your inaccessible mailbox database to a healthy state.
Before you run the Remove-MailboxDatabaseCopy cmdlet, list all of the mailbox database copies on the failed Exchange Server EX01-2016. Then, verify that the Servers with copies column does not show this server and that the Bad copy count is zero. You can also check the database health by running the Get-MailboxDatabaseCopyStatus cmdlet and checking the state parameter.
The DAG service is not responding.
When you try to add or move a mailbox database copy in the DAG, you may encounter this error. This can happen due to corrupt or inaccessible database copies. To fix this issue, you must recover the database to a clean shutdown state using EseUtil Soft Recovery or Hard Recovery.
To do this, navigate to servers > database availability groups > Manage DAG membership. Click on the icon that is displayed next to EX01. You will then see a popup dialog box. Enter the details of your new group and click Save.
Once you have created the DAG, check that the Servers with copies column does not show the failed Exchange Server EX01-2016. Also, verify that the bad copy count is 0.
Once you have removed all of the mailbox database copies from the failed Exchange Server EX01-2016, you can proceed. This process can take some time. Once the process is complete, you can check that the Servers with copies column shows all of the DAG member servers.