cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange2010 Recovery Fails with status 24, 185 and 10054

Kristoffer_Lie
Level 4

Hello. 

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

Master server: win2k8  with Netbackup Admin console 7.6.0.1

Win2k8 server with the RDB database on - Netbackup client 7.6.0.1

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

 

I have tryed to restore from tape and disk. Same result. I have also tryed diffrent MB  ( MB01 - MB10 ), no go. 

Any tips i can try?   I have run this successfully before with no errors. 4-6 months ago.  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....  

 

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 
05.05.2015 14:17:21 - Info bpbrm(pid=4596) APREMSRESTORE01 is the host to restore to      
05.05.2015 14:17:21 - Info bpbrm(pid=4596) reading file list for client        
05.05.2015 14:17:23 - connecting
05.05.2015 14:17:23 - Info bpbrm(pid=4596) starting bptm           
05.05.2015 14:17:29 - Info tar32(pid=4596) Restore started           
05.05.2015 14:17:29 - connected; connect time: 0:00:06
05.05.2015 14:17:29 - Info bptm(pid=4324) start            
05.05.2015 14:17:29 - started process bptm (4324)
05.05.2015 14:17:29 - Info bptm(pid=4324) reading backup image          
05.05.2015 14:17:29 - Info bptm(pid=4324) using 30 data buffers         
05.05.2015 14:17:29 - Info bptm(pid=4324) spawning a child process         
05.05.2015 14:17:29 - Info bptm(pid=4324) child pid: 5792          
05.05.2015 14:17:29 - Info bptm(pid=5792) start            
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       
05.05.2015 14:17:34 - Info tar32(pid=4596) done. status: 185          
05.05.2015 14:17:35 - Error bptm(pid=5792) The following files/folders were not restored:       
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    
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    
05.05.2015 14:17:36 - Info bptm(pid=4324) EXITING with status 24 <----------        
05.05.2015 14:17:36 - Info tar32(pid=4596) done. status: 24: socket write failed       
05.05.2015 14:17:36 - Error bpbrm(pid=4596) client restore EXIT STATUS 24: socket write failed     
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)

2 ACCEPTED SOLUTIONS

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

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. 
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.

 


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

View solution in original post

Kristoffer_Lie
Level 4

SOLUTION!
Upgrade to 7.6.0.4.

Upgraded to 7.6.0.4 on all servers ( master and media + client )
Restarted all servers ( master and media + client )
Running client BAR as admin, trying restore = OK!




07.05.2015 01:04:44 - Info bprd(pid=8676) Restoring from copy 1 of image created 04/22/15 00:13:52 from policy APT-Exchange2010-MB01 
07.05.2015 01:04:48 - Info bpbrm(pid=4196) APREMSRESTORE01 is the host to restore to      
07.05.2015 01:04:48 - Info bpbrm(pid=4196) reading file list for client        
07.05.2015 01:04:49 - connecting
07.05.2015 01:04:49 - Info bpbrm(pid=4196) starting bptm           
07.05.2015 01:04:59 - Info tar32(pid=1948) Restore started           
07.05.2015 01:04:59 - connected; connect time: 0:00:10
07.05.2015 01:04:59 - Info bptm(pid=4352) start            
07.05.2015 01:04:59 - started process bptm (4352)
07.05.2015 01:04:59 - Info bptm(pid=4352) reading backup image          
07.05.2015 01:04:59 - Info bptm(pid=4352) using 30 data buffers         
07.05.2015 01:04:59 - Info bptm(pid=4352) spawning a child process         
07.05.2015 01:04:59 - Info bptm(pid=4352) child pid: 1340          
07.05.2015 01:04:59 - Info bptm(pid=1340) start            
07.05.2015 01:04:59 - started process bptm (1340)
07.05.2015 01:05:03 - begin reading
07.05.2015 01:05:31 - Info bptm(pid=4352) waited for empty buffer 4 times, delayed 146 times    
07.05.2015 01:05:31 - end reading; read time: 0:00:28
07.05.2015 01:05:31 - Info bptm(pid=4352) completed reading backup image         
07.05.2015 01:05:31 - Info bptm(pid=4352) EXITING with status 0 <----------        
07.05.2015 05:14:01 - Info tar32(pid=1948) done. status: 0          
07.05.2015 05:14:01 - Info tar32(pid=1948) done. status: 0: the requested operation was successfully completed    
07.05.2015 05:14:02 - restored image dag01-Kjeller_1429654432 - (the requested operation was successfully completed(0)); restore time 4:09:19
07.05.2015 05:14:07 - end Restore; elapsed time: 15:44:51
the requested operation was successfully completed(0)

View solution in original post

12 REPLIES 12

sdo
Moderator
Moderator
Partner    VIP    Certified

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

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

Marianne
Level 6
Partner    VIP    Accredited Certified

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
Level 6
Partner Accredited Certified

Try with below links ::

 

 

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

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

Kristoffer_Lie
Level 4

SDO:  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 ( so i dont mess up some other stuf ;) )  
The RDB is unmounted.   I am using a guide that we have made and tested OK before. I have used it many times with no problems. 


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


Marianne:  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. 

 

 

Kristoffer_Lie
Level 4

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

ontherocks
Level 6
Partner Accredited Certified

While restoring to alternate destination you are not giving correct path :

 

Mention below as destination path in your case ::

Microsoft Exchange Database Availability Groups:\dag01-Kjeller\Microsoft Information Store\RDB

Share the result 

Kristoffer_Lie
Level 4

When i try to restore using your path i get the same error... 

Michael_G_Ander
Level 6
Certified

Does the event logs on the exchange client show anything around the time of the restoer failure that could be related ?

Could it be permissions on the drive/folders you created for the RDB ? Does the exchnage account netbackup runs as has access to the drive/folders ?

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Level 6
Partner    VIP    Accredited Certified

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. 
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.

 


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

Kristoffer_Lie
Level 4

Yes i am upgrading to 7.6.0.4 now ;)   just found a article about it myself :)   posting after update. 

Marianne
Level 6
Partner    VIP    Accredited Certified

Good luck and remember to let us know!

Kristoffer_Lie
Level 4

SOLUTION!
Upgrade to 7.6.0.4.

Upgraded to 7.6.0.4 on all servers ( master and media + client )
Restarted all servers ( master and media + client )
Running client BAR as admin, trying restore = OK!




07.05.2015 01:04:44 - Info bprd(pid=8676) Restoring from copy 1 of image created 04/22/15 00:13:52 from policy APT-Exchange2010-MB01 
07.05.2015 01:04:48 - Info bpbrm(pid=4196) APREMSRESTORE01 is the host to restore to      
07.05.2015 01:04:48 - Info bpbrm(pid=4196) reading file list for client        
07.05.2015 01:04:49 - connecting
07.05.2015 01:04:49 - Info bpbrm(pid=4196) starting bptm           
07.05.2015 01:04:59 - Info tar32(pid=1948) Restore started           
07.05.2015 01:04:59 - connected; connect time: 0:00:10
07.05.2015 01:04:59 - Info bptm(pid=4352) start            
07.05.2015 01:04:59 - started process bptm (4352)
07.05.2015 01:04:59 - Info bptm(pid=4352) reading backup image          
07.05.2015 01:04:59 - Info bptm(pid=4352) using 30 data buffers         
07.05.2015 01:04:59 - Info bptm(pid=4352) spawning a child process         
07.05.2015 01:04:59 - Info bptm(pid=4352) child pid: 1340          
07.05.2015 01:04:59 - Info bptm(pid=1340) start            
07.05.2015 01:04:59 - started process bptm (1340)
07.05.2015 01:05:03 - begin reading
07.05.2015 01:05:31 - Info bptm(pid=4352) waited for empty buffer 4 times, delayed 146 times    
07.05.2015 01:05:31 - end reading; read time: 0:00:28
07.05.2015 01:05:31 - Info bptm(pid=4352) completed reading backup image         
07.05.2015 01:05:31 - Info bptm(pid=4352) EXITING with status 0 <----------        
07.05.2015 05:14:01 - Info tar32(pid=1948) done. status: 0          
07.05.2015 05:14:01 - Info tar32(pid=1948) done. status: 0: the requested operation was successfully completed    
07.05.2015 05:14:02 - restored image dag01-Kjeller_1429654432 - (the requested operation was successfully completed(0)); restore time 4:09:19
07.05.2015 05:14:07 - end Restore; elapsed time: 15:44:51
the requested operation was successfully completed(0)