Depending on the erros and symptons you are seeing, it could be a space issue or a tunning issue.
1) Space - Make sure you have at 10% free space where netbackup is isntalled at. 7% the bare min. Once it goes below this threshold Netbackup will stop serivces to avoide data corruption.
2) Tuning - Reivew these tech notes :
http://www.symantec.com/docs/DOC4483 -
Symantec NetBackup™ 7.0 - 7.1 Backup Planning and Performance Tuning Guide
http://www.symantec.com/docs/TECH28934
3rd PARTY RELATED ISSUE: Linux kernel tuning recommendations for NetBackup (tm)
/etc/xinetd.conf
cps = 50 10
instances = 50
per_source = 10
hese values have been adjusted in other cases and could limit the number of connections --for example to 50 every 10 seconds and to 50 instances of each service per IP address. Additional information on these parameters are available at: http://linux.die.net/man/5/xinetd.conf
You can increase the number of connections or unlimit per your System Admin.
kernel parameters - sbin/sysctl -a
kernel.sem = 300 32000 32 1024
kernel.msgmnb = 65536
kernel.msgmni = 256
kernel.msgmax = 65536
kernel.shmmni = 4096
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
ulimit -a
ulimit tuning
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 1056767
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 8192
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
