Problem arises when the user faces inconsistent State issue in Exchange Server. Being a server, it is not easy to resolve and recover Exchange corruption. Among a handful of methods, use of /m:RecoverServer Setup in Exchange Recovery is commonly seen. As this method has been successful in recovering damaged Exchange Server, this post will elaborately discuss this method. First of all, we will go through a user query which is related to Exchange Server recovery.
“I have been experiencing some issues while trying to access Exchange Server Database. As an admin of the server, I have a feeling that the database is facing corruption. I have heard that /m:RecoverServer Setup can recover failed Exchange Server but do not know how. I will be grateful if anyone can share the process of Exchange Server recovery using /m:RecoverServer.”
Causes of Exchange Server InConsistent sta
A number of causes can be held responsible for Exchange Server corruption and failure. Some of the important causes of Exchange Server corruption are:
-
- Hardware and Server problems
- Database size crossing the limitations
- Virus attack and anti-virus application
- The sudden closure of system and Server
- Changes in settings done by the user
Importance Setup /m:RecoverServer In Exchange Recovery
If your Exchange server is facing corruption or failed on its part, it is high time you fixed this server using /m:RecoverServer. Otherwise, you will face these problems:
- Information Store Service cannot be started or stopped
- Exchange email client fails to send emails
- Information Store also stops responding
For these reasons, it is imperative that users recover their Exchange Server by using Setup /m:RecoverServer command.
What is Setup /m:RecoverServer Switch in Exchange Server
Setup /m:RecoverServer, also known as M switch, is one of the tools used to recover damaged Exchange Server. It is basically a command that is run to tell the server that it should read Active Directory service Application’s configuration information. The name of the server should be same on which we are running Setup (mode: recovery/ setup). After that, Exchange files and services get installed on the Exchange server. Then settings and roles saved in Active Directory get applied to MS Exchange Server.
How to Use /m:RecoverServer Setup in Exchange Recovery
In this segment, we will learn how to use this command to recover Exchange. Users must remember that this can only be used to recover, not to repair.
Pre-requisites to Setup /m:RecoverServer Command: This command cannot recover Exchange Edge Transport Server. It only works in cases of Mailbox, ClientAccess, HubTransport and management tool.
The server on which you are performing recovery should contain the disk drive letters same as the damaged server. The recovery platform server should also have same hardware configuration and performance characteristics like the failed server.
- The server that will be used as the recovery platform, should be running operating system same as the affected server. For example, it is not possible to recover a server running on Exchange 2010 on a server that runs Windows 2012 R2, or conversely.
Sometime Inconsistent state arise due to the corruption of Exchange Database file and Mode RecoverSever Setup can help the user to access the Exchange Server again. In that case Exchange EDB Mailbox Recovery can be useful.
Steps to Setup /m:RecoverServer In Exchange 2010 , 2013 and 2016
- First of all, reset your computer account. For that, log on to a particular Domain controller and open Active Directory Users and Computers by running “dsa.msc” command. Now go to MMC snap-in and select computer. From the right panel, select the name of the system that crashed>> Action>> Reset Account.
- Establish a connection between your system and respective Domain.
- Now, install dependencies of Exchange Server.
- If Exchange is not installed in its default location, locate Exchange binary files by using /TargetDir switch. Otherwise, Exchange server files are installed in“%programfiles%MicrosoftExchange ServerV14”, which is their default location. Follow these steps to find out the Exchange installation location:
- CN=ExServerName, CN=Servers, CN=First Administrative Group, CN=Administrative Groups, CN=ExOrg Name, CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=DomainName, CN=Com
- Right-click on the Exchange server object and click on Properties option. Find out msExchInstallPath attribute to open it, since it has the current installation path.
- Perform installation of Exchange Server to the changed location that contains setup files of Exchange. Now type Setup /M:RecoverServer. Use “/DoNotStartTransport” syntax after RecoverServer switch, if you want to recover only Hub transport role.
- The recovered server containing the Mailbox Server role should have respective Public folder database and Mailbox retrieved from backup or old server disks (if possible.) Restoration of public folders is not needed if they got replicated by other exchange organization servers. In this case, other Public folder servers will backfill a blank Public folder database.
Conclusion
Here we have discussed how to recovery failed or corrupt Exchange Server database. However, If Exchange 2016 files are suffering from corruption, this remedial method will not. Users have to adopt a different approach to recover corrupt Exchange Server files.
0 comments:
Post a Comment
Post a reply