Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup Exec Agent for Windows crashes on edbprov.dll during an Exchange Granular Recovery Technology (GRT) restore (Backup Exec 2010)

Created: 21 Jan 2014 • Updated: 28 Jan 2014 | 9 comments
This issue has been solved. See solution.

Hi,

I seem to be having the exact same problem that is documented on http://www.symantec.com/business/support/index?pag..., but using Backup Exec 2010 R3 SP3 on Windows 2008-AMD64, with recent windows updates installed are installed.

I am trying to do a redirected restore of an exchange mailbox to an empty mailbox (Exchange 2010 SP3).

The restore job fails after about 80MB with the following errors:

Restore- \\XXX\Microsoft Information Store\XXXMBX1 XXXV-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled.
 
RestoreV-79-57344-65072 - Connection to the restore target has been lost.  Operation canceled.
 
A selection on device \\XXX\Microsoft Information Store\lamant temp was skipped because of previous errors with the job.
 
Final error: 0xe000ff12 - A communications failure has occurred with an Exchange Store resource.
Final error category: Resource Errors

Additionally, the Backup Exec Remote Agent crashed on the media/backup exec server:

Application défaillante beremote.exe, version 13.0.5204.1225, horodatage 0x51e07830, module défaillant edbprov.dll, version 13.0.5204.1225, horodatage 0x51e077fc, code d’exception 0xc0000005, décalage d’erreur 0x0000000000033d53, ID du processus 0x1b28, heure de début de l’application 0x01cf16a4f2354b1a.

A crash dump gets generated and is available upon request.

The logon account used for the restore has all the required permissions (local admin on exchange server, dedicated mailbox, organization RBAC role, etc..).

When I log into the target mailbox, I can see some of the restored mails.

Is this problem known on Backup Exec 2010 and if so, any advice on how to overcome said issue?

Thank you very much

Operating Systems:

Comments 9 CommentsJump to latest comment

lmosla's picture

Are you restoring from tape or disk?  If from tape try a duplicate to disk.

pkh's picture

Removable B2D folders are meant for things like RDX drives.  If you are using a USB/eSata disk, then you should be using the normal B2D folder.

Create a B2D folder on your internal disk, duplicate the backup set over to this B2D folder and try the restore again.

VJware's picture

You are probably facing this known issue for BE 2010 - http://www.symantec.com/business/support/index?pag...

See if the workaround helps and I would recommend to log a formal support case for us to review the crash dump.

lubou's picture

Hi,

I just tried to do a restore to a recovery mailbox databases, as suggest in on http://www.symantec.com/business/support/index?page=content&id=TECH205932, but no luck.

Restore- \\XXX\Microsoft Information Store\Recovery XXXV-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled.
 
RestoreV-79-57344-65072 - Connection to the restore target has been lost.  Operation canceled.
 
beremote.exe crashed on the media server, too.
 
Application défaillante beremote.exe, version 13.0.5204.1225, horodatage 0x51e07830, module défaillant edbprov.dll, version 13.0.5204.1225, horodatage 0x51e077fc, code d’exception 0xc0000005, décalage d’erreur 0x0000000000033d53, ID du processus 0xe10, heure de début de l’application 0x01cf174f32f2984b.
 
I opened a support case provided the crash dump.
Thanks for the help
CraigV's picture

...have you tried to restore the Exchange Information Store by duplicating to disk first? If not, try so and then report back...you can read the article below if you don't know how too.

https://www-secure.symantec.com/connect/articles/restoring-exchange-or-individual-mailboxesitems-using-backup-exec-howto

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

lubou's picture

Update:

I opened a case with Symantec. 

My particular problem has been resolved in Backup Exec 2010 R3 SP4.

Thanks a lot to the engineer who worked with me to solve this problem.

http://www.symantec.com/docs/TECH208828

http://www.symantec.com/docs/TECH204409

SOLUTION