Transaction log files contain the uncommitted data of an Exchange database.
When an EDB (Exchange database) file crashes, the transaction log files act as disaster recovery means as they bring the database to a consistent state.
For these reasons, it is recommended to store transaction logs on a different drive to avoid disk failure consequences that can affect the database.
At times, Exchange Server observes issues when writing data to the drive where log files are stored.
This can occur out of several reasons, such as file system issues, antivirus software problems, disk concerns etc.
You need to troubleshoot the root cause.
However, if the database is still inconsistent, you should restore the damaged database from backup or apply Exchange eseutil tool.
Alternatively, you can opt for using an EDB Recovery Software to recover the damaged database.
For example, you might receive the below error with your Exchange Server: "Unable to create a new log file because the database cannot write to the log drive.
Drive may be out of space or incorrectly configured.
Check file system, drive space, and antivirus settings.
" This error is logged with event 413 in application event log.
Cause The possible reasons for the above error to occur depend on the error number described in the event description section, as follows:
If not, you should restore it from backup.
When there is no valid backup, you can run hard recovery for the database using eseutil /p and isinteg -fix commands.
But the command deletes the corrupted data instead of repairing it.
Thus, you should make a backup first.
To repair the database safely, you should use an EDB Recovery utility.
There are perfect EDB Recovery Software equipped with database-aware algorithms to repair the corrupted Exchange database and extract the user mailboxes.
When an EDB (Exchange database) file crashes, the transaction log files act as disaster recovery means as they bring the database to a consistent state.
For these reasons, it is recommended to store transaction logs on a different drive to avoid disk failure consequences that can affect the database.
At times, Exchange Server observes issues when writing data to the drive where log files are stored.
This can occur out of several reasons, such as file system issues, antivirus software problems, disk concerns etc.
You need to troubleshoot the root cause.
However, if the database is still inconsistent, you should restore the damaged database from backup or apply Exchange eseutil tool.
Alternatively, you can opt for using an EDB Recovery Software to recover the damaged database.
For example, you might receive the below error with your Exchange Server: "Unable to create a new log file because the database cannot write to the log drive.
Drive may be out of space or incorrectly configured.
Check file system, drive space, and antivirus settings.
" This error is logged with event 413 in application event log.
Cause The possible reasons for the above error to occur depend on the error number described in the event description section, as follows:
- Error -1022 = Jet_errDiskIO: This error occurs due to general disk I/O errors that resist the access of requested database page or checking a file.
- Error -1032 = Jet_errFileAccessDenied: The error indicates that Exchange Server cannot access the file, probably because it is read-only or is in use by a process (virus checking or backup process).
- Error -1811 = Jet_errFileNotFound: The error -1811 implies that Exchange cannot found the log file because it is missing or has mismatching signature with the database.
It can also occur if the log files are stored on an unsupported network storage, failed drive or deleted by an antivirus software.
- Make sure that the log drive file system is free from errors by running chkdsk
- Check for system related problems in system log
- Check for the write permissions and available space on the disk
- Make sure that an antivirus software is not running
- Change the folders' permissions containing information store file to default
If not, you should restore it from backup.
When there is no valid backup, you can run hard recovery for the database using eseutil /p and isinteg -fix commands.
But the command deletes the corrupted data instead of repairing it.
Thus, you should make a backup first.
To repair the database safely, you should use an EDB Recovery utility.
There are perfect EDB Recovery Software equipped with database-aware algorithms to repair the corrupted Exchange database and extract the user mailboxes.
SHARE
