Exchange Server Recovery to Sort Out Exchange Server “No Entries Found” issue

Backup helps you in restoring the lost data, as and when you encounter any instance of data loss or inaccessibility in any application. Loss of the data in the Exchange Server database can also be prevented by taking regular backups. There are many utilities available to take timely backups of important data. But, at times, restoring data from backup is not that smooth and numerous error messages pop-up, stopping the restoration process. The most possible reasons behind such problem can be the corruption of Exchange database or corrupt backup file. In order to overcome such situations, corrective measures must be applied. However, if you still failed to resolve the issues, then you have to take the help of any third party Exchange Server Recovery tool to perform the recovery operation.

To further clarify above issue, suppose that you were making an attempt to restore your Exchange Server data from the backup. But, you failed to do the same and received an error message that looked exactly as given below:

“No Entries Found

In addition to this, you received the following information after the above mentioned error message:

Backup of “SBS\Microsoft Information Store\First Storage Group”
Backup set #4 on media #1
Backup description: “SBS Backup created on 30/03/2006 at 6:38 PM”
Media name: “Media created 30/03/2006 at 6:38 PM”
Backup Type: Normal
Backup started on 30/03/2006 at 7:17 PM.
Backup completed on 30/03/2006 at 7:20 PM.
Directories: 4
Files: 6
Bytes: 607,167,376
Time: 3 minutes and 29 seconds
Verify of “SBS\Microsoft Information Store\First Storage Group”
Backup set #4 on media #1
Backup description: “SBS Backup created on 30/03/2006 at 6:38 PM”
Verify started on 30/03/2006 at 7:57 PM.
Verify completed on 30/03/2006 at 8:00 PM.
Directories: 4
Files: 0
Different: 0
Bytes: 607,167,376
Time: 3 minutes and 9 seconds”

Cause:

Some of the causes that are responsible for the above error message are as follows:

• Incomplete backup process.
• Corrupt or damaged Exchange database backup file.

Resolution:

To resolve above problem you have to follow the below suggestions:

• Make sure that the backup process is complete or successful.
• If the reason behind the problem is the corruption of Exchange backup file, then you have to repair the Exchange database, with the help of a ‘Eseutil/p’ command.

You can also refer to the following KB article to get detail steps to backup and restore Exchange server: http://support.microsoft.com/?id=258243

At times, when the Exchange Server database is severely corrupt, this command does not prove helpful. In such situations, you can rely on a third party Exchange Server recovery tool. Such tools perform Exchange database recovery even if the Exchange Server database is severely corrupt and all the normal repair methods have failed.

About the Author: The author of this post is an an technical writer and active blogger. She has enormous experience in Microsoft Exchange Server and wants to share her Exchange Server Recovery solution for the above issue.