Most of the people are very much aware of the fact that Exchange database files (.edb) are nothing more than the exact copy of the user’s mailbox on Microsoft Outlook. Furthermore, this MS Exchange Server operates in right collaboration with MS Outlook in the transaction of mails and other important information like contacts, calendars etc. and every particular mail that is received or sent by the user is mainly stored on the server. Now, exchange server principally accumulates these email files as EDB (Exchange Database) files that proves to be very useful in case of several data disaster situations.
EDB files are also prone to corruption just like any other data files. There can be various software and hardware issues for the same:
- Installation of malicious software
- Inconsistent firewall or Antivirus software
- Power failure
- Virus attack
- System crash etc.
- Accidental shutdown
- Overwriting of garbage data due to bad file system consequences in corruption of OST files
It is extremely important that you take care of your exchange server well. As an IT admin, you should keep a right check on your data saved and at the same time authenticate its reliability. At present, every storage group on an Exchange server typically comprises one or more than one Public Folder stores and Mailboxes. Throughout the installation process, only single storage group is formed by default. With Exchange Server 2000 and 2003, every Mailbox store comprises a database set which consists two files namely ‘Priv1.edb’ and ‘Priv1.stm’.
The ‘Priv1.edb’ file is a lot similar to a text database file that mainly consists of text attachments, headers and email messages. Additionally, this file also includes ‘Priv.stm’ which is a streaming file that mainly includes media files like images, audio and video and some other internet files that are configured as MIME data. The actual concern with ‘Priv. edb’ file is that its size continues to increase, which eventually makes it prone of getting damaged or corrupt. Moreover, Header and Hard disk corruption are other chief reasons responsible for damaging or corrupting the 'Priv1.edb file. But still, you don’t need to fright , since you can restore the damaged/ corrupt Priv1.edb file with a manual method.
1. First of all you need to initiate the Exchange information store and then write down all of the errors.
2. Now halt Exchange information store and then from the ‘Bin’ folder , run the commands given below:
C:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv1.edb"
3. You need to now authenticate the ‘State’ line in the output. Also, make sure that all the files are steady. In case, you discover any of the files incompatible, carry out a soft recovery process. And, to execute such recovery process, you just need to move to the folder where the log files along with the database are placed. After performing this, just make sure to run the subsequent at the command prompt:
C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /r E00
4. Once again, it is vital for you to make sure the steadiness of both the public and private information store.
5. If the files are steady, then skip the next step.
If the databases are found to be inconsistent, then it is significant for you to carry out a hard repair. To perform this, run the commands given below:
C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p priv1.edb
C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p pub1.edb
6. From Mbdata folder, eliminate the log files now which is very crucial.
7. Eliminate the 'Temp.edb' file. and '.chk' file.
8.You need to now mount the databases and then, dismount them immediately.
9. At last, you need to discontinue the ESS(Exchange information store ) and then you should defragment both private and public store DBs. To do the same, run the following commands:
For Pub.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\pub1.edb
For Priv.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\priv1.edb
10. Now, run the 'Isinteg.exe' utility just to make sure that each database is steady.
C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests
11. Lastly, restart the Exchange information store to recover the corrupt PRIV, PRIV1, Pub, and Pub1 Exchange Database Files.
On the other hand, after carrying out the manual process if you are still unable to mount the database and access your valuable emails, contacts and other messages, then you don’t need to panic as with the assistance of a competent third party exchange database recovery software like Stellar Phoenix Mailbox Exchange Recovery, you can resolve the problem very efficiently. This software is very much capable in repairing and recovering inaccessible and corrupt Exchange database files, i.e. 'Pub1.edb' and 'Priv1.edb', and can aid you get back the important user mailbox data. Moreover, with the help of this software, you can save the recovered files in PST format which can be easily imported in MS Outlook to access the mailbox items easily.
If you are facing any Exchange Server errors, then visit the following posts to get their solutions:
How To Resolve Exchange EVENT Error 9646?
How To Resolve Exchange EVENT Error 9646?
How To Resolve Exchange Error 4294966746: JET_ERR DATABASE INCONSISTENT?
How To Resolve Error 0X8004010F IN Exchange 2007?
How To Deal With Exchange SERVER ErrorS?
How To Resolve ESE Event ID 467 IN Exchange?
0 comments:
Post a Comment