() Database requires logfiles – in order to recover successfully. Recovery could only locate logfiles up to .

Details
Product: Exchange
Event ID: 453
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Database <name> requires logfiles <number><number> in order to recover successfully. Recovery could only locate logfiles up to <number>.
   
Explanation

The database requires log files in order to continue.

You will receive the following phrase in the event Description:

Information Store (number) [guid] Database [path\filename] requires logfiles

[e.g.] 154-158 in order to recover successfully. Recovery could only locate logfiles up to [e.g.] 157.

  • Cause 1 – An online restore fails due to log files missing from the temporary folder that is specified in the Microsoft Windows 2000 Backup program under the temporary location for log files.
  • Cause 2 – A hardware failure causes loss of log files in the log file sequence needed for the restore.
  • Cause 3 – Antivirus software has quarantined the current log file, E0n.log.
   
User Action

Generally, verify whether or not the log files have been moved or deleted. If the log files have been deleted, restore them from backup media. If they have been moved, move them to the appropriate location. The event text will specify the required files. Check for related events and their description to determine specific causes and resolutions. Following are some specific resolutions for the common causes indicated in the Explanation.

  • Resolution 1 – Attempt to locate the missing log files and place them in the appropriate folder and run Eseutil /cc (hard recovery) or run Eseutil /cc /t (using the /t switch) to specify another location for all the necessary logs together in one folder and mount the database. If the log files cannot be located, restore from an earlier backup or as a last resort, repair the database, run Isinteg -fix, and ExMerge the results to a blank database.
  • Resolution 2 – Restore from an earlier backup or as a last resort, repair the database, run Isinteg -fix, and ExMerge the results to a blank database.
  • Resolution 3 – Stop the antivirus software scanning the information store files directory and the M: drive and check the registry settings for the antivirus software. Place the current log file back in the appropriate directory.

Related:

Leave a Reply