Exchange2010 Recovery Fails with status 24, 185 and 10054

Question

Hello.&nbsp;

Im trying to restore a Exchange2010 database. Getting this error.

Master server: win2k8 &nbsp;with Netbackup Admin console 7.6.0.1

Win2k8 server with the&nbsp;RDB database on -&nbsp;Netbackup client 7.6.0.1

Selecting Point in time recovery - then adressing it to&nbsp;Microsoft Information Store:\RDB

&nbsp;

I have tryed to restore from tape and disk. Same result. I have also tryed diffrent MB&nbsp; ( MB01 - MB10 ), no go.&nbsp;
	
	Any tips i can try? &nbsp; I have run this successfully before with no errors. 4-6 months ago. &nbsp;i have tryed to look up any changes in our envirement but can`t find any changes from last time i did a MB restore....&nbsp;&nbsp;

&nbsp;

05.05.2015 14:17:05 - begin Restore
	05.05.2015 14:17:08 - restoring image dag01-Kjeller_1430695087
	05.05.2015 14:17:18 - Info bprd(pid=8836) Restoring from copy 1 of image created 05/04/15 01:18:07 from policy APT-Exchange2010-MB03&nbsp;
	05.05.2015 14:17:21 - Info bpbrm(pid=4596) APREMSRESTORE01 is the host to restore to &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:21 - Info bpbrm(pid=4596) reading file list for client &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:23 - connecting
	05.05.2015 14:17:23 - Info bpbrm(pid=4596) starting bptm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:29 - Info tar32(pid=4596) Restore started &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:29 - connected; connect time: 0:00:06
	05.05.2015 14:17:29 - Info bptm(pid=4324) start &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:29 - started process bptm (4324)
	05.05.2015 14:17:29 - Info bptm(pid=4324) reading backup image &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:29 - Info bptm(pid=4324) using 30 data buffers &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:29 - Info bptm(pid=4324) spawning a child process &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:29 - Info bptm(pid=4324) child pid: 5792 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:29 - Info bptm(pid=5792) start &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:29 - started process bptm (5792)
	05.05.2015 14:17:32 - begin reading
	05.05.2015 14:17:34 - Error bptm(pid=5792) cannot write data to socket, 10054 &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:34 - Info tar32(pid=4596) done. status: 185 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:35 - Error bptm(pid=5792) The following files/folders were not restored: &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:36 - Error bptm(pid=5792) UTF - /Microsoft Exchange Database Availability Groups/dag01-Kjeller/Microsoft Information Store/DAG01-Kjeller-MB03/Database &nbsp; &nbsp;
	05.05.2015 14:17:36 - Error bptm(pid=5792) UTF - /Microsoft Exchange Database Availability Groups/dag01-Kjeller/Microsoft Information Store/DAG01-Kjeller-MB03/Logs_1430695040 &nbsp; &nbsp;
	05.05.2015 14:17:36 - Info bptm(pid=4324) EXITING with status 24 &lt;---------- &nbsp; &nbsp; &nbsp; &nbsp;
	05.05.2015 14:17:36 - Info tar32(pid=4596) done. status: 24: socket write failed &nbsp; &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:36 - Error bpbrm(pid=4596) client restore EXIT STATUS 24: socket write failed &nbsp; &nbsp;&nbsp;
	05.05.2015 14:17:37 - restored image dag01-Kjeller_1430695087 - (socket write failed(24)); restore time 0:00:29
	05.05.2015 14:17:42 - end Restore; elapsed time: 0:00:37
	MS-Exchange-Server policy restore error(2810)

marianne · Accepted Answer

I have not downloaded the logs as yet. ( I have a personal bugbear with download of compressed files.)

I have just remembered something that one of my colleagues experienced a couple of months ago.

It was a bug specifically introduced in NBU 7.6.0.1.&nbsp;
	Extract from case notes:

This seems to be an issue with NBU and has been resolved in NBU 7.6.0.2.
		Please refer TN - http://www.symantec.com/docs/TECH196858 (ET3459506)
		
		Hence Please upgrade Client on all Exchange servers to 7.6.0.2, then rerun the restore again.
		&nbsp;

Best to upgrade to latest NBU 7.6.0.x version (7.6.0.4).&nbsp;
	Bear in mind that a client can be higher point patch version that master and/or media server.
	Link to all downloads:&nbsp;http://www.symantec.com/docs/TECH65429&nbsp;

sdo · Answer

The Recovery DB was definitely set to&nbsp;'Allow restores to overwrite this database' ? &nbsp;And was in an un-mounted state?

Are you following a previously documented&nbsp;procedure which was previously tested, and which is now failing? &nbsp;Or are you just trying to remember how to do it on the fly?

marianne · Answer

Can you backup and restore normal filesystem-level files and/or folders on this client?

This will tell us if the issue is with Exchange or if there is a network-related issue.

Create the following folders for further troubleshooting:

On client: tar

On media server: bptm and bpbrm

Increase logging level on media server and client to 3 before trying another restore.

ontherocks · Answer

Try with below links ::

Restoring Exchange 2010 Database Availability Group (DAG) Backups to a Recovery Database (RDB) using NetBackup 7.0&nbsp;

&nbsp;

Performing an Exchange 2010 Database Restore to a Database Availability Group (DAG) with NetBackup 7.0&nbsp;

&nbsp;

Mention in the destination in below syntax and try the restore ::

Microsoft Exchange Database Availability Groups:\dag\Microsoft Information Store\RecoveryDB\

kristoffer_lie · Answer

SDO: &nbsp;Yes, i just created the RDB for this job. I allways create a new RDB for each restore and formating the drive before creating the RDB so the drive is like New&nbsp;( so i dont mess up some other stuf ;) ) &nbsp;
	The RDB is unmounted. &nbsp; I am using a guide that we have made and tested OK before. I have used it many times with no problems.&nbsp;

ONTHEROCKS: &nbsp;Your links dont work? &nbsp;( or is it just me? )
	There is no article that matches your request.....

Marianne: &nbsp;I did a regular File/Folder Backup and restore now with NO problems. Backup did fine, restore was OK and fine.

I am creating the requested folders now and i will report back shortly after the logs/job has finished.&nbsp;

&nbsp;

kristoffer_lie · Answer

Here are my log files. &nbsp;Pleace tell me if i did something wrong or you need more info.

Forum Discussion

Exchange2010 Recovery Fails with status 24, 185 and 10054

12 Replies

Related Content

exit status 140

Netbackup Catalog Recovery

Exchange2010 backup missing mailbox's

Veritas System Recovery 18 - Recovery point set "Greyed Out"

disaster recovery passphrase

Recent Discussions

"failed, status 6" error after increasing datastore (LUN) capacity

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC