How data buffer size and buffer number effect the Netbackup backup and restore performance?
Lately we are having a performance issue in our Widnow server. After looked into details, we found we had smaller data buffer size and buffer number in our Windows serve compare to our HP-UX server.
Can someone please help me with my confusings?
1. Does the data buffer size and buffer number effect the backup and restore performace dymantically?
It looks the backup performance is almost 10 times faster in our HP UX server than in our Window server.
HP-UX 11.31, version: 7.1.02, data buffer size: 262144, buffer number: 64
Windows 2008, 64bit, version: 7.1.0.2, data beffer size: 65536, buffer number: 12
2. How can we determine what is the best data buffer size and buffer number in our enviornment?
3. How can we set the data buffer size and buffer number in Window/Unix server?
4. Should we make the changes on media server only or both media server and client?
thanks,
felix
Felix
On your Media Servers under \program files\veritas\netbackup\db\ create (if it does not already exist) a folder named "config" - by default this folder only exists on a Master Server.
In that folder create your buffer files, they are case sensitive and do not have a file extention so make sure your Windows Explorer is not hiding extensions for know file types otherwise they may end up with a .txt on the end.
From my experience on Windows and using LTO4 or LTO5 drives and also backing up to disk the following work really well as long as Windows paging is also tuned:
SIZE_DATA_BUFFERS with a value of 262144
NUMBER_DATA_BUFFERS with a value of 32
SIZE_DATA_BUFFERS_DISK with a value of 1048576
NUMBER_DATA_BUFFERS_DISK with a value of 32
To tune your paging use the following registry keys (need a reboot) - create them if not already there:
HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\
DWORD - PoolUsageMaximum - Decimal value of 40
DWORD - PagedPoolSize Hex value of FFFFFFFF (this is 8 x F)
Hope this helps
