GRT enabled Incremental backups of Exchange 2010 DAG fails with "Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information."

Article:TECH186423  |  Created: 2012-04-13  |  Updated: 2014-02-05  |  Article URL http://www.symantec.com/docs/TECH186423
Article Type
Technical Solution


Issue



GRT enabled Incremental backups of Exchange 2010 DAG fails with "Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information."


Error



Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-915
Errors
Click an error below to locate it in the job log
Backup- \\DAG\Microsoft Information Store\DB name  V-79-57344-915 - Unable to complete the operation for the selected resource using the specified options.  The following error was returned when opening the Exchange Database file:
'-1022 There is a disk IO error.' 

The beremote logs from Media server shows the following error entries:
================================================================================
ReadFile failed, lastError = 00000006, The handle is invalid.
[5384] 04/02/12 19:30:33 Aborted state machine
[6208] 04/02/12 19:30:36 For Virt VFF id (6208-00001840), Total Bytes
Read=00000001:167E9000, Written=00000001:1946E000
[8556] 04/02/12 19:31:04 [fsys\jet]           - Recovery FAILED - ERROR::RC = -
1022 - -1022 There is a disk IO error.
[8556] 04/02/12 19:31:04 Closing Persistent Virt VFF id (8348-0000209C) with:
Total Bytes Read=00000000:162B9000, Written=00000000:13928000
[8556] 04/02/12 19:31:04 Closing Session [ThreadId=8348, Major=0, Minor=0,
Index=0, Last=00000000].
[8556] 04/02/12 19:31:04 SessionStatus for [28444-00006F1C] - Major=0, Minor=0,
Index=0, LastError=0, Session is not uActiveB.
[8556] 04/02/12 19:31:04 Closing Vlink VFF id (5384-00001508) with: Total Bytes
Read=00000000:0BFA2000, Written=00000000:00000000
[8556] 04/02/12 19:31:04 Closing Session [ThreadId=5384, Major=0, Minor=0,
Index=0, Last=00000006].
[8556] 04/02/12 19:31:04 SessionStatus for [8364-000020AC] - Major=0, Minor=0,
Index=0, LastError=0, Session is not uActiveB.
[8556] 04/02/12 19:31:04 [fsys\mb2]           - Using EDB Provider for Browse/Backup.
[8556] 04/02/12 19:31:04 [fsys\mb2]           - Logon: m_lpMAPISession->Logon returned 80004005
[8556] 04/02/12 19:31:04 [fsys\mb2]           -           OPEN DATABASE FAILED: -1022 There is a disk IO error.
[8556] 04/02/12 19:31:04 [fsys\mb2]           - MB2_Chgdir:Logon returned e000fea9
================================================================================


Solution



A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

Backup Exec 2010R3 Rev 5204 Service Pack 3 (TECH203157)
Backup Exec 2012 Rev 1798 Service Pack 2 (TECH203155)
 


Supplemental Materials

SourceETrack
Value2748526
Description

EXCH: GRT Enabled Incremental backups of Exchange 2010 DAG fails with "Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information."


SourceError Code
Value0xe0000393
Description

Cannot extract mailbox messages from the Exchange backup. Review the job log for more information


SourceUMI
ValueV-79-57344-915
Description

Unable to complete the operation for the selected resource using the specified options.  The following error was returned when opening the Exchange Database file:  '-1022 There is a disk IO error.'
 


SourceETrack
Value2904862
Description

EXCH: GRT enabled Incremental backups of Exchange 2010 DAG fails with "Final error: 0xe0000393 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information." (Honshu)




Article URL http://www.symantec.com/docs/TECH186423


Terms of use for this information are found in Legal Notices