Backup Failes with status code 13 or 40

[backup-botw]

I dont believe this issue is actually related to a network issue because all of the other policies tied to this server work fine. I am not sure where to go with this one.

I found this bit in the bpbkar log from the client...

16:05:58.739 [4700.1924] <2> PackerTAR::processHeaderData(): DBG -  | An Exception of type [OutOfBufferException] has occured at: |   Module: @(#) $Source: src/ncf/tfi/lib/PackerTAR.cpp,v $ $Revision: 1.108 $ , Function: PackerTAR::processHeaderData(), Line: 963 |   Unable to get a buffer, pool size = 30 |  (../PackerTAR.cpp:963)

16:05:58.755 [4700.1924] <16> tar_tfi::processException: 

An Exception of type [OutOfBufferException] has occured at:

  Module: @(#) $Source: src/ncf/tfi/lib/PackerTAR.cpp,v $ $Revision: 1.108 $ , Function: PackerTAR::processHeaderData(), Line: 963

  Module: @(#) $Source: src/ncf/tfi/lib/PackerTAR.cpp,v $ $Revision: 1.108 $ , Function: PackerTAR::startObject(), Line: 478

  Unable to get a buffer, pool size = 30


16:05:58.755 [4700.1924] <4> tar_base::V_vTarMsgW: INF - tar message received from tar_backup_tfi::processException
16:05:58.771 [4700.1924] <2> tar_base::V_vTarMsgW: FTL - network connection broken
16:05:58.771 [4700.1924] <2> dtcp_write: TCP - success: send socket (1760), 32 of 32 bytes
16:05:58.771 [4700.1924] <4> ov_log::OVLoop: Timestamp
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF - V_MODE_BACKUP_POST:
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF -     number of file directives found: 2
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF -      number of files sent to server: 31279 out of 31279
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF -                          image size: 7053878784 bytes
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF -                     adjustment size: -6930147328 bytes
16:05:58.771 [4700.1924] <4> tar_backup::backup_done_state: INF -                         stream size: 123731456 bytes
16:05:58.771 [4700.1924] <2> tar_base::V_vTarMsgW: JBD - accelerator sent 123731456 bytes out of 7053878784 bytes to server, optimization 98.2%
16:05:58.771 [4700.1924] <2> dtcp_write: TCP - success: send socket (1760), 93 of 93 bytes
16:05:58.771 [4700.1924] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup
16:05:58.771 [4700.1924] <4> tar_base::stopKeepaliveThread: INF - waiting for keepalive thread to exit ...
16:05:58.771 [4700.5980] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
16:05:58.771 [4700.1924] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
16:05:58.771 [4700.1924] <8> tar_backup_tfi::cleanupTemp: WRN - will not cleanup 'temp' directory, debug level(s) are too high
16:05:58.771 [4700.1924] <4> send_msg_to_monitor: INF - in send_msg_to_monitor()...
16:05:58.771 [4700.1924] <2> dtcp_write: TCP - success: send socket (1760), 67 of 67 bytes
16:05:58.771 [4700.1924] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 40: network connection broken

I have attached the bpbkar and bpcd logs from the client.

This server has several policies because its remote and has a 1TB shared area with deparment shares and home drive data for users. The only policy that fails is the one that backs up Q-T.

F:\Home\Q*

F:\Home\R*

F:\Home\S*

F:\Home\T*

[sdo]

Version and SP of Windows please? And version of NetBackup Client? And version of media server and master too please? Is this a new backup client? Has this backup only recently started failing? Is the client a cluster member? Have you possibly been able to recently run a read-only chkdsk to search for NTFS structure errors? We see that Accelerator is being used for this backup. Has the backup client been configured to 'Use Windows change journal'? Any related events seen in the Windows application and/or system event log?

[watsons · Accepted solution]

From the logs, I can client is Windows..

The job started well, but at 16:05:58  process hits an exception:

An Exception of type [OutOfBufferException
Unable to get a buffer, pool size = 30 |  (../PackerTAR.cpp:963)

Check if the client is running out of system resources such as RAM, or low diskspace (for virtual memory).

You said for other backups (different policy) using this client it works, maybe those are smaller data compared to this one. If you can't add memory or clean up resources, try to break the backup selection into smaller chunks.

[backup-botw]

Thanks watsons...splitting this policy up even more than it was has resolved the issue.