HrESEBackupEnd failed

[Ourcup]

Posted in Exchange 2000 & ARCserve2000 forums
=============================================

Hi All,

Error occurs when backing up Information Store.

System is Win2k with ARCserve2000+SP4+Hotfixes

NOTE: This apparently undocumented error has only occured after migrating mailboxes (there & back again) to recover whitespace. Will be running ESEUTIL /G tonight to check integrity but if anyone has any input we'd be grateful.

Also, data appears to be backed up successfully but we do not have resource to test a restore on spare machine to verify integrity.

Cheers,
Ourcup


------------
Full Error:
[E8604 Failed to start backup. (DBNAME=First Storage Group, EC=Backup Agent Error -- (362) "Exchange Server Error. HrESEBackupEnd failed. Check Backup Agent Activity Log".) ]
------------------
dbaexch.log shows:

First Storage Group in Full Backup Mode
Exchange Server Message -- Unknown
Exchange Server Message -- Error returned from an ESE function call (-1003)

First Storage Group removed from Backup Mode

Exchange Server Message -- The parameter is not valid
Exchange Server Error. HrESEBackupEnd failed. Check Backup Agent Activity Log

Backup Agent Error -- (362) "Exchange Server Error. HrESEBackupEnd failed. Check Backup Agent Activity Log
--------------------

 

[xenotec]

I believe that there would be corruption in the information store.
Check the Event logs for errors on ESE
Save the backup job as a script file
Stop ARCserve services
Delete the ARCserve$\00000001.QSD directory
Open the registry and check the following
Run regedt32, go to HKLM\Software\ComputerAssociates\ARCserveIT\DSAgent\CurrentVersion\Agent\DBAXCHG2\InBackup
Check to see that the InBackup value is set to 0

 

[mohamdr]

To isolate the cause of the problem I would suggest to try to backup Exchnage IS using NTBackup .

 

[Ourcup]

Thanks for the posts.
Corruption of the Information Store has been identified by ESEUTIL /G.
Fortunately we do have a copy of the database prior to running ESEUTIL /D for the defrag.
Not sure about the wisdom of running 10 days of transaction logs though!
I think the lesson here is to check the integrity before copying the database back ;-)