cancel
Showing results for 
Search instead for 
Did you mean: 

NUMBER_DATA_BUFFERS

hkyeakley
Level 3

So I've read the tuning guide, I've played around with different options for SIZE and NUMBER of buffers and I understand the formula of SIZE * NUMBER * drives *MPX as it relates to shared memory.

Here's my question. Of the four parameters:

MPX level

# of drives (I have 12 drives)

NUMBER of buffers

SIZE of buffers (must be multiple of 1024 and can't exceed the block size supported by your tape or HBA)

 

The NUMBER of buffers and MPX level seem to be the two variables here. I have MPX set pretty low (2 or 3) and NUMBER of buffers set to either 16 or 32. When I multiply it all out, I get a hit on my shared memory of less than a GB. My media servers are dedicated linux hosts that only function as media servers and that's it. Furthermore, they each have somewhere around 35 - 50 GB of memory a piece.

With my current configuration, I'm not even scratching the surface of the amount of shared memory that's sitting idle in my system while my backups run at night. Is there any reason I shouldn't jack the NUMBER of data buffers up to... say... 500? 1000? I've seen some people mention that they have the number of buffers set to 64, but can we go higher?

I've searched around to see if there's a technote on the upper limit of the NUMBER buffers parameter. If there is such a tech note, I can't find it.

Any ideas?

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

Go higher - 64 is way to low. I run my media server on Linux as well. If you ramp it too high, you may hit the shared memory kernel limit and recive a status code 89 "problems encountered during setup of shared memory".

I use 262144 as SIZE_DATA_BUFFERS and at lest 512 for NUMBER_DATA_BUFFERS and NUMBER_DATA_BUFFETS_RESTORE.

Some test I did a few years ago when LOT3 was hot:

Before tuning: 19MB/sec (default values)

Second tuning attempt: 49MB/sec (using 128K block size, 64 buffers)

Final result: 129MB/sec  (using 128K block size and 256 buffers)

And some notes:

http://www.mass.dk/netbackup/guides/49-netbackup-buffer-tuning.html

http://www.mass.dk/netbackup/quick-hints/58-shared-memoy-on-linux-staus-code-89.html

View solution in original post

2 REPLIES 2

Nicolai
Moderator
Moderator
Partner    VIP   

Go higher - 64 is way to low. I run my media server on Linux as well. If you ramp it too high, you may hit the shared memory kernel limit and recive a status code 89 "problems encountered during setup of shared memory".

I use 262144 as SIZE_DATA_BUFFERS and at lest 512 for NUMBER_DATA_BUFFERS and NUMBER_DATA_BUFFETS_RESTORE.

Some test I did a few years ago when LOT3 was hot:

Before tuning: 19MB/sec (default values)

Second tuning attempt: 49MB/sec (using 128K block size, 64 buffers)

Final result: 129MB/sec  (using 128K block size and 256 buffers)

And some notes:

http://www.mass.dk/netbackup/guides/49-netbackup-buffer-tuning.html

http://www.mass.dk/netbackup/quick-hints/58-shared-memoy-on-linux-staus-code-89.html

Tmy_70
Level 5
Partner Accredited Certified

cd /usr/openv/netbackup
echo "262144" >> NET_BUFFER_SZ
cd db
mkdir config
cd config
echo "16" >> NUMBER_DATA_BUFFERS
echo "65536" >> SIZE_DATA_BUFFERS
/etc/init.d/netbackup stop
/etc/init.d/netbackup