Quantcast
Channel: Exchange Server Blog
Viewing all articles
Browse latest Browse all 133

Recovery from Corrupted Exchange Database File

$
0
0
In this blog post I am going to discuss an Exchange error that appears in Exchange information store database and due to some corrupted items. Generally, this error message is displayed on the screen when an administrator tries to take backup of Exchange databases:

“Exchange Information Store backups fail with the error "0xfffffea9 - 0xa000fea9 (2684419753)"
\\SERVER NAME\Microsoft Information Store\Storage Group\Mailbox Store (Exchange Server)" is a corrupt file. This file cannot verify.


\\SERVER NAME\Microsoft Information Store\Storage Group\Public Folder Store (Exchange Server)" is a corrupt file. This file cannot verify.

\\SERVER NAME\Microsoft Information Store\Storage Group\Log Files" is a corrupt file. This file cannot verify.”

The most common reason of this error is the parallel time in which Exchange maintenance and backup process are scheduled. Or may be possible in actual Exchange database include some severe damage in its database.

Solution to Fix this Problem:

• Check and ensure that Exchange maintenance and backup process are not running in parallel. If the maintenance job is going on, stop backup process immediately. Once maintenance job completed, try to create backup of your Exchange server data.

• If NTBackup tool or other backup utility continuously fails to complete its task successfully, it might be possible that your information store database is corrupt. Try to run ESEUTIL repair tools to repair corrupt items in Exchange databases

In case the problem is not fixed by running ESEUTIL command line tool, you can sort it out by using some third party Exchange repair tool like Stellar Phoenix Exchange Server Recovery software. It is one of the most advanced, simple, and easy to use applications that can easily repair and recover all damaged as well as lost data from corrupted Exchange databases. This EDB repair software provides safe recovery of corrupted data from MS Exchange Server 2010, 2007, 2003, 2000, and 5.5 versions.

Viewing all articles
Browse latest Browse all 133

Trending Articles