Database is Missing Required Log Files
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool has determined that log files that are required to recovering this database are not found in the log file folder. If a required log file is missing, a database cannot be recovered until the log file is found.
To correct this error
Locate the missing transaction log files and add them to the appropriate folder.
Restore the database from backup. Then roll the database forward by playing the remaining transaction log files into the database.
Data in the missing log file and subsequent log files will be lost. Before you restore a database from backup, you should save a copy of the current database. If the restoration is unsuccessful, you may be able to repair the current database.
Repair the current database.
Although repairing the database is likely to result in success, it is not guaranteed. Even a successful repair may result in minor or major data loss. For more information about how to repair an Exchange database, see Microsoft Knowledge Base article 812357, "How to maintain your Exchange database after you repair by using the Eseutil /p tool in Exchange Server 5.5, in Exchange 2000 Server, and in Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=812357).
Implement a hybrid strategy that includes repairing and restoring the database. Sometimes, you may be able to restore a database even though it cannot be rolled forward with additional log files. In these cases, you may be able to restore a previous copy of the database while simultaneously repairing the current copy that is not mountable. You can then merge the contents of the databases to maximize data salvage. This is an advanced strategy, and you may want to contact Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkId=31845) before implementation. For more information about this strategy, see Using Recovery Storage Groups in Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=47589).