Exchange Restore Fail with status 2018

[junka]

Hi when attemp to restore an exchage database exit with status 2018

thanks for you help!!

logs for the job

10/17/2016 3:44:32 PM - begin Restore

10/17/2016 3:44:37 PM - media 4050L4 required

10/17/2016 3:44:37 PM - restoring image ogpexchmbx_1419698324

10/17/2016 3:44:41 PM - Info bprd(pid=4796) Restoring from copy 2 of image created 12/27/14 12:38:44   

10/17/2016 3:44:43 PM - Info bpbrm(pid=6072) ogpexchmbx is the host to restore to     

10/17/2016 3:44:43 PM - Info bpbrm(pid=6072) reading file list from client       

10/17/2016 3:44:46 PM - connecting

10/17/2016 3:44:46 PM - Info bpbrm(pid=6072) starting bptm          

10/17/2016 3:45:59 PM - Info tar32(pid=6616) Restore started          

10/17/2016 3:45:59 PM - connected; connect time: 00:01:13

10/17/2016 3:45:59 PM - Info bptm(pid=6208) start           

10/17/2016 3:45:59 PM - started process bptm (6208)

10/17/2016 3:45:59 PM - Info bpdm(pid=6208) reading backup image         

10/17/2016 3:46:00 PM - Info bptm(pid=6208) using 1024 data buffers        

10/17/2016 3:46:00 PM - Info bptm(pid=6208) spawning a child process        

10/17/2016 3:46:00 PM - Info bptm(pid=6208) child pid: 6036         

10/17/2016 3:46:00 PM - Info bptm(pid=6036) start           

10/17/2016 3:46:00 PM - started process bptm (6036)

10/17/2016 3:46:01 PM - Info bptm(pid=6208) Waiting for mount of media id 4050L4 (copy 2) on server ogp18126.

10/17/2016 3:46:01 PM - started process bptm (6208)

10/17/2016 3:46:01 PM - mounting 4050L4

10/17/2016 3:46:01 PM - Info bptm(pid=6208) INF - Waiting for mount of media id 4050L4 on server ogp18126 for reading.

10/17/2016 3:46:01 PM - requesting resource 4050L4

10/17/2016 3:46:01 PM - granted resource 4050L4

10/17/2016 3:46:01 PM - granted resource HP.ULTRIUM4-SCSI.001

10/17/2016 3:47:20 PM - mounted; mount time: 00:01:19

10/17/2016 3:47:20 PM - Info bptm(pid=6208) 4050L4           

10/17/2016 3:47:20 PM - Info bptm(pid=6208) INF - Waiting for positioning of media id 4050L4 on server ogp18126 for reading.

10/17/2016 3:47:20 PM - positioning 4050L4 to file 140

10/17/2016 3:51:26 PM - positioned 4050L4; position time: 00:04:06

10/17/2016 3:51:26 PM - begin reading

10/17/2016 3:51:26 PM - Info bptm(pid=6208) waited for empty buffer 0 times, delayed 0 times   

10/17/2016 3:51:26 PM - Info bptm(pid=6208) INF - Waiting for positioning of media id 4050L4 on server ogp18126 for reading.

10/17/2016 3:51:26 PM - positioning 4050L4 to file 167

10/17/2016 3:52:28 PM - positioned 4050L4; position time: 00:01:02

10/17/2016 3:52:43 PM - begin reading

10/17/2016 3:52:50 PM - Info bptm(pid=6208) waited for empty buffer 0 times, delayed 0 times   

10/17/2016 3:52:50 PM - end reading; read time: 00:00:07

10/17/2016 3:52:50 PM - positioning 4050L4 to file 168

10/17/2016 3:52:50 PM - positioned 4050L4; position time: 00:00:00

10/17/2016 3:52:50 PM - begin reading

10/17/2016 3:52:55 PM - Error bpbrm(pid=6072) from client ogpexchmbx: ERR - Aborting restore: Error writing Exchange object: Microsoft Information Store:\RDB2\ Error: BEDS 0x0:

10/17/2016 3:52:55 PM - Error bptm(pid=6036) cannot write data to socket, 10054      

10/17/2016 3:52:55 PM - Info tar32(pid=6616) done. status 5         

10/17/2016 3:52:55 PM - Info tar32(pid=6616) done. status: 185         

10/17/2016 3:52:55 PM - Info bptm(pid=6208) EXITING with status 24 <----------       

10/17/2016 3:52:55 PM - Info tar32(pid=6616) done. status: 24: socket write failed      

10/17/2016 3:52:55 PM - Error bpbrm(pid=6072) client restore EXIT STATUS 24: socket write failed    

10/17/2016 3:52:55 PM - restored image ogpexchmbx_1419698324 - (socket write failed(24)); restore time 00:08:18

10/17/2016 3:52:56 PM - end Restore; elapsed time: 00:08:24

MS-Exchange-Server policy restore error(2810)

[Michael_G_Ander]

Have never seen a status 2018, but this line:

Error bpbrm(pid=6072) from client ogpexchmbx: ERR - Aborting restore: Error writing Exchange object: Microsoft Information Store:\RDB2\ Error: BEDS 0x0:

seem to indicate a problem with writing to the exchange database, normally you cannot write directly to exchange databases for good reasons. Get your exchange administrator to either create a recovery database or make sure that the RDB2 database is writable. If the RDB2 is a recovery database, it is probably a permission issue.

See the Netbackup Exchange Admin Guide for more information, about permissions and restore scenarios

[backupadminnbu]

i had same issue and its failed becuase when we select the DB for restore from BAR console , if you select the entire DB from left side panel it will try to create new DB inside your Recovery DB "RDB2" ( i.e Microsoft Information Store:\RDB2\<DB from Restore>\ .

Just select the db and log files from right hand side and restore to recovery DB , it will work .

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

[junka]

Sorry is status 2810

thanks for your reply i check later and post the results

[Lowell_Palecek]

@backupadminnbu- that's just not true, and the link is about restoring to an Exchange 2007 RSG. I recommend to users to select the database on the left panel of the GUI in order to make sure you don't leave anything out. If you had a restore try to create a DB within your RDB, you probably mis-typed your redirection path, and when you did it again selecting on the right, you probably got the redirection path right.

As to the error message about failure to write to the RDB, that's not because you were restoring to a wrong target. You need to look at the tar log to see why it failed. The job details only tell you where to start looking. Without the tar log, I can give general reasons why such a failure occurs:

- The RDB has already been mounted, or used. You create an RDB via PowerShell and don't mount it. Then you use it once only as the target of the restore.

- The RDB doesn't have the option set, "This database can be overwritten by a restore."

[Lowell_Palecek]

Also, status 2810 is just generic for "You Exchange restore failed." Tar32 produces status 5, and the server translates that to 2810.