file read failed status code 13

[itenghm]

Hi
We have net backup 5.1 on windows 2003 server as master/media server when we try to do backups or restores from windows Xp clients it gives Error bpbrm(pid=2816) socket read failed, An existing connection was forcibly closed by the remote host. (10054) file read failed (13), I have tried everything but I still get this error

Any ideas please?

 

[Frbutler]

I think there was a thread about adjusting TCP_WAIT_TIME
you might want ot do a search on this board or archive for TCP.

It sounds like a delay in network activity and the port times out and closes. Then NBU goes to send data and the client OS reports the socket closed. you can also increase your client read timeouts in the gui from the default 300 seconds. Add a zero on the end just to test it and see if it works.

Thanks

 

[itenghm]

Thanks I will try it

 

[itenghm]

No, it doesn't work
the strange thing is: it was working before and suddenly failed, I increase client read timeouts, break up the NICs team, stop the anti virus, reinstalled the client, nothing seems to work!!

 

[Stumpr]

> backups or restores from windows Xp clients

What happens when you do it from the master server for these clients?

Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

it gives the same error (file read failed 13)

 

[Stumpr]

can you initiate the restore on the master and have it restore to the master (set destination as master)?

Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

yes I can; but no backup or restore from the clients

 

[Stumpr]

>can you initiate the restore on the master and have it >restore to the master (set destination as master)?

you say yes you can.

Now, next step. Can you initiate the restore on the master and have it restore to the client (set destination as client)



Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

no I can't same error file read failed

 

[Frbutler]

Could it be a rights/secutiry issue on the client
XP firewall or something?

XP could be blocking port traffic.

I am just grasping at straws here as I do not backup XP clients at my location.

 

[Stumpr]

I got this from the FAQ section. You can access them by clicking on FAQ at the top of the forum

In-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup (tm) Server / Enterprise Server 5.0 / 5.1

http://seer.support.veritas.com/docs/276941.htm

Let me know what questions you may have concerning the documentation. it is all numbered so you can easily tell me which step is causing problems



Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

Well in my case I will go to section 2 although I didn't make any changes to the NICs on the clients or the server but I will try upgrading my drivers and let you know

Thank you very much for your help

 

[itenghm]

I update the drivers and used another NIC, another switch
same stupid error

I have been working on this problem for 4 days

and I don't know what to do next

 

[Stumpr]

I have been working on this problem for 4 days and I don't know what to do next

If you cannot follow the in-depth troubleshooting guide for exit status code 13 then you should call symantec support.



Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

I followed the troubleshooting guide: the client and media server are not the same host, the client is not a flash backup nor an advance client and many clients are affected so the solution was by upgrading the NICs drivers and review the setting of network path between the server and the client. (which I did).
Anyway thanks for your help.

 

[Stumpr]

Did you look at the debug logs?

Enable Media server logging:
UNIX: /usr/openv/netbackup/logs/bpbrm
Windows: <install_path>\VERITAS\NetBackup\logs\bpbrm


Enable Client logging:
UNIX: /usr/openv/netbackup/logs/bpbkar
Windows: <install_path>\VERITAS\NetBackup\logs\bpbkar

You can also set the verbosity up to the highest lebel

Bob Stump
VERITAS - "Ain't it the truth?"

 

[itenghm]

from bpbackup log :
11:02:09.204 [880.5140] <2> logparams: -i -c Test -s Cumulative -S srv02-backup
11:02:09.204 [880.5140] <2> OV_SendProcessInfo2BPCD: Information - thread access token does not exist
11:02:09.204 [880.5140] <2> OV_SendProcessInfo2BPCD: Information - About to write 7706 bytes to named pipe
11:02:09.282 [880.5140] <2> OV_SendProcessInfo2BPCD: Information - successfully wrote information to named pipe
11:02:09.282 [880.5140] <2> ParseConfigExA: Unknown configuration option on line 51: RenameIfExists = 0
11:02:09.282 [880.5140] <2> logconnections: bprd CONNECT FROM ip.3969 TO ip.13720
11:02:09.282 [880.5140] <2> logconnections: BPRD CONNECT FROM ip.3969 TO ip.13720
11:02:09.298 [880.5140] <2> ParseConfigExA: Unknown configuration option on line 51: RenameIfExists = 0

 

[slayml]

Get rid of all "weird" software on the XP machines, like Power Toys, firewall s/w, most active X installs, etc. NetBackup was really not designed to backup workstations so you have to make the environment CLEAN and PRISTINE to avoid status code 13's. Also check your TCP/IP stack.

 

[OzzMosiz]

itenghm, did you fix this issue in the end?

Can you resolve the client from the Master and the Master from the client (bot hostnames and IP addresses)?