Tuning NetBackup – Part 2: Solaris 10

Disable TCP Fusion Getting NetBackup status code 23’s?  How about status code’s 24, 25, or 53?  Maybe you just have the occasional status code 50’s?  Chances are you have TCP Fusion enabled. TCP Fusion has caused many issues with NetBackup as it performs flow control while utilizing blocking I/O sockets.  With that said, I recommend everyone disable TCP Fusion if they are using NetBackup. In order to disable TCP Fusion you can utilize one of two ways to do so. OPTION 1: NON- PERSISTENT
  1. Make sure there are no backups or restores running
  2. Run echo 'do_tcp_fusion/W 0' | mdb –kw
  3. Run /usr/openv/netbackup/bin/goodies/netbackup stop
  4. Run /usr/openv/netbackup/bin/goodies/netbackup start
OPTION 2: PERSISTENT
  1. VI (edit) your /etc/system file.
  2. Add this line set ip:do_tcp_fusion = 0 and save.
  3. Reboot your Solaris 10 system
Shmmax CAUTION!!!!!   <<<<<DO NOT DO THIS>>>>> Only implement kernel tuning if you (1) know what you are doing, (2) have a back-out plan, and (3) have a 3-legged pony named “Zippy”.  Okay, so maybe not a 3-legged pony named “Zippy”… just making sure you are still awake during this wonderful tutorial. EDITOR’S NOTE: If you have a 3-legged pony named “Zippy”, a 3-legged animal, an animal named “Zippy”, or any other combination of: Zippy, 3-legged animals, or any-legged animals, DLT Solutions does not take responsibility for anything that you may or may not find offensive herein. Okay, so that statement was not input during the review process.  Yours truly added it and is now in trouble with our legal department!  Way to go Greg!  Okay, back on track… shmmax… You can tune Solaris 10 if you make the following modification to the /etc/system file. set shmsys:shminfo_shmmax=one half of system memory