Event 217 and 478 while Backing up Exchange Database

Exchange Server storage groups and databases areEvent 217 typically indicates backup failure and event
the most vital component of recovery when the478 shows database corruption due to hardware
server crashes. You might observe typical symptomsissues. Event 217 might also be encountered due to
with a corrupted Exchange database. For instance,Exchange beyond EOF (End Of File) condition.
you may fail to backup it. When it occurs, theSolution
corresponding event indicating the failure is logged inMake sure you install all the latest updates and
application event log, which helps you to deduce thehotfixes available for your Exchange Server. To
cause. However, a corrupted Exchange databasecorrect the corrupted database issues, you should
should be restored from backup. In case ofperform steps, as follows:
unavailability of backup, you need an effective EDB1.
Recovery product to repair and restore it.Use your last online backup to restore the
For example, you might encounter the below eventInformation Store databases
logging into application log of Exchange Server after2.
failing in attempts of backing up the InformationTry to move mailboxes to another store if you are
Store:using Enterprise edition of Exchange Server 2000 or
Event Type: Error2003
Event Source:ESE3.
Event Category:Logging/RecoveryIf none of the above solution is applicable, try to
Event ID: 217repair the database. To do so, you need to use
Date:10/25/2007eseutil /p repair command and then eseutil /d
Time:12:15:31 PMcommand to defragment the database. But the
User:N/Acommand deletes the pages that it finds as
Computer:EXCHANGEcorrupted. For safe database repair, you should run
Description:EDB Recovery Software that use safe algorithms to
Information Store (5484) First Storage Group: Errorrestore damaged Exchange databases.
(-613) during backup of a database (file D:\ProgramEDB Recovery utilities are high-end applications with
Files\Exchsrvr\mdbdata\priv1.stm). The database willinteractive design that provide complete database
be unable to restore.repair results. These software are highly reliable and
The error is usually accompanied with event 478.require no prior technical skills to operate them.
Cause