Summary: This post revolves around an Exchange database error "recovery has indicated that there might be a lossy recovery option" that’s not very frequently encountered, but can boggle the smartest of administrators when it does. You can't perform a complete recovery, if transaction log files are missing, in this case, Exchange Recovery Software - Stellar Repair for Exchange can help .
We recently received a request from one of our contacts who needed to replay transaction logs into Exchange database to recover data. The problem was that some of their transaction log files were missing so they weren?t able to perform a complete recovery. Instead, on trying to replay the files the process terminated halfway with the error message:
Recovery has indicated that there might be a lossy recovery option
Now this error message is quite confusing. Since at the base of this problem lie missing log files, understanding why their absence can trigger such a complicated error is essential.
A brief intro to transaction log files
A Microsoft Exchange transaction log file is a file that contains detailed record of the changes that are made to the database. All information that needs to be added to the database is first written to a transaction log and then the contents of that transaction log are written to the database.
This model of using transaction log files eases the process of operating server activities. It enables users to access the server even when a backup is being taken. If transaction logs weren?t used, data would be written directly to the database in which case, the database would need to be closed before being backed up. To avoid server inaccessibility during backups, transaction logs were introduced as a middle entity that can hold information till server backups complete. To maintain database consistency, transaction logs are written to the database when it is shut down at the end of the day.
Now, if at the time of database shutdown some log files get missed out from being committed to the database, the database is left in an inconsistent state and marked to be in ?dirty shutdown? state. This state of the database is the cause of many Exchange errors. TO resolve these errors, restoring the database is needed either by committing unsaved log files, or restoring the database from backup, or replaying committed log files.
If one or more of the log files that needs to be replayed are missing or deleted by accident, the error we?re focusing on right now will be thrown by the server:
Recovery has indicated that there might be a lossy recovery option
Let us now see what a user should do to overcome this error.
Solutions to the error
If you do not have a full backup to restore the database from, performing a soft recovery is the best way to bring an inconsistent database to consistent state. However, this option won?t work if some of the transaction log files are missing, as is the case here. Thus, the problem needs to be dealt with in a different way:
- Re-perform the restore procedure. If it still doesn?t work, you?ll need to hard repair the database as shown in the next solution.
- ESEUTIL + ISInteg
Use the ESEUTIL and ISInteg command combination as follows:
- Run Eseutil/p <databasePath> to repair the database file
- Click Yes on any warning signs that pop up
- Once the repair process completes, the database should be marked to be in ?clean shutdown? state
- Run Eseutil/d <databasePath> on the repair store
- Mount the database and then dismount it
- Then run isinteg ?s Server Name ?test ?alltests ?fix on the store till it reports no errors
While the above mentioned procedure should work, it will cause some of your data to be erased. The ESEUTIL /p command attempt to fix damaged database pages, however, the pages that cannot be repaired are discarded.
If you need a solution that doesn?t involve any data loss, or it this solution also doesn?t work, you?ll need a reliable third-party application to repair Exchange database.
- Repair EDB files with Third-party software
The best software for repairing Exchange database (EDB) files is Stellar Repair for Exchange. This proficient application not only repairs damaged EDB files but also facilitates extracting and saving mailbox items in Outlook PST format. The software can repair large as well as multiple EDB files simultaneously and it also supports exporting recovering mailboxes to Live Exchange Server or Office 365.
The best way going ahead?
Keeping a product like Stellar Repair for Exchange handy has its advantages. It can combat all Exchange issues with expertise and ensure that your users don?t have to face any server downtime or mailbox inaccessibility owing to unexpected errors.
Check out what MVP says about Exchange Recovery Tool from Stellar.
