Restoring e-mail from Granular backup completes with a status 2810 and does not restore all of the Mailbox items.
Error bpbrm(pid=XXX) client restore EXIT STATUS 5: the restore failed to recover the requested files
MS-Exchange-Server policy restore error(2810)
ncfgre logs error:
0,51216,158,352,89,1401389273894,22308,19480,0:,87:FS_WriteObj() Failure! (0xE000FE2D:The backup of the item is bad.) (../Object.cpp:2589),25:Object::writeStreamData(),
In certain cases the job in the activity Monitor will fail with a status 2810 but most of the mailbox items have been restored.
This is a snip it from the Backup Archive and Restore status:
INF - GRE EXITING WITH STATUS = 0
INF - GRE RESTORED 8 OF 9 FILES SUCCESSFULLY
INF - GRE KEPT 0 EXISTING FILES
INF - GRE PARTIALLY RESTORED 0 FILES
Status of restore from copy 1 of image created 7/8/2013 12:08:34 AM = the restore failed to recover the requested files
INF - Server status = 2810
INF - Status = MS-Exchange-Server policy restore error.
The most likely reason is that the mail item is actually bad. Check whether the user can access that mail or attachment.
-- Use exmerge to make a .pst, then delete the users mailbox and then recreate the mailbox and import the mail back into Exchange. If the item cannot be imported back then there is corruption.
Apart from the situation where the item is itself corrupted, following are other some other causes for this error : (but, not necessarily limited to):
-- Anti-virus software accessing the Information Store at the same time as the backup, i.e. using the same messaging API as NetBackup does.
--Multiple levels of embedded mail messages (a message attached to a message attached to a message etc.). Remove message.
[- Error bpbrm(pid=4956) from client srswxxxx: ERR - failure reading file: Microsoft Exchange Mailboxes:\Chirag xxxxx [chirag.bhanvadia]\Top of Information Store\Inbox\Fw: FW: Amazing plz see till last .... (BEDS 0xE000FE2D: The backup of the item is bad.)]
-- Automated system messages (undeliverable, over size limit etc.).
-- Virus infected Information Store (clean for virus)
-- Very long subject lines.
-- Very long attachment names.
-- Very large attachments (might give out of resource like errors). Remove message.
-- Review this information with your Exchnage Administrator.