Status code 41

[Rithesh]

HI All,

One of my netbackup client(6.5.2A)windows 2008 server is getting status code 41 on weekly as well as weekly full backup.

I tried to increace the client timeout, but no luck,

I also tried to create file named bpbkar_path_tr in \netbackup on client, it didn't trace any locked files.

I checked out the bpbkar logs which is as follows

284.4924] <16> dtcp_write: TCP - failure: send socket (360) (TCP 10054: Connection reset by peer)
2:25:58.596 AM: [284.4924] <16> dtcp_write: TCP - failure: attempted to send 23 bytes
2:25:58.596 AM: [284.4924] <16> dtcp_write: TCP - failure: send socket (360) (TCP 10054: Connection reset by peer)
2:25:58.596 AM: [284.4924] <16> dtcp_write: TCP - failure: attempted to send 22 bytes
2:25:58.612 AM: [284.4924] <16> dtcp_write: TCP - failure: send socket (360) (TCP 10054: Connection reset by peer)
2:25:58.612 AM: [284.4924] <16> dtcp_write: TCP - failure: attempted to send 19 bytes
2:25:58.612 AM: [284.4924] <16> dtcp_read: TCP - failure: recv socket (484) (TCP 10054: Connection reset by peer)
2:25:58.612 AM: [284.4924] <2> tar_base::V_vTarMsgW: ERR - CONTINUE BACKUP message not received
2:25:58.612 AM: [284.4924] <16> dtcp_write: TCP - failure: send socket (360) (TCP 10054: Connection reset by peer)
2:25:58.612 AM: [284.4924] <16> dtcp_write: TCP - failure: attempted to send 43 bytes
2:25:58.612 AM: [284.4924] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
2:25:58.612 AM: [284.4924] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
2:25:58.612 AM: [284.4924] <4>

I checked the connectivity b/w the master server & client through bptestclnt command.its also fine.

Can anyone please help on this..

Thanks
Ritz

[lu]

Could you post more lines from your bpbkar log ?

[Will_Restore · Accepted solution]

The following error message will appear in the bpbkar log file on the client:
"(TCP 10054: Connection reset by peer)"
http://seer.entsupport.symantec.com/docs/200380.htm


This error has been attributed to a variety of causes:

1. A temporary disruption in the network communication (i.e. happens once in a great while)
2. Bad network interface card (NIC) on the client
3. Bad NIC on the server
4. Faulty routers or routers that are not set to the correct duplex
5. Other programs (applications) cause the VERITAS NetBackup connection to drop

[Rithesh]

Thanks for the suggestions..
Actually the server had some h/w issues tooo.