Welcome to YLOAN.COM
yloan.com » Data Recovery » Event 217 And 478 While Backing Up Exchange Database
Games Personal-Tech Data Entry registry cruise torrent mac code virus storage uninstaller systems cisco bugs wireless codes maintenance dell update communication trojan atlanta Data Backup Data Storage Data Protection Data Recovery Anti-Virus Windows Linux Software Hardware Mobil-Computing Certification-Tests Computers & Internet Internet

Event 217 And 478 While Backing Up Exchange Database

Exchange Server storage groups and databases are the most vital component of recovery when the server crashes

. You might observe typical symptoms with a corrupted Exchange database. For instance, you may fail to backup it. When it occurs, the corresponding event indicating the failure is logged in application event log, which helps you to deduce the cause. However, a corrupted Exchange database should be restored from backup. In case of unavailability of backup, you need an effective EDB Recovery product to repair and restore it.

For example, you might encounter the below event logging into application log of Exchange Server after failing in attempts of backing up the Information Store:

Event Type: Error

Event Source:ESE


Event Category:Logging/Recovery

Event ID: 217

Date:10/25/2007

Time:12:15:31 PM

User:N/A

Computer:EXCHANGE

Description:

Information Store (5484) First Storage Group: Error (-613) during backup of a database (file D:Program FilesExchsrvrmdbdatapriv1.stm). The database will be unable to restore.

The error is usually accompanied with event 478.

Cause

Event 217 typically indicates backup failure and event 478 shows database corruption due to hardware issues. Event 217 might also be encountered due to Exchange beyond EOF (End Of File) condition.

Solution

Make sure you install all the latest updates and hotfixes available for your Exchange Server. To correct the corrupted database issues, you should perform steps, as follows:

1.Use your last online backup to restore the Information Store databases

2.Try to move mailboxes to another store if you are using Enterprise edition of Exchange Server 2000 or 2003

3.If none of the above solution is applicable, try to repair the database. To do so, you need to use eseutil /p repair command and then eseutil /d command to defragment the database. But the command deletes the pages that it finds as corrupted. For safe database repair, you should run EDB Recovery Software that use safe algorithms to restore damaged Exchange databases.

EDB Recovery utilities are high-end applications with interactive design that provide complete database repair results. These software are highly reliable and require no prior technical skills to operate them.

Stellar Phoenix Mailbox Exchange Recovery is a powerful tool that provides systematic Exchange database repair. It is a secure EDB Recovery Software that supports Exchange Server 5.5, 2000 and 2003. The tool can restore mailboxes in individual .pst files, which can be directly accessed in Outlook. The software is enriched with a realistic approach to repair corrupted EDB file in each instance.

by: axel culver
Do You Understand The Importance Of Account Details Like We Do? Many Users Should Keep In Memory How To Repair Corrupted .mdb Files Recovery Toolbox For Rar Is The Easiest Rar Header Corrupt Fix That You Have Eve How To Repair Corrupt .doc File Errors While Downloading Zip File With Internet Explorer 6 This Program Works With Affected Databases, Created In Foxpro, Clipper And Some Damage To Hard Drive Structure Doesn't Allow You To Delete Files In Windows Nanny Pay Rates - Updated 2010 Caregiver Rate Database! Rehab Clinic Recovery Toolkit For Suffering Addicts Pcb/logic Board Damage In A Laptop Inability Of Compact.exe Tool To Compress File System Cause Data Loss In Windows Partitions Inaccessibile After Server Exception Error In Windows 2000 How To Begin Your Recovery From Alcoholism
print
www.yloan.com guest:  register | login | search IP(18.117.158.108) Georgia / Atlanta Processed in 0.008092 second(s), 7 queries , Gzip enabled , discuz 5.5 through PHP 8.3.9 , debug code: 44 , 2849, 165,
Event 217 And 478 While Backing Up Exchange Database Atlanta