Forum Discussion
I would suggest that you look at NET_BUFFER_SZ - a good article is here: https://www.veritas.com/support/en_US/article.100030830
Here is why I say that; from the job details you posted:
1. bptm (pid=16188) using 1048576 data buffer size
**This means currently the SIZE_DATA_BUFFER is 1048576. I'm just pointing this out as this is already large - at 1 Mebibyte.
2. bptm (pid=16188) waited for full buffer 219160 times, delayed 629651 times
**This means that the media server bptm process waited for a buffer to be full 219160 times; sometimes checking multiple times before a buffer was full (the multiple checks is why the delayed is 629651). What this means is that we are not receiving the information fast enough from the client to keep the buffers full. With this said - I wouldn't recommend starting with the media server buffer sizes - instead I would start with the network buffer size (or NET_BUFFER_SZ).
**** It also appears that you may have network resiliency enabled based on the following in the job details:
nbjm (pid=16108) Resiliency information was persisted, job is resilient.
You may want to disable this as a test as it can cause slow performance. See https://www.veritas.com/support/en_US/doc/18716246-157328516-0/v57758733-157328516 for details
3. bpbkar32 (pid=11808) bpbkar waited 54283 times for empty buffer, delayed 132114 times
** What this tells us is that bpbkar is waiting for network buffers to empty 54283 times - and had to check multiple times for an available network buffer. This indicates to me that the bottle neck is on the client side, and that there simply aren't enough, or large enough, network buffers. Hence - check out the Network buffer size article I popped in at the top of this reply. In addition, you may want to check out the following to make sure the tcp send and receive space is configured correctly:
https://www.veritas.com/support/en_US/article.100016112
Good luck!
Deb
NET_BUFFER_SZ is deprecated. Pls don't change the default value.
Best practices for NET_BUFFER_SZ and Buffer_size, why can't NetBackup change the TCP send/receive space
Related Content
- 2 months ago
- 3 months ago