Status Code: 2 Top

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.

 On UNIX clients, check to see if the files or directories would be excluded because of an entry in
/usr/openv/netbackup/exclude_list.
 On PC clients, check the exclude list per the instructions in the user's guide for the client.
 On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to
the files.

If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the
Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The
SYSTEM account cannot access network drives.

To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has
permission to access network drives.

Status Code: 6 Top

Message: the backup failed to back up the requested files

Explanation: Errors caused the user backup to fail.

Recommended Action:

1. Verify that you have read access to the files. Check the progress log on the client for messages on why the
backup failed. Correct problems and retry the backup.
2. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to
the files.
3. On Macintosh clients, this code can be due to multiple backups being attempted simultaneously on the same
client. Some possible solutions are:
o Adjust the backup schedules.
o If the client is only in one class, set the general class attribute, Maximum Jobs per Class, to 1.
o Set the NetBackup global attribute, Maximum Jobs Per Client, to 1 (note that this limits all clients in all
classes).
4. For a UNIX database extension client (for example, NetBackup for Oracle), this can mean a problem with the
script that is controlling the backup.

Check the progress report on the client for a message such as "Script exited with status code = number" (the number
will vary). The progress log also usually names the script.

Check the script for problems. Also, check the troubleshooting logs created by the database extension. See the
NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs.
Status Code: 13 Top

Message: file read failed

Explanation: A read of a file or socket failed. Possible causes include:

 I/O error reading from the file system.

 Read of an incomplete or corrupt file.
 Socket read failing. A socket read failure can be caused by a network problem or a problem with the process
that is writing to the socket.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the problem occurred.
2. For a FlashBackup client, check the /var/adm/messages log for errors like the following:

Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are
now unusable

This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if
multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of
them or reschedule the entire backup to a time when the file system is less active.

3. For detailed troubleshooting information, create an activity log directory for the process that returned this status
code, retry the operation, and check the resulting activity log.

Status Code: 21 Top

Message: socket open failed

Explanation: A socket open failed.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine
the cause from the Problems report, create activity log directories for the processes that returned this status
code. Then, retry the operation and check the resulting activity logs.
2. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the
NetBackup Release Notes - UNIX).
3. On Windows NT, verify that the recommended service packs are installed.

Status Code: 24 Top

Message: socket write failed

Explanation: A write operation to a socket failed.

Recommended Action:
 1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine
the cause from the Problems report, create activity log directories for the processes that could have returned
this status code. Then retry the operation and check the resulting activity logs.
2. A possible cause could be a high network load. For example, this has been seen in conjunction with Cannot
write to STDOUT when a Windows NT system that is monitoring network load has detected a high load and
sent an ICMP packet to other systems that says the route being used by those systems was disconnected. The
log messages were similar to the following:

01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242:
No route to host

01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_0823125016, copy 1,

fragment 1, 440864 Kbytes at 628.538 Kbytes/sec

01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com CLASS Remote3SysFullW SCHED Sirius
EXIT STATUS 24 (socket write failed)

3. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the
NetBackup Release Notes - UNIX).
4. On Windows NT, verify that the recommended service packs are installed.

Status Code: 25 Top

Message: cannot connect on socket

Explanation: A process timed out while connecting to another process for a particular operation. This problem can occur when a
process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is
not running (On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager
services). It can also occur if the network or server is heavily loaded and has slow response time.

Recommended Action:

1. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. If these processes
are not running, start them. On a Windows NT master server, verify that the NetBackup Request Manager and
NetBackup Database Manager services are running. If these services are not running, start them.

If the above processes are running, examine the All Log Entries report for the time of the failure to determine where the
failure occurred.

o If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify
again that the NetBackup Database Manager daemon (or service) is running. Then, create an activity
log directory for bpdbm, retry the operation, and check the resulting activity log.
o If you can view the report and have not found an entry related to this problem, create activity log
directories for the related processes that were running when the error first appeared (this process will
frequently be bpbrm). Then, retry the operation and check the resulting activity logs.
2. Verify that the server list specifies the correct master server.
o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in
the NetBackup Configuration dialog box.

To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions
menu (also see "Using the Configure - NetBackup Window" on page 57).

o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file.
o On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.
 If you change the server list on a master server, stop and restart the NetBackup database manager and request
daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows
NT).

3. Check the services file.

On UNIX, verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd,
bpdbm, and bprd. On Windows NT, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct
entries for bpcd, bpdbm, and bprd.

Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the
Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box,
start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure
- NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup
Client service starts. Also, see "Verifying Host Names and Services Entries" on page 31.

4. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the
NetBackup Release Notes - UNIX).
5. On Windows NT, verify that the recommended service packs are installed.

Status Code: 41 Top

Message: network connection timed out

Explanation: The server did not receive any information from the client for too long a period of time.

Recommended Action:

1. On a UNIX or Windows NT clients, check for the following problems with the bpbkar client process.
o •The bpbkar client process is hung on a file that has mandatory locking set. For this case, add the
following to the client's bp.conf file:

VERBOSE

and as root on the client execute:

touch /usr/openv/netbackup/bpbkar_path_tr

mkdir /usr/openv/netbackup/logs/bpbkar

Then retry the operation. The names of the files are logged in the activity log file in the
/usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them. The last file in the log will be the file
that is causing problems.

Note: Also, use the above procedure for other, "unknown" bpbkar hangs. If the problem is due to mandatory file
locking, you can have NetBackup skip the locked files by setting LOCKED_FILE_ACTION to SKIP in the
/usr/openv/netbackup/bp.conf file on the client.

o •The bpbkar client process is not hung, but due to the files and directories it is scanning, it has not
replied to the server within CLIENT_READ_TIMEOUT or CLIENT_CONNECT_TIMEOUT. This has
been seen to occur during backups when directories have thousands of unmodified files; it has also
been seen when backing up file systems or directories that reside on optical disk, which is considerably
slower than magnetic disk.
 For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT
values in the server's /usr/openv/netbackup/bp.conf file. The default for the CLIENT_READ_TIMEOUT and
CLIENT_CONNECT_TIMEOUT is 300 seconds if unspecified.

Use your system's ps command and monitor CPU utilization to help decide which of the above conditions exist.

When you are through investigating the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, since
the log files can become quite large and are not deleted automatically. Also delete
/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files than needed the next time you
create directory /usr/openv/netbackup/logs/bpbkar.

2. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows NT only) activity log
directories on the client, retry the operation, and check the resulting logs. If these logs do not provide a clue,
create a bpbrm activity log on the server, retry the operation again, and check the resulting activity log.

If the bpbrm log has entries similar to the following:

bpbrm hookup_timeout: timed out waiting during the client hookup

bpbrm Exit: client backup EXIT STATUS 41: network connection timed out

then the problem is in the routing configuration on the server. Verify that the client IP address is correct in the name
service that is being used. On UNIX, if both NIS and DNS files are used, verify that they match. Also, see "Resolving
Network Communication Problems" on page 21.

3. If you are using an AIX token ring adapter and the routed daemon is running, the timeout can occur because the
token ring adapter creates dynamic routes, causing the routed daemon to crash.
4. For a FlashBackup client, this can happen if the file system being backed up is very large and has a very large
number of files. It can also occur if a large number of concurrent data streams are active at the same time. The
corrective action is to add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set it to
increase the timeout interval.

Status Code: 48 Top

Message: client hostname could not be found

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

Recommended Action:

1. Verify that the client name is correct in:

o The NetBackup class configuration on the master server.
o The General and Clients tabs in the NetBackup Configuration dialog box on Microsoft Windows and
NetWare nontarget clients. To display this dialog box, start the Backup, Archive, and Restore interface
on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup
Window" on page 57).
o The bp.conf file on UNIX and Macintosh clients.
o The bp.ini file on OS/2 and NetWare target clients.
2. On clients and servers, verify that the name service is set up to correctly resolve the NetBackup client names.
On UNIX clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps.
Status Code: 50 Top

Message: client process aborted

Explanation: The client backup aborted. One instance when this code appears is if a NetBackup master or slave server is shut
down or rebooted when a backup or restore is in process.

Recommended Action:

1. Enable detailed activity logging:

o Create a bpbkar activity log directory (UNIX or Windows NT only).
o Create a bpcd activity log directory (this log is created automatically on Macintosh clients.
o On UNIX clients, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.
o On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3,
"Using the Logs and Reports."
2. Retry the operation and examine the resulting logs.
3. On UNIX clients, check for core files in the / directory.
4. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems.
5. This problem can sometimes be due to a corrupt binary.

On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, located in
/usr/openv/netbackup/bin on the client. Reinstall them if they are not the same as in the client directory under
/usr/openv/netbackup/client on the server.

On a Windows NT client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe executables located in the
install_path\NetBackup\bin folder on the client. Reinstall the client if these executables are not the same size as on
other Windows NT clients or are not at the same release level or do not have the same NetBackup patches applied as
other Windows NT clients.

Status Code: 54 Top

Message: timed out connecting to client

Explanation: The server could not complet e the connection to the client. The accept system call timed out after 60 seconds.

Recommended Action:

1. For a Macintosh or NetWare target client, verify that the server is not trying to connect when a backup or restore
is already in progress on the client. These clients can handle only one NetBackup job at a time.

On a Macintosh, you can check for activity by examining the NetBackupListen file in the following folder on the startup
disk of the Macintosh client: :System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy

2. On a Sequent platform, verify that the system has the correct level of TCP/IP.
3. Perform "Resolving Network Communication Problems" on page 21.
4. On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size.
Status Code: 58 Top

Message: can't connect to client

Explanation: The server was unable to connect to the client.

Recommended Action: Perform "Resolving Network Communication Problems" on page 21.

Status Code: 59 Top

Message: access to the client was not allowed

Explanation: The master or slave server is trying to access the client, but the server is not recognized by the client as a valid
server.

Recommended Action:

1. If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:
o On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration
dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and
click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).
o On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file.
o On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.

If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request
daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. On
Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.

2. On Windows NT clients, enable bpinetd activity logging as follows:

a. Create a bpinetd activity log directory on the client.

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and
Reports."
c. Retry the backup and examine the resulting logs to determine the cause of the failure.
2. On all but Macintosh clients, enable bpcd activity logging as follows:
a. Create a bpcd activity log directory on the client.
b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.
c. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the
Logs and Reports."
d. Retry the backup and examine the resulting logs to determine the cause of the failure.
3. On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically.

o Check the inetd log to see if NetBackupListen is running.

o Check the bpbkar and tar messages in the bpcd log file. To increase the amount of information
included in the logs, set the loglevel parameter in the mac.conf file to a higher value.
3. Check the bpcd activity log to determine the server's peername and what comparisons are being made. The
bpcd process compares NetBackup server list entries to the peername of the server attempting the connection
and rejects the connection if the names are different. If necessary, change the server list entry on the client to
match the peername.
4. On Windows NT clients, check the following:
o Verify that NetBackup for Windows NT software was installed under a Windows NT administrator
account.
 If NetBackup is under another type of account, reinstall it under an administrator account. The installation will
complete successfully under a non-administrator account but the NetBackup Client service is not added to
Windows NT and the NetBackup server cannot access the client.

o Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the
subnet that contains the NetBackup servers. UNIX and Windows NT clients are frequently not on the
same subnet and use different domain servers. When this condition exists the NetBackup servers and
Windows NT clients may be able to ping one another, but the server is still unable to access the
Windows NT client.
5. If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page
21.

Status Code: 71 Top

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 when there is only one file in
the file list and the file cannot be backed up due to an I/O error.

Recommended Action:

1. Verify that the correct file list is specified for this client.
2. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to
the files.

If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the
Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The
SYSTEM account cannot access network drives. To back up network drives or UNC paths, change the NetBackup
Client service startup to log in as a user that has permission to access network drives.

3. Check the All Log Entries report for clues.

4. Set up activity logging:
o • On UNIX and Windows NT clients, create an activity log directory for bpbkar.
o • On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created
automatically on Macintosh).

To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and
Reports."

5. Retry the operation and check the resulting activity logs.

Status Code: 86 Top

Message: media position error

Explanation: The system's device driver returned an I/O error while NetBackup was positioning media (tape or optical disk).

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error
• System and error logs for the system (UNIX)

• Event Viewer Application and System logs (Windows NT)

2. Check for the following:

• A defective or dirty drive. Clean it or have it repaired (see the tpclean command for cleaning).

• Incorrect drive configuration. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive could be configured for fixed mode when it must be variable mode. See the Media Manager
Device Configuration Guide for more information.

• 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 are using.

Status Code: 90 Top

Message: media manager received no data for backup image

Explanation: The tape manager (bptm) or disk manager (bpdm) received no data when performing a backup or archive. This can
occur for incremental backups where no data was backed up because no files have changed.

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error

• System and error logs for the system (UNIX)

• Event Viewer Application log (Windows NT)

2. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive may not be set for variable mode in a case where that mode is required by NetBackup. Check
the Media Manager Device Configuration Guide for drive configuration information.

3. Verify that the Media Manager configuration for the backup device matches what is specified for the storage unit in the
NetBackup class.

4. Verify that you are using the correct media in the drive.

5. For detailed debug information, create a bpdm or bptm activity log directory (whichever applies) on the server. If the client is
Windows NT, also create a bpbkar activity log directory on the client. Retry the operation and check the resulting activity logs.
Retry the operation. Check the resulting activity log file.

Status Code: 96 Top

Message: unable to allocate new media for backup, storage unit has none available

Explanation: The tape manager (bptm) could not allocate a new volume for backups. This indicates that the storage unit has no
more volumes available in the volume pool for this backup.

Recommended Action:

Check the NetBackup Problems report to determine the storage unit that is out of media.

1. If the storage unit is a robot and there are empty slots, add more volumes (remember to specify the correct volume pool).

• If there are no empty slots, move some media to nonrobotic and then add new volumes.

• If you are having difficulty keeping track of your available volumes, try the available_media script:

On UNIX, this script is in:

/usr/openv/netbackup/bin/goodies/available_media

install_path\NetBackup\bin\goodies\available_media.cmd

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

2. If the storage unit and volume pool appear to have media, verify the following:

• Volume is not FROZEN or SUSPENDED.

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 desired).

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

• Volume Database Host name for the device is correct.

If you change the Volume Database Host name, stop and restart the Media Manager device daemon, ltid, (if the server is UNIX)
or the NetBackup Device Manager service (if the server is a Windows NT system).

• The correct host is specified for the storage unit in the NetBackup configuration.

The host connection should be the server (master or slave) that has drives connected to it.

• The Media Manager volume configuration has media in the correct volume pool and unassigned or active media is available at
the required retention level.

Use the NetBackup Media List report to show the retention levels, volume pools, and status (active and so on) for all volumes.
Use the NetBackup Media Summary report to check for active volumes at the correct retention levels.

3. In some configurations, the NetBackup bptm process is rejected when requesting media from the vmd process (NetBackup
Volume Manager service on Windows NT) because that processcannot determine the name of the host that is making the
request.

This can be due to incorrect network configuration involving:

• Multiple network interfaces

• /etc/resolv.conf on those UNIX systems that use it

• Running DNS and not having reverse addressing configured

4. Create bptm and vmd activity log directories and retry the operation.

5. Examine the bptm activity log to verify that bptm is connecting to the correct system. If an error is logged, examine the vmd
log.

On UNIX, the vmd log is:

/usr/openv/volmgr/debug/daemon/log.xxxxxx

On Windows NT, the vmd log is:

install_path\Volmgr\debug\daemon\xxxxxx.log.

6. If this is a new storage unit, and this is the first attempt to use it, stop and restart NetBackup on the master server.

Note: The bptm activity logs (in verbose mode) usually show the NetBackup media selection process.

Status Code: 150 Top

Message: termination requested by administrator

Explanation: The process is terminating (or has terminated) as a direct result of a request from an authorized user or process.

Recommended Action: None.

Status Code: 196 Top

Message: client backup was not attempted because backup window closed

Explanation: A backup or archive operation that was queued by the backup scheduler was not attempted because the backup
window was no longer open.

Recommended Action:

• If possible, change the schedule to extend the backup window for this class and schedule combination so it does not occur
again.

• If the backup must be run, use the Manual Backup command on the Class menu in the Backup Policy Management window to
perform the backup. Manual backups ignore the backup window.

• If the backup must be run, use the NetBackup administration interface command for manual backups to perform the backup.
Manual backups ignore the backup window.

Status Code: 200 Top

Message: scheduler found no backups due to run

Explanation: When checking the class and schedule configuration, the NetBackup scheduler process (bpsched) did not find any
clients to back up. This could be due to:

• No backup time windows are open (applies only to full and incremental schedules).

• Classes are set to inactive.

• The clients were recently backed up and are not due for another backup (based on Frequency setting for the schedules).

• Classes do not have any clients.

Recommended Action: Usually, this message can be considered informational and does not indicate a problem. However, if you
suspect a problem:

1. Examine the NetBackup All Log Entries report to see if there are any messages in addition to one indicating that the
scheduler found nothing to do.

2. Examine the class configuration for all classes or the specific class in question and determine if any of the reasons mentioned
in the Explanation section above apply.

3. To obtain detailed troubleshooting information, create a bpsched activity log directory on the master server and retry the
operation. Check the resulting activity log.