Video Screencast Help
Search Video Help Close Back
to help

About Error 13...!

Created: 15 Oct 2012 | Updated: 29 Oct 2012 | 4 comments
Sahil Joshi's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi All,

Some of the backups in our setup is failing by error code 13. We have done the entry if Client_read_Timeout on both media and client to more than 3600.

Infact the client_Read_time out entry on the media server is more than that of client.

I saw the below errors in the bpbkar logs.

10:12:51.788: [12972.12540] <16> dtcp_write: TCP - failure: send socket (1660) (TCP 10053: Software caused connection abort)
10:12:51.788: [12972.12540] <16> dtcp_write: TCP - failure: attempted to send 1 bytes
10:12:51.788: [12972.12540] <4> TfiExitEvent::signal(): INF - Terminate Signal called .
10:12:51.788: [12972.12540] <16> tar_base::keepaliveThread: INF - keepalive thread abnormal exit :14

11:43:27.746: [9836.13736] <16> dtcp_write: TCP - failure: send socket (1656) (TCP 10054: Connection reset by peer)
11:43:27.746: [9836.13736] <16> dtcp_write: TCP - failure: attempted to send 1 bytes
11:43:27.746: [9836.13736] <4> TfiExitEvent::signal(): INF - Terminate Signal called .
11:43:27.746: [9836.13736] <16> tar_base::keepaliveThread: INF - keepalive thread abnormal exit :14

Just want to know if this is a network error, and if yes then how can i prove this to customer.

Few more observations:

On the client end the network cards are teamed.

bpclntcmd -pn doesnot gives output. (this is the same case with other clients, but for them backup happens fine)

Kindly assist.

Regards,

 

 

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

Marianne van den Berg's picture

Please post all the text in Job details.

You need all of the following logs to troubleshoot:

On media server: bpbrm and bptm

On client: bpbkar

If you want us to help look at logs, please rename logs to reflect process name (e.g. bpbrm.txt) and post as File attachments.

Please also let us know which OS on media server and client as well as NBU version on media server and client.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

0
Login to vote
  • Actions
Yogesh9881's picture

Hi Sahil,

As u said "Some of the backups in our setup is failing by error code 13."

is it failing immediately or after some time ??

Kindly run below command & post o/p

<installpath>\veritas\netbackup\bin\admincmd#bptestbpcd -client SERVER01 -verbose -debug

 

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

0
Login to vote
  • Actions
revaroo's picture

Network issue. Either NIC card issue, network issue or software interferring with ports.

How many clients is it happening to? Are they all in the same network?

0
Login to vote
  • Actions
Sahil Joshi's picture

Sorry Folks for the late reply...

The issue got resolved. The clients are failing due to snap shot error, VSS issue as confirmed by Symantec.

Only the shadow Copy component backup is failing. After Multistreaming the policies, we understood the issue and now the case is with Microsoft.

SOLUTION
0
Login to vote
  • Actions