cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

NBU DB settings of Small/Medium/Large configuration

Hello Forum,  I was wondering what best practice is for setting the "small/medium/large" confioguration for the NBU db.

 

Is it based on the number of clients (we have 400 windows and Unix clients), the amount of data backed up daily (10-15TB) or number of backup streams running at once (400-700 streams nightly) ?

 

Currently our settings are set to the "small" configuration with a very large maximum (not sure when or how that was changed):

 

Setting Initial Minimum Maximum

Current 200M 200M 10053M

Small 200M 200M 2048M

Medium 768M 768M 2560M

Large 2048M 2048M 4096M

 

We have NBU 7.6.0.3 running on RedHat 2.6 Master and Media servers

 

As always, thanks in advance for any info/technotes, etc

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Go for medium/large no matter

Go for medium/large no matter what. Too small memory size will impact Netbackup operation. Espicially allocation/deallocation of deivces (e.g tape devices). 

The maximum value does not seem to be default ones ....

From : http://www.symantec.com/docs/HOWTO33587

Select this option to view and modify the SQL Anywhere memory cache settings of the relational database server.

Changes to these settings affect all of the relational databases that the database server manages, and do not take effect until the database server is restarted.

The database cache is an area of memory that the database server uses to store database pages for repeated fast access. The more pages that are accessible in the cache, the fewer times the database server needs to read data from disk. To read data from disk is a slow operation, so the amount of cache available is often a key factor that determines performance. The database cache is automatically resized as needed. The cache grows when the database server can usefully use more, as long as memory is available. The cache shrinks when other applications require cache memory, so that the database server does not unduly affect other applications on the system.

Three memory cache settings can be used to control the size of the database cache. These settings are set in the server.conf file. The database server reads the file when it is started. The server.conf file is found in the following locations:

View solution in original post

1 Reply
Highlighted
Accepted Solution!

Go for medium/large no matter

Go for medium/large no matter what. Too small memory size will impact Netbackup operation. Espicially allocation/deallocation of deivces (e.g tape devices). 

The maximum value does not seem to be default ones ....

From : http://www.symantec.com/docs/HOWTO33587

Select this option to view and modify the SQL Anywhere memory cache settings of the relational database server.

Changes to these settings affect all of the relational databases that the database server manages, and do not take effect until the database server is restarted.

The database cache is an area of memory that the database server uses to store database pages for repeated fast access. The more pages that are accessible in the cache, the fewer times the database server needs to read data from disk. To read data from disk is a slow operation, so the amount of cache available is often a key factor that determines performance. The database cache is automatically resized as needed. The cache grows when the database server can usefully use more, as long as memory is available. The cache shrinks when other applications require cache memory, so that the database server does not unduly affect other applications on the system.

Three memory cache settings can be used to control the size of the database cache. These settings are set in the server.conf file. The database server reads the file when it is started. The server.conf file is found in the following locations:

View solution in original post