Database Corruption in Exchange 2010 Server – Issues & Prevention
MS Exchange Server is prone to failures and corruption issues. No matter what version, there stands, always a chance for the database to get damaged. Database Corruption in Exchange 2010 occurs mainly due to two reasons:
- Hardware Failure
- Software Issues
Different hardware issues can result in physical corruption of Exchange database. Database mounting issue, Disk failure & User errors, Jet Engine Error are some major issues found in the Exchange database. The user (Administrator) errors occurred might be deleting some important log files from the Exchange directory while freeing up space in Exchange database by the Exchange Administrator. Jet Engine errors can occur if an Incorrect checksum is found during page read, or when the pages are uninitialized in the Exchange database Engine or if restrictions are provided to the Disk I/O process. These errors are named as Error 1018,1019,1022 respectively. The effect is generally low (on damage), but, it is advised to take steps to prevent hardware issues to prevent database corruption in Exchange 2010.
These issues can vary in the level of occurrence and corruption. Exchange server may encounter corruption at the page-level, or entire database may get damaged. There can be various reasons involved in Exchange 2010 database corruption that is difficult to foresee. It can range from Exchange Server failures, antivirus programs to Exchange Dirty Shutdown state. This unexpected shutdown is actually the most common cause of database corruption in Exchange 2010 Server and other Exchange Server versions. Let us discuss them in detail followed by the ways to prevent or fix them.
Methods to Prevent Corruption In Exchange Server Database
The most basic thing to do is to use good quality components and ensure that the database never exceeds the storage device limit. It prevents from the physical corruption or a chance to reduce its occurrence. Some other common proactive methods are listed below:
• Keep the application updated with the latest service packs.
• Always ensure proper shutting down of Exchange Server.
• Make sure other applications such as antivirus are not meddling with the Exchange Server.
• Perform regular database optimization and configure appropriate Server settings.
• Prevent virus or malware attack and take timely backups.
The above shown proactive measures can prevent corruption to an extent. But in case, if your Exchange Database still shows any corruption symptoms, follow the given PowerShell to fix it effortlessly.
Expert Solution to Fix Database Corruption in Exchange 2010 Server
As an Exchange database gets corrupted, the Exchange Administrator try to resolve it with Microsoft built-in utilities. However, to actually operate them, the Administrator will require a proper technical understanding of its working. Also, for the most part(especially major corruption), using these utilities will definitely result in data loss.
So, in case, the utilities fail to fix the corrupted Exchange Database, go for SysTools Exchange Recovery Software that easily recover Exchange database from corruption. This software effectively fixes all levels of the corrupted Exchange Mailboxes (EDB); dismounted/offline Exchange Database file.
This recovery manager for Exchange utility offers dual scanning mode i.e. Quick and Advance scan that recovers and repair EDB file from minimal and major corruption. According to the level of corrupted Exchange database file users can select the scan mode option to recover & repair Exchange mailbox without any loss of data. The advance scan mode option also recovers hard deleted EDB mailboxes and data items.
With the help of given option, one can recover deleted mailbox after retention period. The tool supports pub1.edb file, priv1.edb file and Streaming Media File. Users can export various types of mailboxes and items directly to Live Exchange Server, Office 365, and HTML, EML, MSG, PST, MBOX, PDF file formats.
One can selectively migrate Microsoft Exchange emails, contacts, journals, tasks, notes to the given export option. The software allows users to remove encryption from Exchange mailbox i.e. (SMIME/OpenPGP). Also, you can migrate public folders to Office 365 along with private Exchange mailboxes.
Step by Step Procedure to Fix Database Corruption in Exchange 2010
Step 1: Download, Install the advanced utility in your machine and Run it
Step 2: Select the Add File button > Load the corrupted offline Exchange EDB file
Step 3: From the scan mode option, click advance scan > Click on the Add button
Step 4: Preview recovered corrupted .edb file > Click export
Step 5: Select Exchange database mailboxes > Click on the export option > Select the browse button to set target file location > Click on the export button
Repair Database Corruption In Exchange 2010 Server
Microsoft has provided some built-in utilities in Exchange Server which verifies and fixes the database damage to some extent. The utilities provided will exceptionally repair the minor corrupted database file or the entire database, but when the corruption turns to major level, the repairing utility may lose the corrupted data from the database.
Isinteg Utility to State Corruption Level In Exchange Database
Isinteg is actually an Information Store Integrity Checker tool. It displays the health state of the database along with a list of examined tables. The issues detected by this utility can be easily repaired. These issues are generally related to logging into the Exchange server database, send, receive and open particular emails, etc. To run this command line utility, use the following code in the command prompt:
- Pri : private store(default)
- Pub: public store
- Fix: repair store
- Logfilename: Stores log information(default – \isinteg.pri, isinteg.pub)
- Verbose: report verbosely
- Detailed: detail mode(default: non-detail mode)
Eseutil Utility to Fix Corruption In Exchange Database
This inbuilt tool is considered to be of great importance among the Exchange administrators. Its usefulness extends from fixing the corrupted database and defragmentation to verifying their integrity. Let us take a look at its functionality:
- ESEUTIL /D – defrag Exchange mailbox database(to eliminate the occurrence of white spaces)
- ESEUTIL /R – perform soft recovery in Exchange database
- ESEUTIL /P – repair corrupt offline EDB files(discards not repaired pages)
- ESEUTIL /K – to verify the checksum of pages
- ESEUTIL /G – Verify the integrity of the Exchange database
- ESEUTIL /M – display headers, log files and checkpoint files
- ESEUTIL /C – Hard recovery of database
PowerShell Command – An isinteg Tool Alternative
Apart from the utilities provided Exchange Server introduced a new PowerShell Command in Exchange Server 2010 SP1, to detect and fix corruption of specific mailbox or the entire Exchange database. It’s named the “New-MailboxRepairRequest cmdlet“. However, it can run only in Exchange Management Shell on Exchange environment and once the process starts, it can’t be stopped unless you dismount the database.
It is capable of fixing the following corruption types:
- SearchFolder Corruption – issues in search folders
- AggregateCounts – Incorrect values of folder items and size
- FolderView– Incorrect contents displayed by views
- ProvisionedFolder– Provisioned folders pointing to wrong parent folders
The above-shown methods are to be done in Exchange Management Shell (Command Line). Thus, if anyone feels disturbed using the above methods can use Exchange Recovery Tool to recover Exchange Database file and repair the database from corruption and data loss.
The inbuilt utilities provide useful means to fix minor issues with less effort. But, they cannot hold up very well in every situation especially when major level corruption occurs. In such cases, use Exchange Recovery Tool to recover database corruption in Exchange 2010, 2013, 2016, 2019. It eases up the entire process and provides you with the best possible solution with minimal effort.