Vmware or Hyper-v App GRT backup of Exchange virtual machine fails with "Recovery FAILED - ERROR::RC = -582 - "

Article:TECH202212  |  Created: 2013-01-29  |  Updated: 2013-07-23  |  Article URL http://www.symantec.com/docs/TECH202212
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Vmware or Hyper-v agent App GRT backup of Exchange 2007/2010 fails with "Recovery FAILED - ERROR::RC = -582 - <n/a>".  The issue can appear when App GRT attempts to protect the Mailbox databases and Public folders.


Backup Exec was unable to prepare Microsoft Exchange resources for Granular Recovery Technology (GRT) operations. Therefore you will be unable to perform GRT-enabled restores of Microsoft Exchange data for '\\server\Microsoft Information Store\Mailbox Database' from this backup.


Backup Exec has discovered and protected Microsoft Exchange Server data on virtual machine 'ServerName.DomainName'.
Backup Exec has discovered and protected Microsoft Exchange Server data on virtual machine 'ServerName.DomainName'.
Backup Exec has discovered and protected Microsoft Exchange Server data on virtual machine 'ServerName.DomainName'.



Backup Exec 2012

Vmware or Hyper-v Agent (App GRT)

Exchange 2007/2010




Backup Exec remote agent Debug Log:


[2468] 2013-01-30T14:35:52.270 [fsys\jet]           - STARTING RESTORE MAP:
 SOURCE PATH:  C:\Program Files\Symantec\Backup Exec\Data\IMG000001
 TARGET PATH:  C:\Program Files\Symantec\Backup Exec\Data\IMG000001
[2468] 2013-01-30T14:35:52.270 [fsys\jet]           - RSTMAP[0] -  >>>> C:\Program Files\Symantec\Backup Exec\Data\IMG000001\Mailbox Database.edb
[2468] 2013-01-30T14:35:52.315 [fsys\jet]           - Restore SES=0x0,         Unknown: 0% (543301/183304344) Time Elapsed: 1363:16.784
[2468] 2013-01-30T14:36:09.265 [fsys\jet]           - Restore SES=0x0,          Failed: 100% (100/100) Time Elapsed: 1363:33.725
[2468] 2013-01-30T14:36:09.274 [fsys\jet]           - ### [DbInstance::RecoverDb] - JetInit3 ... (-582)
[2468] 2013-01-30T14:36:09.274 [fsys\jet]           - Recovery FAILED - ERROR::RC = -582 - <n/a>
[2468] 2013-01-30T14:36:09.274 [fsys\mb2]           - OPEN DATABASE FAILED: <n/a>
[2468] 2013-01-30T14:36:09.274 [fsys\mb2]           - MB2_Chgdir:Logon returned e000fea9
[2468] 2013-01-30T14:36:09.274 [fsys\ntfs\img_pdi]  + img_pdi_chgdir.cpp (581):
[2468] 2013-01-30T14:36:09.274 [fsys\ntfs\img_pdi]  | Error (0xe000fea9) calling FS_ChangeDir: 'Mailbox Database'




Backup the Exchange resources via RAWS (Remote Agent) instead of using APP GRT through AVVI or Hyper-v Agent.


Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see 
http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

NOTE: Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.


Supplemental Materials


App GRT backup of Exchange 2007 fails with "Recovery FAILED - ERROR::RC = -582 - <n/a>"

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

Terms of use for this information are found in Legal Notices