subject: 613 Message And You Cannot Back Up Exchange Server [print this page] Taking backup of updated database in certain intervals keeps the backup copy updated and for that reason online backup procedures have been put into practice by Exchange server administrators.
Sometimes the online backup process may get interrupted due to occurrence of 613 error. You can see events in event log, which may be similar to following event:
Event Type: Error
Event Source: ESE
Event Category: (3)
Event ID: 217
Description:
Information Store (1812) e85d4e03-5bb3-44c5-bd2f-1343972a1b1a: Error (-613) during backup of a database (file D:ProgrammeExchsrvrmdbdatapriv1.stm). The database will be unable to restore.
Reasons of the problem:
This problem can occur due to any of the following reasons:
Hardware related issue on the computer where Exchange server is installed.
Issues related with third party applications installed on Exchange server computer.
Solution:
The process of resolving 613 error can be performed in two steps:
Determining the cause of problem
Before trying out any solution, it is essential to determine the root cause of the problem. As mentioned earlier, this problem can occur due to hardware or third part application issue of Exchange server computer therefore, you should first determine the exact cause. To determine the root cause of the problem you can check the system log or run Chkdsk or perform various diagnostic tasks.
Performing successful backup process
To perform successful backup of Exchange server, you can use any of the below mentioned methods:
If the issue is caused due to third party application, then contact the third party company to resolve the problem.
Restore the information store from the previous online backup.
If the mailbox store is affected and you have an Enterprise version of Exchange 2000 or Exchange 2003, move the mailboxes to another server or mailbox store.
If the public folder store is affected, replicate the content of the public folders to another server.
If database pages are corrupt and you do not have a valid backup and you are running the standard version of Exchange 2000 or Exchange 2003, run the eseutil /p command, run the eseutil /d command, and then run the isinteg -fix command on the affected store.
Using above mentioned methods you can successfully backup your Exchange server and can get prepared for unexpected corruption situations. If you face Exchange server corruption and are unable to deal with it, you can take help of Exchange Disaster Recovery software that efficiently extracts mailboxes from Exchange server database and rebuilds the database.
