Previous Post Next Post

Exchange DAG Backup failing with error 24 socket write failed

Created: 02 Sep 2012 | Updated: 02 Sep 2012 | 2 comments

chandanamadhu19

08/31/2012 00:49:34 - Error bptm (pid=3404) system call failed - Connection reset by peer (at child.c.1295)
08/31/2012 00:49:34 - Error bptm (pid=3404) unable to perform read from client socket, connection may have been broken
08/31/2012 00:56:18 - Critical bpbrm (pid=3405) from client XXXXXX.service.XXX.net: FTL - socket write failed
08/31/2012 00:56:35 - Info bpbrm (pid=3394) media manager for backup id XXXXXX.service.XXX.net_1346395628 exited with status 150: termination requested by administrator
08/31/2012 00:56:35 - end writing; write time: 1:06:42
socket write failed (24)

Discussion Filed Under:

Backup and Recovery, NetBackup - 7.1.x and Earlier, NetBackup, Backing Up, Agent for Microsoft Exchange Server

Comments RSS Feed

Comments 2 Comments • Jump to latest comment

Backup_Exec Symantec Employee Accredited

Exchange DAG Backup failing with error 24 socket write failed - Comment:03 Sep 2012 : Link

Hi

For the above issue have checked the link below

http://www.symantec.com/docs/TECH34183

http://www.symantec.com/docs/TECH150369

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

Dyneshia Symantec Employee

Exchange DAG Backup failing with error 24 socket write failed - Comment:07 Oct 2012 : Link

More info is needed :

MAster Server OS :
NBU Version:

Media Server OS:
NBU Version :

Exchange server OS:
NBU Version :
Exchange Version:

IS this a CCR ? DAG ?
How many CAS servers are involved ?

Logs to look at :

   Master server
                --------------
                bpdbm

                Media server
                -------------
                bpbrm
                bptm
                bpdm

               Exchange
               -----------------
               bpbkar
               bpfis
               bpcd
               bpresolver