Netbackup error 24 windows client

[Arturo_Lopez]

Hi,

We have a problem with a windows client backup. The versión of the master is 7.7.2 Linux redhat 5.5 and we are using a media appliance 5230 with the version 2.6.0.4. The last month que change de storage for backup from datadomain directly connected to master server to new storage appliance media server.

Now, not all days we have error 24 in this backup. We have configured other windows machines with the same OS in the appliance and not have this problem. But the problem is that not happen every days.

A little output with the error.

18-ago-2016 3:54:26 - end writing; write time: 0:34:14

18-ago-2016 3:56:31 - Critical bpbrm (pid=213086) from client mpavmlvpr1106: FTL - socket write failed

18-ago-2016 3:56:31 - Error bptm (pid=213252) system call failed - Connection reset by peer (at child.c.1306)

18-ago-2016 3:56:31 - Error bptm (pid=213252) unable to perform read from client socket, connection may have been broken

18-ago-2016 3:56:31 - Error bptm (pid=213089) media manager terminated by parent process

Anyone knows another case similar like this.

Regards.

[Marianne]

You forgot to tell us which Windows version on the problematic clients?

Here are some TNs regarding status 24 on Windows clients:

http://www.veritas.com/docs/000011538 

http://www.veritas.com/docs/000090272 

and forum discussion: 
https://vox.veritas.com/t5/NetBackup/Netbackup-failure-with-code-24/td-p/576636 

Many more forum discussions found by Google.... 

[Arturo_Lopez]

The version of windows is Windows server 2008.

[Marianne]

Have you had a look at the URLs in my previous post?

[Arturo_Lopez]

Sorry for response so late Marianne. Yes i check the URL that you have been posted but I'm having the same problem with the error 24.

[Marianne]

So, what have you done or checked since reading through the URLs?

[Michael_G_Ander]

Connection reset by peer (at child.c.1306) looks like a timeout/broken connection, the usually suspect for that is firewall, antivirus & slow answering file system.

firewall issues can often be migated by decreasing the TCP keepalive parameter on the client and servers to less than the firewall idle session timeout.

antivirus, can usually excluded processes e.g. bpbkar32

slow answering file system, can often be migated with defragmentation. Another thing seen slow file systems down is a too small page file. As windows seem to use the page file for some things if it exists even when there is free memory.