Exchange Server is the emailing, scheduling, contact, calendaring, and collaboration platform set up on the Windows Server OS. It is used by both small and large-scale organizations. There are some situations where Exchange Server crashes or fails. The main reasons behind this issue is an inconsistent state in Exchange Server.
However, Exchange Server recovery is not such an easy task for any Exchange admin. So, it is important to always be prepared for any disasters. This is because any of type of disaster in a data center will affect the server mailbox so it is best to have a recovery plan. Thus, this blog will let users know how to recover mailboxes from failed Exchange 2016 Server without any loss of data.
“My mailbox server is the member of DAG and is creating some issue when I tried to access it. Being an admin, I think that Exchange Server is either crashed or there must be some corruption issue. I have heard about /m:RecoverServer set up to recover Exchange Server. But in the case of database availability group member server recovery, there are few changes in /m:RecoverServer set up. Can anyone tell me, how to repair mailboxes from failed Exchange 2016 database availability group member server via the same recovery set up?”
Before performing the manual activity to recover Exchange mailboxes from a failed Exchange Server, you need to first identify the problem properly in that only some of the database is corrupted, or if users are not able to access mailboxes and a restoration is needed.
Microsoft Exchange Server 2016 setup has a switch /m:RecoverServer, which can be used to rebuild Exchange Server. This Recovery Mode set up will read the configuration details from the AD (Active Directory) for a server using the same name as a server (on which you are running the setup). After that gathering information, the original Exchange files and services are installed on the Server. All roles and settings that are stored in the Active Directory are practically implemented on the Server.
Now, to recover mailboxes from failed Exchange 2016 Server, use setup /m:RecoverServer by following the steps mentioned below:
Get-MailboxDatabase DB1 | Format-List *lag*
Remove-DatabaseAvailabilityGroupServer - Identity DAG1 -MailboxServer MBX1
Add-DatabaseAvailabilityGroupServer - Identity DAG1 -MailboxServer MBX1
Add-MailboxDatabaseCopy - Identity DAG1 -MailboxServer MBX1
Note: The replay lag or truncation lag time of the database copies added before is greater than zero. You can simply use ReplayLagTime and TruncationLagTime parameters to reconfigure those settings:
When you have successfully recovered mailboxes from failed Exchange 2016/2013/10 Server and other below versions using Recovery mode, its time to place the database at the right place. After restoring the database, you have to mount the certificate again in Exchange Server.
After mounting the Exchange Database, if users unable to view the mailboxes data items due to corruption issues in the database. To overcome this problem first, you have to repair EDB file of Exchange Database. In order to recover corrupt EDB file data in a trouble-free way, try Exchange Recovery software.
Some prominent features of the tool are given below:
It is capable of repairing all data stored in the EDB files without any hassle. Some characteristics of the tool are given above that can help in recovering mailboxes from failed Exchange Server EDB Files.
|Office 365 to Exchange 2019 /2016 /2013 /2010 Migration – Quick Guide||264|
|Recover Exchange Mailbox Folder From EDB File – SysTools Exchange Recovery Tool||245|
|IT Pros Agree: AI and Machine Learning Key for the Future of Security||348|
|Exchange Disaster Recovery Plan – For 2016, 2013 & Below Versions||34|