How to Fix the Error “Database Redundancy Two-Copy Health Check Failed” In Exchange 2013? Get Solution
Summary: This write-up provides the solution to fix the error “database redundancy two-copy health check failed” in Exchange 2013.
To setup the Exchange Server 2013, user must have to configure the DAG (Database Availability Group) and Exchange database mailbox copies. For this, firstly you have to make sure that you should meet all the requirements which are present in Exchange 2013 Server Standard or Enterprise edition such as: how many mailbox databases you will have and the Exchange Services hosted by two or more servers must have the same OS level that is the Exchange 2013 standard or enterprise edition should be updated with the same patches.
Every Database Availability Group (DAG) must have a dedicated network for Messaging Application Programming Interface (MAPI) & another for the replication network. Exchange Server requires a minimum of two networks and can support more networks than this. You have to cater the hardware as well as the bandwidth between the sites depending on the email flow and no. of users.
When you don’t meet the requirement and move forward to complete the setup, then you may have to face the issues such as: your Exchange database health issue or replication. You will see such issues with the error – redundancy health check failing on the Microsoft Exchange 2013 Server.
The failure of health check can also occur due to corrupted / damaged / unhealthy EDB. For this, first check Exchange database status and then repair it by using ESEUTIL tool or the advanced software provided by SysTools i.e. Exchange Server Recovery Software which provides Quick and Advance scan mode that easily resolves database corruption Exchange 2010/2013/2016 and repair EDB file automatically with no data loss.
The Error – Database Redundancy Two-Copy Health Check Failed
Having two servers running Exchange Mailbox, Client Access Server (CAS), and hub roles together with an Exchange Server DAG setup geo-located with different subnets connected to a site-to-site VPN, Windows Server 2012 R2 and Exchange 2013 Server standard configured.
In the event log, you can see the no. of error message in the application log on MSExchangeRepl along with many Event IDs such as: 4113, 2059, & 2153.
How to Fix the “Exchange 2013 Database Redundancy Two-Copy Health Check Failed”?
There could be so many possibilities that is the cause of this error. For this, first users have to check the Exchange Server log and see if there is any changed in that or not. After checking, if all the log are correct then check the connectivity. In that verify the connection speed, lost packet during transmission, and if there is any disconnected or not. Also, check any changes in the network firewall or configuration changes.
Then check the AD (Active Directory) Servers are working properly with the “repadmin /replsummary” to see replication between site is okay. After that, use the /queue to check if there are any blocked or processed item.
Use the /showrepl command the AD partition overview. Also, you can check DNS is healthy & replicating between sites. Microsoft Exchange Server fully depends on you Active Directory schema and if the AD, as well as DNS, aren’t healthy than you have Exchange Problem.
Another thing to keep in mind is the amount of mailboxes with their size and the size of the original database. It would be wise to segment users based on their department or location. Other option is to create the new Exchange database and move all the EDB mailboxes into it.
Users can also use another option i.e. to reseed the database depending on the bandwidth & size. This process takes time to finalize.
You can also use the backup software but make sure that the tool is compatible with Exchange Server DAG because using the wrong create chaos in your setup and also create corrupted or damaged database.
Run the Exchange PowerShell command Test-ReplicationHealth and if you encounter an error on “DatabaseRedundancy and DatabaseAvailaibility” then you have to go through the setup. Also, check the network card again, if you are using one, add another card because the minimum that is used in the server is two.
For reseeding the other copy, login to the EAC (Exchange Admin Center) >> Go to Servers >> Database. Then, users will see that the “Bad Copy Count” of the mailbox database is 1. Select the database which has issues.
Click the update button and follow the wizard to see the problem you are seeing in the database copy. If everything goes well then the database should be re-seed and issues resolved, but first be cautious in reseeding the database to see what impact it makes on connections & users. If the problem isn’t resolved, in that case, users can use the Exchange Server Recovery Software that repair Exchange mailbox and EDB file from corruption without any loss of data and export directly to the Live Exchange Server, Office 365, and multiple file formats by using recovery manager of Exchange database utility.
Bringing It All Together
Now users have complete information on how to fix the error “database redundancy two-copy health check failed” in Exchange 2013 Server. If the solution doesn’t work and your Exchange database is severely corrupted then you can use the advanced software mentioned here which remove corruption from offline/dismounted EDB file and export the healthy as well as recovered mailboxes to the Exchange Server, O365 and various file format in a simplified manner.