Troubleshooting guide

Status Codes
82 NetBackup Troubleshooting Guide - UNIX
Recommended Action:
1. Check the All Log Entries and Problems reports to determine which system call failed
and other information about the error.
2. A frequent cause is that the server’s file system is full. For example, you may see a
message similar to the following in the Problems report or bpdbm activity log:
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent process
06/27/95 01:05:15 romb romb backup of client romb exited with status 11
(system call failed)
On UNIX systems, run a df command on the /usr/openv/netbackup/db
directory.
If the df command does not reveal the problem, check the bpdbm activity logs or do a
grep for the message
system call failed
in /usr/openv/netbackup/db/error/*
On Windows NT/2000 systems, verify that there is enough room in the disk partition
where NetBackup is installed.
3. Verify that the system is not running out of virtual memory. If virtual memory is the
problem, shut down unused applications or increase the amount of virtual memory.
To increase virtual memory on Windows NT/2000, 98, and 95:
a. Display the Control Panel.
b. Double-click System.
c. On the Performance tab, set Virtual Memory to a higher value.
4. Check for a semaphore problem. This error can be caused by the system not having
enough semaphores allocated. This is most commonly seen on Solaris 2 servers when
an RDBMS is also running.
The symptoms of the problem vary. In some cases, error messages in the NetBackup
log indicate a backup failure due to an error in semaphore operation; another
symptom is the inability of the NetBackup Device Manager service Media Manager
device daemon, ltid, to acquire a needed semaphore (this is the NetBackup Device
Manager service on Windows NT/2000).