| Exchange Server database corruption can occur | | | | -573” |
| for several reasons and if backup is present that | | | | The database recovery method fails and data |
| is stable, you can use it to restore the database | | | | remains inaccessible. |
| conveniently. A database backup alone is not | | | | Cause |
| sufficient to bring the database back to consistent | | | | Error -573 indicates that Exchange Server has |
| state. It is because after restoration, database | | | | detected some corruption in a backup set and |
| and log files are not in perfect sync with each | | | | cannot proceed. |
| other. So, you need to replay the transaction files | | | | Solution |
| in order to make the database consistent. This | | | | You can try applying these solutions to solve such |
| process is termed as 'Hard Recovery'. The hard | | | | problems: |
| restore requires all backup sets to be in clean | | | | 1. |
| state or otherwise, this procedure may fail. In | | | | Check for some other backup set that may be |
| such instances, you left with no alternatives other | | | | used to restore the database and carry out hard |
| than using an Exchange Server Recovery utility | | | | restore |
| that can repair the original database. | | | | 2. |
| As example, consider an instance when you | | | | Run 'ESEUTIL /P database_filename.edb' |
| experience dirty shutdown with Microsoft | | | | command to repair the database, where |
| Exchange Server. The next time, when you try | | | | 'database_filename' is the name of the corrupted |
| to mount the Information Store database(s), it | | | | database file. But during repair, the command can |
| fails and you receive errors suggesting that one | | | | discard table rows and even complete tables. So, |
| or more database(s) are corrupt. You try to | | | | it is suggested to backup the database and later, |
| perform hard restore, but cannot do so and | | | | opt for safe third-party Exchange Server |
| receive the below error message: | | | | Recovery solutions if you find the important data |
| “JET_errLogCorruptDuringHardRestore | | | | missing after repair or the repair process fails. |