Symantec NetBackup status code 11 to status code 12
Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.
Below are some of the NetBackup status error codes from Status Code 11 to Status Code 12 which may be received while using the Symantec NetBackup tool.
NetBackup status code: 11
Message: system call failed
Explanation: Asystem call has failed. This status code is used for a generic system
call failure that does not have its own status code.
Recommended Action: Do the following, as appropriate:
■ 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
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call
06/27/95 01:04:01 romb romb media manager terminated by parent
06/27/95 01:05:15 romb romb backup of client romb that exited with
status 11 (system call failed)
On UNIX and Linux systems, run a df command on the
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
To increase virtual memory on Windows, do the following in the order
■ Display the Control Panel.
■ Double-click System.
■ On the Performance tab, set Virtual Memory to a higher value.
■ The following information applies only to UNIX and Linux 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 rebooted the system (boot
-r). The changes were adequate.
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
NetBackup status code: 12
Message: file open failed
Explanation: An open of a file failed.
A disk storage unit tries to write to or create a directory on the root device of the
NetBackup server or media server. In this case, the Activity Monitor job details
log contains the message “not permitted to root device.” By default the absolute
path or specified directory for a disk storage unit cannot be on the root file system
(or system disk). You must explicitly enable them to be there when the storage
unit is created.
Recommended Action: Do the following as appropriate:
■ If you want the path for the disk storage unit to reside in the root file system:
Open the Change Storage Unit dialog box in the NetBackup Administration
Console and select the check box: This directory can exist on the root file
system or system disk.
■ If the specified path for the disk storage unit is not in the root file system or
system device, verify that the path is in a mounted file system.
■ If the specified path for the disk storage unit is in the root file system or system
device but does not need to be, use the Change Storage Unit dialog box to
specify a different (non-root) path in a mounted file system.
■ Check the NetBackup Problems report. Try to determine the file and why the
error occurred. A possible cause is a permission problem with the file. For
detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then, retry the operation and check
the resulting debug log.
■ For NetBackup Lotus Notes, point-in-time restore jobs may fail with a status
12. These jobs are initiated from the master server by using either the
NetBackup Administration Console or the Backup, Archive, and Restore
interface. Their failure is reported in the NetBackup tar log file. (For Windows,
this file is located in the install_path\NetBackup\logs\tar folder. For UNIX
and Linux, it is located in the /usr/openv/netbackup/logs/tar folder.) If the
install path of the NetBackup master server is different from the install path
of the NetBackup client, the automatic restore of Lotus transaction log extents
during recovery of the Lotus database fail. Note that the Activity Monitor
shows a status 0 (successful). The tar log on the client, however, shows success
for the restore but a failure (status 12) for the Lotus database recovery.
Perform the restore job from the Backup, Archive, and Restore interface on
the NetBackup client.
■ For NetBackup Snapshot Client, status code 12 may appear in the
/usr/openv/netbackup/logs/bptm or bpdm log with the following:
tpc_read_config failed: cannot open file
This status code may indicate that the policy is configured with either the
NetBackup media server or Third-Party Copy Device as the off-host backup
method, but the 3pc.conf file does not exist or is in the wrong location.
Instructions are available on how to create the 3pc.conf file.
See the NetBackup Snapshot Client Administrator’s Guide.
■ For a FlashBackup policy, if the CACHE= entry follows the source data entry,
the backup fails with status code 12. Messages such as the following appear
in the /usr/openv/netbackup/logs/bpbkar logs on the client:
09:55:33.941  <16> bpfsmap: ERR – open_snapdisk: NBU
snapshot enable failed error 3
09:55:33.942  <32> bpfsmap: FTL – bpfsmap: can’t open
snapshot disk /dev/rdsk/c4t1d0s3 errno 0
09:55:33.950  <16> bpbkar Exit: ERR – bpbkar FATAL exit
status = 12: file open failed
09:55:33.956  <4> bpbkar Exit: INF – EXIT STATUS 12: file
09:55:33.957  <2> bpbkar Exit: INF – Close of stdout
Change the order of the backup selections list so that theCACHEentry precedes
the source data entry. (The source data entry specifies the raw partition that
contains the file system to be backed up.)
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.