cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange 2010 Restore is failing with 2810 status

Zing
Level 3

Hi All,

I'm facing issue while restoring Exchange DB restore to same DAG and same server with below error, kindly help to provide some solution .

 

Environment :-

NetBackup Master 7.5.0.7 Windows 2k8

Media server 7.5 Windows 2k3 

Client 7.5.0.7 Windows 2k8 R2, Exchange 2010 .

 

Restore Path :-

Actual path :- Microsoft Exchange Database Availability Groups:\DAG\Microsoft Information Store\DB03\ 

Changed as below for restore:-

Microsoft Exchange Database Availability Groups:\DAG\Microsoft Information Store\RDB_NEW\

Parent Stream :-

23/03/2017 14:13:06 - begin Restore
23/03/2017 14:13:10 - Info bprd(pid=12896) starting BPRESOLVER
23/03/2017 14:13:12 - Info bprd(pid=12896) BPRESOLVER has executed on server (xxxxx)
23/03/2017 14:15:25 - end Restore; elapsed time: 00:02:19
the restore failed to recover the requested files(5)

 

Child Stream:-

2223/03/2017 14:13:29 - begin Restore
23/03/2017 14:13:31 - media 0288L5 required
23/03/2017 14:13:31 - restoring image DAG_1488062678
23/03/2017 14:13:38 - Info bprd(pid=3244) Restoring from copy 1 of image created 02/25/17 22:44:38
23/03/2017 14:13:41 - Info bpbrm(pid=9496) XXXXX is the host to restore to
23/03/2017 14:13:41 - Info bpbrm(pid=9496) reading file list from client
23/03/2017 14:13:46 - connecting
23/03/2017 14:13:46 - Info bpbrm(pid=9496) starting bptm
23/03/2017 14:13:56 - Info tar32(pid=14680) Restore started
23/03/2017 14:13:56 - connected; connect time: 00:00:10
23/03/2017 14:13:56 - Info bptm(pid=12064) start
23/03/2017 14:13:56 - started process bptm (12064)
23/03/2017 14:13:56 - Info bpdm(pid=12064) reading backup image
23/03/2017 14:13:56 - Info bptm(pid=12064) using 64 data buffers
23/03/2017 14:13:56 - Info bptm(pid=12064) spawning a child process
23/03/2017 14:13:56 - Info bptm(pid=12064) child pid: 8444
23/03/2017 14:13:56 - Info bptm(pid=8444) start
23/03/2017 14:13:56 - started process bptm (8444)
23/03/2017 14:13:58 - requesting resource 123456
23/03/2017 14:13:58 - granted resource 123456
23/03/2017 14:13:58 - granted resource HP.ULTRIUM5-SCSI.007
23/03/2017 14:13:59 - mounted
23/03/2017 14:13:59 - Info bptm(pid=12064) XXXX
23/03/2017 14:14:01 - Info bptm(pid=12064) INF - Waiting for positioning of media id 0288L5 on server xxxxx for reading.
23/03/2017 14:14:01 - positioning 123456 to file 337
23/03/2017 14:15:09 - positioned 123456; position time: 00:01:08
23/03/2017 14:15:11 - begin reading
23/03/2017 14:15:17 - Info bptm(pid=12064) waited for empty buffer 1 times, delayed 1 times
23/03/2017 14:15:17 - end reading; read time: 00:00:06
23/03/2017 14:15:17 - Info bptm(pid=12064) completed reading backup image
23/03/2017 14:15:17 - Info bptm(pid=12064) EXITING with status 0 <----------
23/03/2017 14:15:24 - Error bpbrm(pid=9496) from client XXXXX ERR - Aborting restore: Error writing Exchange object: Microsoft Exchange Database Availability Groups:\DAG\Microsoft Information Store\RDB_NEW\Logs_1487988957 Error: BEDS 0x0:
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status 5
23/03/2017 14:15:24 - restored image DAG_1488062678 - (tar did not find all the files to be restored(185)); restore time 00:01:53
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status: 185
23/03/2017 14:15:24 - Info tar32(pid=14680) done. status: 185: tar did not find all the files to be restored
23/03/2017 14:15:24 - Error bpbrm(pid=9496) client restore EXIT STATUS 185: tar did not find all the files to be restored
23/03/2017 14:15:25 - end Restore; elapsed time: 00:01:56
MS-Exchange-Server policy restore error(2810)

2 REPLIES 2

MateuszK
Level 3

Hi Zing,

Have you read this article?

https://www.veritas.com/support/en_US/article.000010827

And also you can check logs from: (it should show more details)

/usr/openv/netbackup\logs\user_ops\(username that did restore)\logs 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Hopefully @Zing came right in the meantime.

He/she has not been back in 2 weeks...

This seems to be a duplicate post. See:
https://vox.veritas.com/t5/NetBackup/Exchange-Restore-is-failing-with-2810-status/m-p/828416