XADM: Third-Party Online Backup Software May Not Restore Log Files (258236)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
- Microsoft Exchange Server 5.5
This article was previously published under Q258236 SYMPTOMS
When you attempt to start the Microsoft Exchange Directory Service or the Information Store Service after a database is restored, the service may not start.
You may receive one of the following error messages, or a similar error message, which indicates that log files are missing:
Error(s) -1811 JET_errFileNotFound -509 JET_errMissingPreviousLogFile
If you check the database in question by running the following command
eseutil /mholt;path to DB file> |more
the database appears to be in an inconsistent state, which indicates that to start the database, log files must be played into it. In addition, the Restore In Progress Key may be missing from the registry after the restore.
CAUSE
This behavior can occur because certain backup software packages allow you to restore log files from an online backup. When each service starts, it is directed to the transaction log files so that it can replay any missing transactions. These log files default to the Dsadata folder in the Directory Service or the Mdbdata folder in the Information Store Service.
RESOLUTION
To resolve this issue, restore log files in the backup software when you restore from an online backup.
WORKAROUND
To work around this issue, restore the entire database again. You can also restore only the missing log files by using the Exchange Server-aware portion of the backup software.
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kbprb KB258236 |
|---|
|