Troubleshooting guide

Status Codes
78 NetBackup Troubleshooting Guide - UNIX
Recommended Action: None, unless this was a database backup performed through a
database extension product (for example, NetBackup for Oracle or NetBackup for SQL
Server). In those instances, code 0 means the backup script that started the backup ran
without error. However, you must check other status as explained in the related
NetBackup manual to see if the database was successfully backed up.
Status Code: 1
Message: the requested operation was partially successful
Explanation: A problem that may require corrective action was detected during the
requested operation.
Recommended Action: Check the All Log Entries report and also the progress log (if there
is one).
Some of the problems that can show up under Status Code 1 are:
◆ A file or directory path that is more than 1023 characters long.
◆ Could not open a file.
◆ On a UNIX system, NetBackup could not get the link name of a file.
◆ On a UNIX system, NetBackup could not process a sparse file.
◆ Read error encountered in a file.
◆ File is of an unknown type.
◆ On clients using Open Transaction Manager (OTM) for open file management, the
OTM cache may be full. See the recommended actions under status code 11.
◆ On a UNIX system, the lstat system call fails on a file that is eligible to be backed
up. This may be a permission problem.
◆ On UNIX, a file could not be locked that has mandatory locking enabled.
Status Code: 2
Message: none of the requested files were backed up
Explanation: A backup or archive could not back up any of the files in the file list.
Recommended Action: Verify that the files exist and you have read access to them.
◆ Check to see if there is a trailing space on one or more of the filenames in the client’s
file list. Remove any inadvertent trailing characters (such as spaces or tabs).
◆ On UNIX clients, check to see if the files or directories would be excluded because of
an entry in /usr/openv/netbackup/exclude_list.