Symantec NetBackup status code 136 to status code 145
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 136 to Status Code 145 which may be received while using the Symantec NetBackup tool.
NetBackup status code: 136
Message: tir info was pruned from the image file
Explanation: The TIR information was pruned from one or more of the component
(differential or cumulative) backup images being synthesized.
This situation arises when the following occurs:
¦ The most recent backup image for the client is a synthetic full or cumulative
¦ The TIR information from one or more of the component images before the
synthetic full (or cumulative) backup is pruned
The TIR information is automatically restored to the image catalog if you expire
the synthetic backup (full or cumulative) image and try to rerun the synthetic
backup job for the client. However, the synthetic backup job fails with this error
if the TIR restore fails due to bad, missing, or vaulted media or a bad drive.
Recommended Action: Reimport the TIR information into the catalog of each
component image (from which the TIR information was pruned). Then rerun the
synthetic backup job. The TIR information can be imported into the image catalog
by initiating a true image restore of any file from that component image. The
restore process also restores the TIR information in the image catalog.
NetBackup status code: 140
Message: user id was not superuser
Explanation: A user or process that did not have root privileges (on UNIX and
Linux) or administrator privileges (on Windows) started the process.
RecommendedAction: If appropriate, give the user or the process administrator
privileges (on Windows) or root privileges (on UNIX and Linux) and retry the
NetBackup status code: 141
Message: file path specified is not absolute
Explanation: The file specification must be an absolute path.
Recommended Action: Correct the file specification and retry the command.
NetBackup status code: 142
Message: file does not exist
Explanation: To back up a VxFS file system with Snapshot Client, the VxFS file
system on the client must be patched with correct, dynamically linked libraries.
If the correct VxFS libraries are not installed, the backup fails with status 142.
The following appears in the log:
¦ For most snapshot backups, the following message appears in the
/usr/openv/netbackup/logs/bpfis log on the client:
09:36:48.299  <32> fs_dev_rt_check: FTL – snapshot method:
nbu_snap abort – required VxFS dynamic linked libraries for
NetBackup are not installed. Please visit the Symantec support
web site, and refer to Technote number 262225 for further
¦ For the backups that run from a FlashBackup policy, the following appears in
the /usr/openv/netbackup/logs/bpbkar log on the client:
10:09:56.566  <32> bpfsmap: FTL – bpfsmap: FlashBackup
abort – required VxFS dynamic linked libraries for NetBackup are
not installed. Please visit the Symantec support web site, and
refer to Technote number 262225 for further information.
10:09:56.571  <16> bpbkar Exit: ERR – bpbkar FATAL exit
status = 142: file does not exist
10:09:56.573  <4> bpbkar Exit: INF – EXIT STATUS 142: file
does not exist
¦ The bpexpdate, bpimmedia, bpimport, and bpverify commands can return this
status code if you cannot gather disk pool, disk volume, disk pool volume, disk
media IDs, or server type information.
¦ The bpbkar returns this status code if a checkpoint clone is missing, or if a
frozen image backup does not return the snapshot information.
Recommended Action: Install the VxFS dynamic libraries on the NetBackup
client as described in TechNote 28008 and try the backup again.
NetBackup status code: 143
Message: invalid command protocol
Explanation: Apoorly formed request was made to the NetBackup request daemon
(UNIX and Linux) or to the Request Manager service (Windows). This error can
be due to the following: mismatched versions of the product, corrupted network
communication, or to a non-NetBackup process sending data across the port for
the daemon or service.
RecommendedAction: Examine the NetBackup error logs to determine the system
that was the source of the data. On that system, determine the process that
initiated the request. If it was a NetBackup process, verify that the process or
command is compatible with the version of software on the server.
NetBackup status code: 144
Message: invalid command usage
Explanation: This status code is due to a NetBackup process being started with
improper options or an incompatibility in the product.
RecommendedAction: Either correct the command or verify that all NetBackup
binaries are at the same version level.
NetBackup status code: 145
Message: daemon is already running
Explanation: Another copy of the process is running.
RecommendedAction: Terminate the current copy of the process and then restart
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.