Microsoft Exchange Server is a powerful platform for business communication and collaboration. It manages mailboxes and their items, including emails, contacts, calendars, and public folders. Like all the other items in a mailbox, public folders also play a distinct role in facilitating seamless communication. They simplify the information sharing and enhance teamwork across multiple users.
However, a corrupt Exchange database can make public folders inaccessible, disrupting crucial business operations. This necessitates the prompt recovery of the Exchange server and the affected public folders. Here is a comprehensive guide to recovering public folders from a corrupt Exchange database.
Public folders in Exchange Server – A brief introduction
Microsoft Exchange Server consists of two database files:
- Streaming data file (.stm), a part of the private folder
- Exchange database file (.edb), a part of the public folder
Here, the EDB file is the primary storage location for mailbox data
The Private folder helps the Exchange server select the default mailbox storage database. It contains database files named Priv1.edb and Priv1.stm.
The Public folder stores email information related to the default public store, such as emails, contacts, attachments, notes, etc. It includes database files with the names Pub1.edb and Pub1.stm, respectively.
Functions of public folders
Designed for shared access, public folders help collect, organize, and share business details with others in your organization or workgroup. They make it easier to browse a deep hierarchy and search for the required content.
All the action happens in the EDB and STM database files of the public folder. In addition, the Pub1.edb files also consist of important email attachments and MAPI messages. Any damage to these files can cause significant data loss. To avoid any kind of data compromise, you need to protect the file from potential threats.
Security of Public folders in Exchange server
The Exchange server uses a built-in security model based on Role-Based Access Control (RBAC), which allows only the admins to grant permissions to groups and users. This protects the folders from any unauthorized entry, saving their data and averting the chances of corruption due to malware injection.
Still, in case of a corrupt Exchange database, the public folder is likely to become inaccessible, thus disrupting crucial business operations. This makes it essential to recover the affected public folders. We will discuss it more, but before that, let’s learn about the Exchange database and the reasons behind its corruption.
What is an Exchange Database, and how does it become corrupt?
An Exchange Database file, stored in the MS Exchange Server, consists of all the mailboxes and the included items. The data stored in an EDB file is accessible by JetBlue, a common moniker for Extensible Storage Engine (ESE), a database technology.
The ESE stores secure information for smooth email communication. It also works as a mode to access Exchange Server data called the indexed and sequential access method (IASM).
An EDB file can become corrupt due to several reasons, such as power outage, virus attack, hardware issues, Dirty shutdown, or crash of the Exchange server or software. In all these cases, the resulting EDB corruption results in the loss or inaccessibility of sensitive data. This causes huge reputation and financial losses to organizations.
The effect of corrupt EDB on public folders
The impact of a corrupt, damaged, or inaccessible EDB file on public folders is also severe.
- Inaccessible: It makes public folders and the associated shared content, emails, contacts, etc., inaccessible.
- Data loss: Public folders may suffer a partial or complete loss of data, causing corrupt metadata and folder hierarchy.
- Communication loss: EDB corruption causes communication breakdown in public folders, reducing productivity.
- Recovery challenges: Data inconsistency is a possible risk that poses challenges in public folder recovery.
- Permanent data loss: Another major threat, it makes public folders irrecoverable. This condition is possible mostly if there is no recent backup of the public folders.
- Jet Engine errors: Usually caused due to issues in hardware or software, damaging the EDB at various levels, such as Jet database, Information store, Exchange server file, etc.
Steps to Repair and Recover Exchange Public Folders
To carry out Exchange recovery, you need to perform several important steps, including those on the command prompt. Make sure to be careful while executing these steps, as even a minor typo can cause severe damage to the EDB file. Before you start repairing, go through the error in the public folder carefully, as it will lead to changes in the repair steps. Here are the steps:
- Press Windows + R on your keyboard
- In the Run dialog box, type services.msc
- Click OK to open the Services page
- Look for Exchange Information Store Services and stop it
- On the PowerShell command-line interface, use the command below to move to the Bin folder:
eseutil /mh ..\mdbdata\priv1.edb
- Enter the command line path: C:\exchsrvr\bin>
- Press the ‘Enter’ button.
After performing the above steps, you will get the database status – whether it is a clean or dirty shutdown. If the database is still in the dirty shutdown state, move the EDB file to the log file location and proceed with a soft recovery.
- At the command line path C:\Program Files\exchsrvr\MDBDATA> run the below command:
C:\Program Files\exchsrvr\BIN\eseutil /r E00
- Recheck the database state. If the dirty shutdown still exists, now is the time for hard recovery.
- At the command line path C:\Program Files\exchsrvr\MDBDATA>, run the following command:
C:\Program Files\exchsrvr\BIN\eseutil /p pub1.edb
- Next, visit the Mbdata folder to discard the*.chk files, Temp.edb files, and log files
- In the next step, you need to be extremely careful to mount and dismount the Exchange server database. This will stop the Exchange Information Store services.
- Now is the time to defrag the Public EDB mailboxes by running the command below at the command line path C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\pub1.edb
- Next, fix the Isinteg.exe file through the following command:
C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests
- Exit the command prompt and restart the Exchange Server services to recover the corrupt Pub1.edb files.
These Exchange recovery steps will help repair the public folders in cases of minor database corruption. If the damage is severe, this process may be insufficient to recover the public folder. In addition, considering the technical steps involved, you should have sound technical knowledge to carry out these Exchange recovery steps. Using professional Exchange recovery software would be a better option to remedy this situation.
Stellar Repair for Exchange – A popular Exchange Recovery Tool
Stellar Repair for Exchange – the GUI-based, reliable, and user-friendly software is a preferred choice among MVPS. Some of its prominent functions are as follows:
- Recovers dismounted databases
- Repairs corrupt exchange database files
- Restores the mailbox items, including the Public folders
You can buy this third-party Exchange recovery tool in any of the three variants – Corporate, Technician, and Toolkit. Much depends on your specific requirement and budget. Explore the Stellar Info website to know the features of this software in detail and proceed to buy the best variant.
Conclusión
Your Exchange database may become corrupt due to several reasons, and the same holds for the contained mailboxes and their items, including public folders. To repair them, you can proceed with a lengthy and error-prone method based on command prompts on the command line interface. Alternatively, you can perform Exchange recovery using third-party software such as Stellar Repair for Exchange. Download its free trial version to get an idea of how it works. To buy its paid version, visit the Stellar Info website.