NetBackup status code 1:

Message: the requested operation was partially successful

Explanation: A problem was detected that may require corrective action during the requested operation. The following are
some of the problems that can appear under status code 1:

1. A file or a directory path is more than 1023 characters long.

2. You cannot open a file. The file may have been locked for some reason.
3. NetBackup cannot get the link name of a file (Unix server).
4. Backups might fail skipping the system state backups.

Review below general areas for more information on the Status Code 1:

1. Activity Monitor | Job Details | Status window.

2. NBU Problems report
3. Bpbkar log on the client

DB backups

 User_ops/dbext
 Oracle: DBCLIENT log on client, RMAN script output log
 Vault: vault log and vault session directory from the master
 NDMP: bptm log, ndmp log from the master

NetBackup status code 5:

Message: the restore failed to recover the requested files

Explanation: Errors caused the restore to fail. It’s a generic error code for restore and could be several reasons for the failure.
Recommended Action: Perform the following items in the order presented:
■ Ensure that the client’s server list (bp.conf) contains entries for the master server and any media servers that can be used
during a backup or restore.
Edit the /usr/openv/netbackup/bp.conf file and ensure that there is a “SERVER=” line for any Master and Media Servers that
connect to the Client. The Master Server name must be the first SERVER entry in this server list, followed by an entry for any
Media Servers that will connect to the host.

■ Check the free space on directories where the files would be restored.

Destination Path
If the destination path must be changed, ensure that this destination restore path is typed with the proper path/syntax.

UNIX example: /usr/restore

Windows example: c:\restore
If error comes that the path is invalid then use unix path:
/C/ProgramFiles/*
NetApp NDMP host example: /vol/vol1/restore

Regardless of the destination path, check the ownership and permissions on directories where files will be restored. For
restores of UNIX and Windows Clients, the bpcd daemon/NetBackup Client Service must have access to the directory structure
where the files will be restored to. Otherwise, a status 5 will occur.

■ Check if the destination exists or not. In case of NDMP check is the volume-qtree exists.

To check the logs for the restore job:

Page | 1
/usr/openv/netbackup/logs/user_ops/<user_name>logs

Media Server Configuration

If the Media Server being used for restore is different from the Media Server that wrote the backup, use “Media Host
Override”.

FORCE_RESTORE_MEDIA_SERVER = original_media_svr_name new_media_svr_name

Verify the /etc/hosts file on the client should have the entries for the master/media server.

NetBackup status code 6:

Message: the backup failed to back up the requested files

Explanation: Errors caused the user backup to fail. It’s a generic error code for backup and could be several reasons for the
failure.
Recommended Action: Do the following as appropriate:
■ Verify that you have read access to the files. Check if the Database is online.
■ Verify that the account used to start the NetBackup Client service has read access to the files (Windows).
■ For a database backup this status code can indicate a problem with the script that controls the backup. E.g. check the
database script if the client name in the script is same as in NetBackup.

NetBackup status code 10:

Message: allocation failed

Explanation: The system memory allocation fails because of insufficient system memory available. A possible cause is that the
system is overloaded with too many processes and not enough physical or virtual memory.
Recommended Action: Free up memory by terminating any unneeded processes that consume memory. Add more swap space
or physical memory. Else try changing the backup schedule to the time when we have less number of processes running.

NetBackup status code 11:

Message: system call failed

Explanation: A system call has failed. This status code is used for a generic system call failure that does not have its own status
code.
Recommended Action:
■ 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. Verify that sufficient disk space is available on the volume where
NetBackup is installed.

Compress NetBackup Catalogs

NetBackup can be configured to compress catalog images in order to conserve disk space. This setting can be configured from
Host Properties -> Master Server -> Global Attributes Tab -> “Compress catalog interval”. Select a number of days to wait before
compressing images.

Page | 2
Migrate NetBackup Catalogs
Client images under /usr/openv/netbackup/db/images can be relocated to alternate volumes to reclaim space.

Eliminate Unnecessary Logging

When not actively troubleshooting a NetBackup issue, debug logs should be disabled or kept at a low verbose level.

■ 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.

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 storage destination of the storage unit of the NetBackup server
or media server. Verify that the path is in a mounted file system and not full.
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.

NetBackup status code 13:

Message: file read failed

Explanation: A read of a file or socket failed.
The possible causes include the following:
■ A network communication problem that occurred on the master server, media server, or one of the clients.
■ An I/O error that occurred during a read from the file system.
■ Read of an incomplete file or a corrupt file.
■ A socket read failure caused by a network problem or a problem with the process that writes to the socket.
Recommended Action:
■ Check that network communication works properly.
■ Ensure that all the network hardware (hubs, switches, routers, etc.) throughout the environment are set to full duplex, not
half duplex.

■ Check the following items regarding the NICs in your system:

 Upgrade to the latest NIC drivers throughout the system.
 Ensure that all NICs are set to full duplex, not half duplex.
 Replace the NIC itself on the affected client or server.

■ The files to back up exist on a file system that is not mounted.

NetBackup status code 14:

Message: file write failed

Explanation: A write to a file or socket failed.
Possible causes include the following:
■ An I/O error that occurred during a write to the file system.
■ Write to a socket failed. Cause of this failure: a network problem or a problem with the process that reads from the socket.
■ Writing to a full disk partition.
Recommended Action: Do the following, as appropriate:
■ Make sure that routers, bridges, and other network devices are all at "full" duplex.

Page | 3
■ A bad network interface card on a NetBackup client or server.
■ Faulty routers.
■ The error occurs while you use the NetBackup-Java interface: The application server (bpjava processes) for the NetBackup-
Java interface probably ran out of disk space in the file system containing /usr/openv/netbackup/logs/user_ops. The application
server writes temporary files into directories in the /user_ops directory. Try clearing up disk space in the file system.

Ensure that no volumes are full on the client in question.

Temporarily disabling VSP (VERITAS Snapshot Provider) may help focus on the source of the problem.

NetBackup status code 21:

Message: socket open failed

Explanation: A socket was not opened.

NetBackup status code 22:

Message: socket close failed

Explanation: A socket was not closed.

NetBackup status code 23:

Message: socket read failed

Explanation: A read operation from a socket failed.

NetBackup status code 24:

Message: socket write failed

Explanation: A write operation to a socket failed.
Recommended Action:
Verify that all operating system patches/service packs are installed. A possible cause is a high network load.

NetBackup status code 25:

Message: cannot connect on socket

Explanation: A process that timed out while it connects to another process for a particular operation.
It is important to ensure that processes are running on the Master Server and the client.

Ensure that PBX is installed and running.

Restarting PBX (UNIX):

For UNIX systems use the ps -ef |grep pbx command to determine if the pbx_exchange process is running. On NetBackup
servers the bpps -x command can also be used to verify if PBX is running. The "-x" switch is new in NetBackup 6.0 and will
display VERITAS Shared Processes such as pbx_exchange.

The following example is from a Solaris 9 server running NetBackup 6.0:

# /usr/openv/netbackup/bin/bpps -x

Page | 4
...
Shared VERITAS Processes
------------------------
root 827 1 0 Sep 23 ? 1:26 /opt/VRTSpbx/bin/pbx_exchange

To stop the pbx_exchange daemon:

# /opt/VRTSpbx/bin/vxpbx_exchanged stop

To start the pbx_exchange daemon:

# /opt/VRTSpbx/bin/vxpbx_exchanged start

This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon ( bprd) or
database manager daemon (bpdbm) and the daemon is not running.
Stop and restart NetBackup.
Unix
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all
Windows
install_path\NetBackup\bin\bpdown
install_path\NetBackup\bin\bpup

NetBackup status code 26:

Message: client/server handshaking failed

Explanation: A process on the server encountered an error when it communicated with the client. This error indicates that the
client and server were able to initiate communications, but encountered difficulties and the communications did not complete.

NetBackup status code 40:

Message: network connection broken

Explanation: The connection between the client and the server was broken. This status code can also appear if the connection
is broken between the master and the media server during a backup.

 If the bpbrm or bptm process was killed the backup fails with status 40.
 Status code 40 can also be due to denial of a mount request by the operator.
 This status code may occur if nbjm was unable to connect to bpbrm or to bpmount.
NetBackup status code 41:
Message: network connection timed out
Explanation: The server did not receive any information from the client for too long a period of time.

The bpbkar client process has not replied to the server within the Client read timeout or Client connect timeout period. This
error occurs during incremental backups when directories have thousands of unmodified files.
For this case, use Host Properties on the NetBackup server to change Client connect timeout or Client read timeout. Else add
the following in the client’s bp.conf
CLIENT_READ_TIMEOUT or
CLIENT_CONNECT_TIMEOUT.

On Windows systems, try the following:

■ Disable the following file:
install_path\VERITAS\NetBackup\bin\tracker.exe

Page | 5
Before performing the backup Netbackup estimates the files to be backed up. In case we have directories inside directories and
directories and then files that too in large number, NetBackup will hang during the estimation. In such cases we need to exclude
such files.

Enable allow multiple data stream and see which FS is causing the issue and try excluding it or removing the unwanted data.

NetBackup status code 48:

Message: client hostname could not be found

Explanation: The system function gethostbyname() failed to find the client’s host name.

Issue with the reverse lookup.

NetBackup status code 50:

Message: client process aborted

Explanation: The client backup terminated abnormally. For example, this error occurs if a NetBackup master or media server is
shut down or rebooted when a backup or restore is in progress.

Else if the backup processes got killed at the client side when the backup is in progress, may be because of any other process.

At times the backup fails while backing up the system state backups with status 50.

Resource/System level issues

It is often necessary to examine a Status Code 50 event from a Non-NetBackup perspective. Often, an OS or environmental
event is a factor in the Status Code 50. Examine the following non-NetBackup related information on all hosts involved with the
failure:

1. Available Memory on the system.

2. Available Hard Disk space on the system.
3. OS System Logs

Solaris: /var/adm/messages

HP-UX: /var/adm/syslog/syslog.log

NetBackup status code 52:

Message: timed out waiting for media manager to mount volume

Explanation: The requested volume was not mounted before the timeout expired.

 This error can also occur if the volume is a cleaning tape but was not specified as a cleaning tape.
 Another possible cause: the last available drive has a mount request for a non-backup (such as a restore). Then a
backup that requires the same drive is initiated before the mount completes. This error is due to the drive not being
reported as busy until the mount completes.
 Else the drive went down during the backup.

NetBackup status code 54:

Message: timed out connecting to client

Page | 6
Explanation: The server did not complete the connection to the client. The accept system or winsock call timed out after 60
seconds.

On a Windows NT/2000 or UNIX master server Verify NetBackup Server processes are running.

NetBackup status code 57:

Message: client connection refused

Explanation: The client refused a connection on the port number for bpcd.
This error can occur because of the following:
■ No process listening activity occurs on the bpcd port
Try netstat –a on the client and check the bpcd port should be “LISTENING”
■ The number of connections to the bpcd port is more than the network subsystem can handle with the listen() call

Recommended Action: Do the following, as appropriate:

■ Make sure the NetBackup client software is installed.
■ Verify that the bpcd and bprd port numbers in the
%SystemRoot%\system32\drivers\etc\services file on the server matches the setting on the client.
■ Verify that the NetBackup client service is running.

NDMP policy type:

When using the NDMP protocol make sure that the Policy Type of the policy being used is set to NDMP. This is set in the
Attributes tab of the policy. Having the Policy Type set to something other then NDMP, such as Standard or MS-Windows-NT,
will result in a status code 57 when a backup job is initiated.

Catalog backup file list:

For catalog backups, make sure the file paths are valid entries. In the Java GUI go to the Catalog section and select Actions >
Configure NetBackup catalog. The Files tab will list the files that will be backed up as part of the catalog backup. Ensure these
are pointing to the correct path names.

NetBackup status code 58:

Message: can’t connect to client

Explanation: The server was unable to connect to the client.
Recommended Action: Resolve network communication problems.

NetBackup status code 59:

Message: access to the client was not allowed

Explanation: The master or the media server tries to access the client, but the client does not recognize the server as a valid
server.

Recommended Action: Do the following, as appropriate:

■ If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:

Page | 7
 On Windows clients: Add the server on the Server to use for backups and restores drop-down in the Specify NetBackup
Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the
client. Then click Specify NetBackup Machines and Policy Type on the File menu.
■ On UNIX and Linux, and Macintosh clients: add a SERVER entry in the bp.conf file.

If the master server entries are there in the client so you would be able to connect to the client from host properties -> clients -
> servers. So add the media server entries.

Try removing unwanted entries and the first entry should always be the master server.

NetBackup status code 63:

Message: process was killed by a signal

Explanation: A kill signal was sent to the client process.
RecommendedAction: The usual cause for this error is that someone intentionally
terminated a backup.

NetBackup status code 69:

Message: invalid file list specification

Explanation: The file list from the server had invalid entries.
Check the selection list for OS backups and verify the backup selection with the DBA in case of the DB backups. Else try
removing the selection list and add it again, it might work.

NetBackup status code 71:

Message: none of the files in the file list exist

Explanation: The files in the file list did not match any of the files on the client. This error can occur with only one file in the file
list and the file cannot be backed up due to an I/O error.
Recommended Action: Do the following, as appropriate:
■ Verify that the correct file list is specified for this client.

If multi-streaming is enabled and a path does not exist, but is listed in the exclude list, Status
71 will be generated. This is the result of the order BPBKAR processes the backup information. With
multi-streaming enabled, the BPBKAR process first verifies that everything in the file list exists and
then checks the exclude_list.

Page | 8
In the above screen capture, if the path F:\Shared does not exist, and multi-streaming is enabled, the
backup will fail with a Status Code 71. This differs from non-multi-streamed backups, where
BPBKAR skips missing items in the file list and continues with the backup.

In case everything is fine try removing the selection list and add it again, it works in some cases.

Files List Inaccessible

If the policy file list is correct, the next most likely cause of Status 71 is the NetBackup Client is unable to access the files.

NetBackup status code 80:

Message: Media Manager device daemon (ltid) is not active

Explanation: If the server is UNIX or Linux, the NetBackup device manager daemon, ltid, is not running. If the server is
Windows, the NetBackup Device Manager service is not running.

NetBackup status code 81:

Message: Media Manager volume daemon (vmd) is not active

Explanation: The tape manager (bptm) did not communicate with the NetBackup Volume Manager (vmd). This communication
is required for most operations.

NetBackup status code 82:

Message: media manager killed by signal

Explanation: Another process or a user terminated the tape manager (bptm) or disk manager (bpdm).

NetBackup status code 83:

Message: media open error

Explanation: The tape manager (bptm) or disk manager (bpdm) did not open the device or file that the backup or restore must
use.
Recommended Action: Typically, this status code indicates a drive configuration problem
■ The configuration for the drives was modified (in the administrator interface or vm.conf) and the Media Manager device
daemon, ltid, was not restarted. Verify the configuration and then start ltid. On Windows, the problem may be that the Media
and Device Management device configuration was modified but the NetBackup Device Manager service was not restarted.
Verify the configuration and restart the NetBackup Device Manager service.
■ On Windows, make sure that the tapes are not write protected.
■ On UNIX and Linux, restart ltid in the verbose mode by running the following:
/usr/openv/volmgr/bin/ltid –v

When the backups are going to SAN using FT and settings are set to always use SAN. However the FT services on the media
server or the client are not running/hung, we get status 83.

NetBackup status code 84:

Message: media write error

Explanation: The system’s device driver returned an I/O error while NetBackup wrote to removable media or a disk file.
Recommended Action: Do the following, as appropriate:

Page | 9
Tape errors fall into two categories. Either there was an I/O error while writing or the tape was not at the correct position after
the write.

NetBackup keeps track of how much data it is sending to the operating system to write to the device. As an integrity check after
the end of each write, NetBackup will ask the tape device for its position. If this position does not match what NetBackup has
calculated the position should be, then the job will fail with a media write error.

This error will occur when NetBackup encounters an unexpected error while writing to disk. A disk full error will generally be
reported as a Status Code 129, but some disk-full conditions may be reported as the more general Status Code 84.
■ On Windows, make sure that the tapes are not write protected.
■ The wrong media type. Verify that the media matches the drive type you use.
■ Defective media. If it is defective, use the bpmedia command to set the volume to the FROZEN state so it is not used for
future backups.

NetBackup status code 85:

Message: media read error

Explanation: The system device driver returned an I/O error while NetBackup reads from tape or a disk file.
Recommended Action: For additional information, check the following:

■ Defective media. In this case, you may not be able to recover all the data on the media. Use the bpmedia command to set the
volume to the FROZEN state so it is not used for future backups.
■ The wrong media type. Verify that the media matches the drive type you use.

NetBackup status code 86:

Message: media position error

Explanation: The system’s device driver returned an I/O error while NetBackup was positioning the tape media.
Recommended Action: For additional information, check the following:

■ Defective media. In this case, some data may be lost. Use the bpmedia command to set the volume to the FROZEN state so it
is not used for future backups.
■ The wrong media type. Verify that the media matches the drive type you use.

NetBackup status code 89:

Message: problems encountered during setup of shared memory

Explanation: The NetBackup processes use shared memory for some operations. This status is returned when an error is
encountered in the initialization of the shared memory by the operating system’s APIs.
RecommendedAction: Check for a shared memory problem. This error can occur if the system cannot allocate enough shared
memory. It usually occurs with multiplexing, which increases the amount of shared memory that is required for the
operation.

Solaris: you may need to change one or more default System V Shared Memory settings to prevent jobs failing with the memory
allocation message, as follows:
■ For Solaris 9, the default shminfo_shmmax value is 8 megabytes. You can place the following line in your /etc/system file to
increase this setting. A value of 32 megabytes has been used in this example.
(This parameter is not applicable to Solaris 10).
set shmsys:shminfo_shmmax=33554432
■ For Solaris 9, the default shminfo_shmmni value is 100. You can place the following line in your /etc/system file to increase
this setting. A value of 220 has been used in this example. (This parameter is not applicable to Solaris 10).

Page | 10
set shmsys:shminfo_shmmni=220

Note: If you modify any of these values in the /etc/system file, you must reboot the system with boot -r for the new settings to
take effect.

NetBackup status code 90:

Message: media manager received no data for backup image

Explanation: The tape manager (bptm) or disk manager (bpdm) received no data when it performed a backup, archive, or
duplication. This error can occur for incremental backups where no data was backed up because no files have changed.
Recommended Action: Do the following, as appropriate:
Verify the exclude list as at time
 the selection list contains ALL_LOCAL_DRIVES
 and the policy has “allow multiple data streams” enabled
 so separate backups will run for each drive or filesystem. E.g. separate job for C, D and E or /, /usr and /var
 and if any of these are in the exclude list the backup will fail with status 90.

NetBackup status code 96:

Message: unable to allocate new media for backup, storage unit has none available
Explanation: The NetBackup resource broker (nbrb) did not allocate a new volume for backups. This error indicates that the
storage unit has no more volumes available in the volume pool for this backup.

Recommended Action:
■ If the storage unit is a robot with empty slots, add more volumes (remember to specify the correct volume pool).
■ If there are no empty slots, move some media to non robotic and then add new volumes.
■ If you have difficulty keeping track of your available volumes, try the available_media script:

On UNIX and Linux, this script is in:

/usr/openv/netbackup/bin/goodies/available_media
On Windows, the script is in:
install_path\NetBackup\bin\goodies\available_media.cmd

This script lists all volumes in the volume configuration, and augments that list with information on the volumes currently
assigned to NetBackup.

■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup needs a new tape and none are available in the
current volume pool, it does the following:
moves a tape from the scratch pool into the volume pool that the backup uses.

To check how many volumes are currently available in the scratch pool:

Vmquery | grep –i Scratch | wc -l

In case we have multiple robots configured in the environment run:

Vmquery –rn <robot_number>| grep –i Scratch | wc –l

Else click on media under media and device management and filter with ‘volume pool’ = “Scratch”. Check if the column robot
type shows TLD/ACS as if it shows NONE means that media is non robotic. You can also click on the particular robot no. under
media and then filter with “scratch”.

■ If the storage unit and volume pool appear to have media, verify the following:
■ Volume is not FULL, FROZEN or SUSPENDED.

Page | 11
Check for this condition by using the NetBackup Media List report. If the volume is frozen or suspended, use the bpmedia
command to unfreeze or unsuspend it (if that is wanted).

■ Volume has not expired or exceeded its maximum number of mounts.

Verify if the Scratch pool is properly configured.

Incorrect density in use

If the density defined in the storage unit does not match the density of the volumes as stored in the volume database, the
media is not considered for a backup.

NetBackup status code 98:

Message: error requesting media (tpreq)

Explanation: The tape manager (bptm) received an error when they requested a media mount from the NetBackup Device
Manager service (on Windows) or the Media Manager device daemon (ltid) (on UNIX and Linux).
Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report to determine the reason for the failure.
The most common cause is that the NetBackup Device Manager service (on Windows) or the Media Manager device daemon
(ltid) (on UNIX and Linux) is not running. Start it if necessary.
■ If you duplicate backups or use Vault to duplicate backups, this error could indicate the following: the Alternate Read Server
does not have access to the tape where the original backup resides.

In case the media labels are failing with status 98. Verify the drives on the media server used, try using a different media
server. If the tapes are VTL tapes check all the physical adaptor links are up. Finally check the nbrb evaluation time and you
might need to restart the NetBackup services or the master server.

NetBackup status code 99:

Message: NDMP backup failure

Explanation: The paths in your NDMP policy file list did not back up successfully.
Recommended Action: A possible cause for this error is that none of the backup paths exist on the NDMP host.

The NDMP backup job might fail with or without backing up any data:

 Verify if the volume/qtree/snapshot exits.

 Check if the filer volume is full.
 Check for the filer permissions and NDMP credentials.
 Set verbose level 70 on NDMP filer and OID 134 & 151 debug/diagnostic level to 6
 To check the logs on the filer side
shh filer name rdfile /var/messages | grep down
 The default timeout (NDMP_PROGRESS_TIMEOUT) value is 8 hours so the backups waits for 8 hours and fails without
writing:
echo 1440 > NDMP_PROGRESS_TIMEOUT
This creates the NDMP_PROGRESS_TIMEOUT file, and specifies a timeout value of 24 hours (1440 minutes).
 Finally at the filer end we can set the below setting:
Tape reservation – persistent

NetBackup status code 129:

Message: Disk storage unit is full

Page | 12
Explanation: As NetBackup writes to the file system for the disk storage unit,
runs out of space. Until more file system space is available, images of similar size
or larger may fail with this error when written to this disk storage unit.
In a scheduled backup job that writes to a storage unit group (which contains this
disk storage unit), the following occurs: the NetBackup scheduler requests the
storage unit with the greatest available capacity when the job is retried.

NetBackup status code 130:

Message: system error occurred

Explanation: An error occurred that prevents the product from operating in a
consistent fashion. This error is usually related to a system call.
Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for additional information about the
error.
■ Check the system log for reported problems.
NetBackup status codes
NetBackup status codes
108
■ For detailed troubleshooting information, create bpdbm, bptm, and bprd debug
log directories on the master server. Increase the unified logging level by using
the vxlogcfg command.
■ Retry the operation and check the resulting debug logs.

NetBackup status code 134:

Message: unable to process request because the server resources are busy
Explanation: Status code 134 is an informational message that indicates that all drives in the storage unit are currently in use. If
all drives are in use, NetBackup automatically tries another storage unit. If one is not available, NetBackup re-queues the job
with a status of 134 and retries it later.
Recommended Action: None.
The 134 code is an informational message only and is not considered an error. It can occur for a number of reasons in normal
operation. The 134 status code can occur more frequently in an SSO environment. No action is necessary.
A status 134 is not logged in the error logs. A 134 status causes a new try to appear in the Activity Monitor. It does not increase
the retry count that is associated with the allowed number of retries.
If the Status 134 error is exhibited extensively, this could indicate a possible problem in the implementation of VERITAS
NetBackup™, such as:

1. Too many jobs are running at once for the available server resources.
2. Poor network communication between hosts in the environment.
3. The library is too small to accommodate the environment’s policy configuration.
4. Multiple Storage Units are configured for the same host that also designates the same library and drives.

NetBackup status code 150:

Message: termination requested by administrator

Explanation: The process terminates (or has terminated) as a direct result of a request from an authorized user or process.
Recommended Action: None.

NetBackup status code 155:

Message: disk is full

Page | 13
Explanation: The write to the catalog file failed because the disk that contains the catalog database is full.
Recommended Action: Free up space on the disks where NetBackup catalogs eside and retry the operation.

NetBackup status code 156:

Message: snapshot error encountered

Explanation: The following are possible causes of this status code:
■ A snapshot-backup related error regarding Windows Open File Backup or Snapshot Client.
Recommended Action: Do the following, as appropriate:
■ For a Windows Open File Backup Snapshot Provider that uses VSS:

■ For backups using Snapshot Client and the NAS_Snapshot method, with or without SnapVault:
■ If the backup fails with status code 156, consult the bpfis legacy log, in
/usr/openv/netbackup/logs (UNIX and Linux) or
■ On Windows clients, when restoring files from a backup that is made with the NAS_Snapshot method, log into the NetBackup
Client Service as the Administrator account, not as the local system account. Otherwise, the backup fails with status 156.

■ For other NetBackup Snapshot Client issues:

■ The file system that is specified as a snapshot source is not mounted.

Do one of the following:

■ Configure the policy with a snapshot method that supports the client’s current file system.

If VSS/VSP are enabled a snapshot cache file would be created in the each drive before backup and in case the free space on the
drives is low and Netbackup fails to create the file. Backups might fail with 156.

Try disabling VSP/VSS from host properties - master server – client attributes – windows open file backup. In case the backups
are required with the snapshot try changing the VSP settings.

NetBackup status code 157:

Message: suspend requested by administrator

Explanation: Status code 157 is an informational message, which indicates that the administrator suspended the job from the
Activity Monitor. The job is in the suspended state in the Activity Monitor. It can be resumed from the last checkpoint by the
administrator.
Recommended Action: The administrator can resume the job from the last checkpoint from the Activity Monitor.

If the backups are not check pointed you can’t suspend the job. So only check pointed backups can be suspended.

NetBackup status code 174:

Message: media manager - system error occurred
Explanation: An abnormal condition caused a tape manager (bptm) or disk manager
(bpdm) failure.
Recommended Action: Do the following, as appropriate
A Status Code 174 with the following error message indicates one or more bytes which were sent across the network did not
make it to the Media server.

During backups, NetBackup keeps track of the number of bytes sent to it from the hard drive, and pads all blocks it receives to
512 bytes. After a backup finishes, as an integrity check to confirm all data was received, NetBackup divides the total number
of bytes received by 512. If this number divides evenly by 512, it is assumed all data was correctly received. If the number
does not divide evenly by 512, then it is assumed that some amount of data was not received. NetBackup only concludes that
not all of the data was received. During a data transmission for backup, it is the responsibility of the TCP stack to re-transmit

Page | 14
any packets that it recognizes as being dropped. The problem comes when the TCP stack does not recognize that a packet has
been dropped and does not re-transmit it properly.

The bptm log will show an error similar to this:

<32> fill_buffer: attempted to write 8 gigabytes, 1569582536 bytes, it is not a multiple of 512

The bpbkar log on the client will show how much data was sent:

<2> tar_base::backup_finish: TAR - backup: file data: 495841280 bytes 9 gigabytes

Two typical causes of a Status Code 174 are Network Interface Card (NIC) drivers, and (on some platforms) a gigabit ethernet
card in a 33-mHz PCI slot.

This type of error can be very difficult to troubleshoot given the fact that the TCP stack was unable to detect the loss of data.
The system log will rarely show any possible causes of the problem. Network analysis equipment may be necessary to
determine where the packets are being dropped.

Tape/SCSI Causes
If data is not written to the storage media as requested by NetBackup, a Status Code 174 error can occur.
Example:

From the bptm log file:

write_data: write of 64512 bytes indicated only 0 bytes were written, errno = 0
or
write_data: write of 65536 bytes indicated only 65528 bytes were written, errno = 0

NetBackup status code 190:

Message: found no images or media matching the selection criteria

Explanation: A verify, duplicate, or import was tried and no images that matched the search criteria were found in the
NetBackup catalog.
Recommended Action: Change the search criteria and retry.

In such errors the image is already duplicated but Netbackup thinks its not

nbstlutil cancel -backupid tsjipudbop101-bak_1386547282

This will cancel the image from SLP list

NetBackup status code 191:

Message: no images were successfully processed

Explanation: A verify, duplicate, duplication to remote master, automatic import, or import was tried and failed for all
selected images.
Recommended Action: Do the following, as appropriate:
■ If the error was encountered during duplication of backups, check the duplication progress log to help determine the root
cause of the problem.

■ An automatic import job may cause this error. This job is an import job that shows a storage lifecycle policy name.
■ If a Vault job encountered the error responsible for the duplication, check the duplicate.log files in your sidxxx directories to
determine the root cause:

Page | 15
UNIX and Linux:
/usr/openv/netbackup/vault/sessions/vault_name/sidxxx
(where xxx is the session ID)

NetBackup status code 196:

Message: client backup was not attempted because backup window closed
Explanation: A backup or an archive operation that the backup scheduler queued was not tried because the backup window
was no longer open.
Recommended Action: Do the following, as appropriate:
■ If possible, change the schedule to extend the backup window for this combination of policy and schedule so it does not occur
again.
■ If the backup must be run, use the Manual Backup command on the Policy menu in the Backup Policy Management window
to perform the backup.

Manual backups ignore the backup window.

Check if the resources are available till the backup window closes.

Maximum Jobs per policy and client

Policies have a setting for “Limit jobs per policy”. Ensure that this setting is not overly constrictive of jobs that could be running.
If the maximum number of jobs is reached on the policy, additional jobs will queue. If this setting is too low, queued jobs may
result in a status 196 despite the fact that they have the resources to run.

Within “Global Attributes” under the Master Server’s host properties, there is a setting for the “Maximum jobs per client”. This
has an effect similar to that of “Limit jobs per policy”, but on the client level.

We need to verify the multiplexing settings as well to ensure jobs will not remain in queue:

Multiplexing - Implementation
Multiplexing is configured in three places:
• Within the Storage Unit, under “Maximum multiplexing per drive”.
• Within the Policy Attributes through the “Allow Multiple Data Streams” checkbox.
• Within the Policy’s Schedule in the “Media Multiplexing” setting.

As mentioned above, the following configuration options might also be relevant when configuring multiplexing:
• Limit jobs per policy (set in Policy Attributes)
• Maximum Jobs per Client (set in Global Attributes)
• Maximum Data Streams (set in ‘Client Attributes’ within the Master Server’s host
properties)

NetBackup status code 198:

Message: no active policies contain schedules of the requested type for this client
Explanation: A user backup or archive was requested, and this client is not in a
policy that has a user backup or archive schedule.
RecommendedAction:Determine if the client is in any policy that has a schedule
of the appropriate type (either user backup or archive).
■ If the client is in such a policy, check the general policy attributes to verify
that the policy is set to active.
■ If the client is not in such a policy, do either of the following:
■ Add a schedule of the appropriate type to an existing policy that has this
client.
■ Create a new policy that has this client and a schedule of the appropriate
Type

Page | 16
NetBackup status code 213:

Message: no storage units available for use

Explanation: The NetBackup resource broker (nbrb) did not find any storage units
available for use. Either all storage units are unavailable or all storage units are
configured for On demand only. In addition, the policy and schedule does not
require a specific storage unit.
Recommended Action:

Common causes of Status Code 213.

Status code 213 falls into 3 main categories:
1. Prior to NetBackup 4.5 FP3 it was mandatory the master and media servers be at the same NetBackup version/patch
level. For these versions, the cause of a status code 213 is the media server not being the same version as the master.
2. Storage unit(s) incorrectly configured.
3. Policy has storage unit set to “any available” and drives are down.

Verify Storage Unit Configuration

1. Verify none of the storage units have their “Maximum concurrent jobs” attribute set to 0 (for Disk storage units) or
“Maximum concurrent drives used for backup” attribute set to 0 (for Media Manager storage units).
2. The "On Demand Only" attribute should only be used when a class/policy and schedule combination requires one and
only one particular storage unit. If the class/policy and schedule combination does not require a specific storage unit
at all times, then "On Demand Only" should not be selected. Determine if all storage units are set to "On Demand
Only" for a class/policy and schedule combination that does not require a specific storage unit. If this is the case,
either specify a storage unit for the class and schedule combination or turn off "On Demand Only" for a storage unit

Policy has Storage Unit set to “Any Available” and the Drives are Down.
A status code 213 is returned for any policy where the policy’s storage unit is set to "Any available" and there are no available
drives. (A status code 219 is returned for any policy where the storage unit is specified and there are no available drives.)

NetBackup status code 219:

Message: the required storage unit is unavailable

Explanation: The policy or schedule for the backup requires a specific storage unit, which is currently unavailable. This error
also occurs for other tries to use the storage unit within the current backup session.
Recommended Action: Look in the Job Details window for the failed job.
■ Verify that the schedule specifies the correct storage unit and the storage unit exists.
■ Verify that the following devices are running: the Media Manager device daemon (ltid) (UNIX or Linux server) or the
NetBackup Device Manager service (Windows server). Use bpps on UNIX and Linux and the Activity Monitor on Windows or the
Services application in the Windows Control Panel.
■ Verify the following attribute settings:

 For a disk storage unit, Maximum concurrent jobs is not set to 0.

 For a Media Manager storage unit, the Maximum concurrent drives attribute is not set to 0.
 If the storage unit is a tape, verify that at least one of the drives is in the UP state. Use the Device Monitor.
 Verify that the robot number and host in the storage unit configuration match what is specified in the Media and
Device Management device configuration.
 Verify that the master server can communicate with the bpcd process on the server that has the storage unit.

Page | 17
  Verify that bpcd listens on the port for connections. On a UNIX or Linux server where the storage unit is connected, if
you run netstat -a | grep bpcd, it should return something similar to the following:
*.bpcd *.* 0 0 0 0 LISTEN
 Check the nbrb and the mds logs by using the vxlogview command.

On Demand Only
If the "On Demand Only" attribute is checked on a Storage Unit, please note that any policies that do not target that Storage
Unit directly will not use that Storage Unit. For example, if a policy is set to use “Any Available” Storage Unit, it will not utilize a
Storage Unit that has the “On Demand Only” box checked.

Storage Unit(s) are not configured correctly

Maximum Concurrent Drives / Jobs
Verify that no Storage Units have their Maximum concurrent jobs attribute set to 0
Media Server Specification
Verify that the Media Server name in the Storage Unit configuration is correct.
Robot Number
Verify that the Robot number in the Storage Unit configuration matches the Media Manager device configuration

Multiplexing
In an SSO environment, when drives are shared, a job will typically requeue with a status code 134 if a drive is “over-
committed”. In some situations, due to timing, this scenario may result in a Status Code 219 (if a specific Storage Unit is
designated in the policy). To help minimize this, try increasing the “Maximum Multiplexing per drive” within the Storage Unit.
Allowing more streams per drive will increase drive availability (This also applies to non-SSO environments). Note that
Multiplexing can result in significantly longer restore times. See the Media Manager System Administrator’s Guide for more
information on this feature.

NetBackup status code 287:

Message: vault eject failed

Explanation: This error occurs when Vault fails to eject any of the media that
was identified for eject during a Vault Session. Potential reasons: Media and Device
Management services are down, the robot is down, or no empty slots are available
in the media access port (MAP).
Recommended Action: Ensure that the Media and Device Management services
are running, the robot is up, and empty slots are available in the media access
port (MAP).

NetBackup status code 288:

Message: vault eject partially succeeded

Explanation: This error occurs when not all of the media that was identified for
eject during a Vault session can be ejected.
Potential reasons include the following:
■ Some of the media is in use by NetBackup
NetBackup status codes
NetBackup status codes
174
■ Some of the media are in a drive
■ Not enough empty slots are available in the media access port (MAP)
Recommended Action: Ensure that the media are not loaded in a drive and in
use by other processes. Ensure that empty slots are available in the media access
port (MAP).

Page | 18
NetBackup status code 800:

Message: resource request failed

Explanation: The nbjm process was unable to get the required resources for a job. An EMM reason string that appears in the
Activity Monitor job details display and in the nbjm debug log accompanies this status code. The EMM reason string identifies
the reason for the failed resource request.
Recommended Action: Locate the EMM reason string, correct the problem, and rerun the job. Some generic EMM reason
strings (such as Disk volume is down) may require generating some reports to determine the cause of the failure. Generate the
report by using either bperror or various log entry reports.

Mostly happens when the robotic library is down on the robot and no drives are available.

Increasing the allowed threads for read to the database eliminated the status 800's.
An example of modifications that can be made are:

1. Create a file in /usr/openv/var/global/ named: emm.conf

In that file add:
NUM_DB_BROWSE_CONNECTIONS=10
NUM_DB_CONNECTIONS=11
NUM_ORB_THREADS=21

NUM_DB_CONN=NUM_DB_BROWSE_CONN+1

2. Save a copy of the existing /usr/openv/var/global/server.conf file.

Increase the following parameters:
-c 200M
-cl 200M
-ch 750M

The above configuration settings increase the read threads to emm. There is only one write thread to the database. This is
done intentionally to ensure data integrity.

It is not recommended to increase the settings further unless directed to do so by a Symantec NetBackup Technical Support
representative as each additional read thread may consume between 200 to 400MB of system memory.

*** USE CAUTION WHEN MODIFYING THE emm.conf and server.conf files! Incorrect spacing or typos prevent normal process
startup for nbemm.
NetBackup status code 2001:

Message: No drives are available for this job

Explanation: A job requested a tape drive, but no eligible drive path was configured for the job.
Recommended Action: Try the following:
■ Verify that the required drives and robots are configured and up.
■ Verify that ltid is active and a drive path exists that is configured on the drive for the media server that the storage unit
requires.
■ If the job requires an NDMP drive path, verify that one exists.

NetBackup status code 2009:

Message: All compatible drive paths are down but media is available
Explanation: All configured drives that can be used for this job are down.

Page | 19
RecommendedAction: Verify that ltid is running on the required media server, and the media server is active for tape. Using
device monitor, bring up the drive paths if they are down. If drives are downed again, clean the drives.

Documented By: Punit Kumar Dahiya

Organization: EMC

Page | 20