Database is Missing Optional and Required Log Files

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool has determined that log files that are required to recover 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.

If an Exchange database has not been shut down correctly, there are always log files that must be replayed into the database before it can be mounted again. At a minimum, there may be only a single log file that must be replayed. Typically, however, there are several log files.

In addition to the required log files, there may be additional log files that can be played into the database. Although it is not required that these optional log files are replayed before the database can be mounted, you can use these log files to recover additional data. If you do not replay these optional log files, all data that was contained within them will be lost.

To correct this error

Locate the missing transaction log files and add them to the appropriate folder.
If you cannot locate all the optional log files, you can recover the database in isolation with only the required log files. To recover the database without the optional log files, follow the instructions in the Exchange Server Analyzer. Remember, if you recover the database without the optional log files, you will lose the data that was in those optional files.

However, depending on which log file is missing, you may be able to replay some of optional log files into the database. For example, consider the following scenario. You have log files numbered one through ten. The tenth log file is required (the remaining files are optional) the sixth log file is missing. In this case, you would be able to replay the log files numbered seven through ten because the sequential order up to the required file is constant.

Repair the current database.

Note:
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 repairing 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).

Note:

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 repairing 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).