Logs BPBKAR

Only for 1 day? Did it coincide with any errors for that server?

If its not happening continously then just delete the file and monitor the folder to see if it happens again.

Have a look in the log and see what it was doing ...

Normal, well, I don't know your environment, but I would say that seemed a tad on the large side ...

the server is being backed up and the logs is over 2G
The file system This greatly filled

Once the backup is finished, you can delete the log.  However, without looking in it there is no way to comment on why it is happening.

If you delete the dir, it will prevent bpbkar from making any logs.
 

often this server backup errors (Example 13) I need to analyze logs
  after an upgrade to 7.6.0.1 to 7.6.0.3 I have the error code 24

ROOT@admincmd> bptestbpcd -client nameserver -debug -verbose
11:22:41.271 [20765] <2> bptestbpcd: VERBOSE = 0
11:22:41.277 [20765] <2> vnet_pbxConnect: pbxConnectEx Succeeded
11:22:41.278 [20765] <2> logconnections: BPCD CONNECT FROM 10.59389 TO 10..1556 fd = 3
11:22:41.282 [20765] <2> vnet_pbxConnect: pbxConnectEx Succeeded
11:22:41.318 [20765] <8> do_pbx_service: [vnet_connect.c:2152] via PBX VNETD CONNECT FROM 10.250.5.145.41277 TO 10.109.10.13.1556 fd = 4
11:22:41.319 [20765] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
11:22:41.455 [20765] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string 3668
11:22:41.495 [20765] <2> put_string: cannot write data to network:  Connection reset by peer (104)
11:22:41.495 [20765] <2> bpcr_put_vnetd_forward_socket: put_string 3668 failed: 104
11:22:41.495 [20765] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 24
11:22:41.495 [20765] <2> ConnectToBPCD: bpcd_connect_and_verify(samba, samba) failed: 24
<16>bptestbpcd main: Function ConnectToBPCD(samba) failed: 24
11:22:41.495 [20765] <16> bptestbpcd main: Function ConnectToBPCD(samba) failed: 24
<16>bptestbpcd main: socket write failed
11:22:41.503 [20765] <16> bptestbpcd main: socket write failed
<2>bptestbpcd: socket write failed
11:22:41.503 [20765] <2> bptestbpcd: socket write failed
<2>bptestbpcd: EXIT status = 24
11:22:41.503 [20765] <2> bptestbpcd: EXIT status = 24
socket write failed
 

bptestbpcd failing with status 24 is suggestive of a network error, not a NetBackup error.

NetBackup doesn't control the network, it just uses what is available, and if that isn't working properly, it errors.

Are you a NetBackup Appliance? There were instances of 24 related to tcp timestamps setting on appliance

I'm not on a NetBackup Appliance.
Error 24 occurred after the update

TCP Chimney has been known to sometimes create intermittent errors. You'll see specific errors such as "2:18:23.023 PM: [1912.2224] <2> TransporterRemote::write[2](): DBG -  | An Exception of type [SocketWriteException] has occured at: |   Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.51 $ , Function: TransporterRemote::write[2](), Line: 307 |   Local Address: [::]:0 |   Remote Address: [::]:0 |   OS Error: 10054 (An existing connection was forcibly closed by the remote host."

In your bpbkar logs.

https://support.symantec.com/en_US/article.TECH150369.html

Please note, this sometimes works and sometimes doesn't.

regarding the error 24, I handed my server to its previous version (7.6.0.1) and error 24 is gone.
just be a patch problem to do with the Windows team

I have the same problem of bpbkar logs which swelled considerably.
I still do not understand why?