Veritas NetBackup™ Status Codes Reference Guide

Check the All Log Entries and Problems reports to determine the system call that failed and other information about the error.

nbjm and nbproxy return status code 11 when an exception is processed, such as when nbproxy obtains policy or configuration information. Examine the nbjm unified log (originator ID 117) or the nbproxy legacy log for more detail on the cause of the error.

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 debug 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 that 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 debug logs or do a grep for the message

system call failed

In relevant files under the directory /usr/openv/netbackup/db/error/

On Windows systems, verify that the disk partition where NetBackup is installed has enough room.

Verify that the system is not running out of virtual memory. If virtual memory is the problem, turn off unused applications or increase the amount of virtual memory.

The following information applies only to UNIX clients:

Check for a semaphore problem. This error may occur because the system does not have enough allocated semaphores. It is most commonly seen on Solaris 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 daemon, ltid, to acquire a needed semaphore.

System requirements vary; thus, no definite recommendations can be made. One customer running NetBackup and ORACLE on a Solaris server made the following changes to the /etc/system file and then restarted the system (boot -r). The changes were adequate.

set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600

Set these attributes to a value great enough to provide resources to all applications on your system.

Examine other debug logs or the progress log or status on the client. Examine the nbjm unified log (originator ID 117) for more detail on the cause of the error.